Date: Sun, 3 Oct 1999 21:31:20 -0400 (EDT) From: David Kott <dakott@home.com> To: John Dowdal <jdowdal@destiny.erols.com> Cc: High Voltage <zapper@idsmail.com>, FreeBSD-Stable <freebsd-stable@FreeBSD.ORG> Subject: Re: @Home Connect. Message-ID: <Pine.BSF.4.10.9910032108310.87389-100000@kott> In-Reply-To: <Pine.BSF.4.05.9910031835010.44787-100000@destiny.erols.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 3 Oct 1999, John Dowdal wrote:
> One additional note for setting up @home, or most other cable modem
> services, (hmm .. any more words to throw in here for the search engine?)
> make sure you power cycle the cable modem when switching between two
> computers. When the cable modem powers up, it locks itself onto the MAC
> address of your ethernet card, and only listens to packets from that one
> address. If you go from one computer to another (or one ethernet card to
> another), you must power cycle the cable modem to reinitialize the MAC
> address, otherwise the connection will appear totally dead. Two friends
> of mine have wasted hours on this; lets get this archived to keep anyone
> else from wasting all this time.
That seems odd to me. My roommate and I share the same cable modem. We
are not proxied as each of us have a distinct, and static IP. @Home
allows us to purchase additional IPs (up to 3 per household) to add
additional computers.
The modem is a Mot. Cybersurfer Wave.
I merely ran the cable modem's 10bT segment to the crossover port on an
el-cheapo hub, and regular patch cable to each of our NICs.
Perhaps your friends are using a first generation cable modem?
Perhaps there is an ability to configure the cable modem we have remotely
at the service head to allow multiple MAC addresses on the same segment?
The modem would have to cache this configuration in something
non-volatile as I have cycled the power on it several times.
Also, I see ARP requests bouncing off my NIC (and presumably my
roommates). This seems to suggest that most of the MAC level filtering,
if you will, is done at the upstream router, and not necessarily in the
cable modem itself.
>
> Otherwise, its quite easy to set up. You could set up the DHCP client, or
> else just run 'winipcfg' on the windoze machine they set up to get your
> IP, netmask, gateway, dhcp server, and DNS server, and punch that
> information into the BSD machine.
>
It is indeed easy to setup. Just copy down the settings the techy
installs in your Win32 configuration and translate them when you boot
'nix.
For instance, place the DNS entries in /etc/resolv.conf in this format:
nameserver nnn.nnn.nnn.nnn
where:
nnn.nnn.nnn.nnn is your assigned nameserver
and use something similiar to the following commands to utilize your @Home
interface:
ifconfig de0 inet xxx.xxx.xxx.xxx netmask 255.255.255.0
route add default ddd.ddd.ddd.ddd
where:
xxx.xxx.xxx.xxx is your IP.
ddd.ddd.ddd.ddd is your upstream router. (called a "gateway" in
Microsoft-eze)
replace interface "de0" with the interface that is attached to your
cable modem.
I don't use DHCP, and indeed, the only time I ever tried to use it, no one
responded to the DHCP requests. I am not very familiar w/ the protocol
or implementation that I tried, so YMMV.
Curiosity may, or may not, have killed Schrodinger's cat.
-townba
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9910032108310.87389-100000>