Hi, Mike.
The usual problem with setting up @Home service with Linux is that many
@Home installations use MAC-address authentication to identify the computers
allowed to connect to the service. If this is the source of your problem,
then the network is remembering the identity of the Ethernet card in your
Win98 machine and will not lease "its" address to your Linux host.
Four possibilities for getting around this:
1. Power down the cable-modem device and leave it off for about 5 minutes,
to let it lose state (sort of equivalent to a PC BIOS losing its CMOS
settings). Then plug everything in and see if the Linux host now gets a DHCP
address. In some areas, the MAC-address stuff is in the cable-modem box and
can be reset this way.
2. Tell @Home you have changed computers and they need to recognize the new
NIC. Since this is NOT a Linux issue -- changing to a new Windows host would
raise the same problem -- they shouldn't blow you off on this request. SOme
areas control MAC-address settings from the head end.
3. Spoof the MAC address of the Win98 host's Ethernet card in the Linux
host. If you can do this -- some NICs/modules will do it, but not all, and I
don't know if 3c59x.o does -- you do it with a command about like the following:
ifconfig eth0 hw Ethernet aa:bb:cc:dd:ee:ff
replacing the last part with the MAC address you want to use (I'm not
certain of the format for the address; the man page isn't clear on that, and
I don't have an example here to check).
4. Connect the Windows computer, note the address and other information it
gets in its lease, and hand-configure the Linux host with the same addeess,
netmask, nameservers, etc. This might not work, and it is risky even if it
does ... when your lease expires, you won't get a new address assignment ...
but it will serve as a short-term test to verify that you don't have
hardware problems we are missing.
Another possibility is that you have to provide a specific hostname to the
head end to get an address; if you do, they should have told you so (or put
it into your Windows settings, if they did the setup for you). If so, that's
a simple DHCP client option; there is probably a commented-out example in
the dhcpcd config file.
DHCP leases normally provide nameserver information, so your not having them
is just another symptom of the failure to get a lease.
Unfortunately, @Home service characteristics vary a lot from community to
community, so while I (and others) can give you some general advice, you
need to find someone who has installed Linux locally (in or near Mt View) to
tell you what specific problems your instance of @Home imposes on Linux users.
For more information, consult the Cable Modem HowTo, one of the HowTos at
http://www.linuxdoc.org . Also, if you can search the archives of the
[EMAIL PROTECTED] mailing list (it's archived at
http://www.geocrawler.com/lists/3/Linux/303/0/), you will find a lot of
discussion of problems connecting LRP router/firewalls to @Home.
Sorry I can't give you more specific help than this. If you get partway
through and have more problems, please don't hesitate to post a follow-up.
At 08:04 PM 7/22/00 -0700, Mike Keithley wrote:
>Hello all
>
>I know this has been discussed and I've followed some of the suggestions
>but I'm deep in the woods as to getting My @home in Mountain View Ca to
>work at all. Help is really appreciated.
...
>I am using Slackware 7.1 under the 2.2.16 kernel. I know my eithernet
>card is working as ifconfig -a shows an entry for it.
[other details deleted]
--
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
