>On Sun, 23 Jul 2000, Mike Keithley wrote about, Confuguring @home with Linux:
>> Hello all
>>
>> 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.
>>
>> eth0 Link encap:Ethernet HWaddr 00:B0:D0:76:AC:96
>> BROADCAST MTU:1500 Metric:1
>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:100
>> Interrupt:10 Base address:0xec00
>>
>> The 3com card appears to be initialize at boottime:
>
>It is also transmitting packets to the modem, TX count = 8 BUT RX count = 0
>so your modem is NOT talking to the eth0 interface, rest of the answer
>below.
>
>>
>> The Cable modem is an RCA model but I don't know the number.
>
>Please tell us, is the ethernet card a different card to the one you use in
>Windows.???? THIS IS IMPORTANT.
>
It is the same card.
>>
>> Although I'm blind and can't see the lights on the cable modem, I'm told
>> they change so I believe the network card is talking to the modem.
>
>Like i said above, its a ONE way link at this minute.
>
Do I understand correctly that at least 1 packet should be received from
the modem even if the dhcpd failed?
>>
>> The network is working in Windows 98. The fellow who installed the
>> modem got it up and running without installing any software that I can
>> tell. It's possible that something is hidden! For information, I've looked in
>> control panel/networks/tcpip protocols and that is where I found that the
>> "automatically assign IP address was checked" which leads me to assume
>> that an IP address is assigned to the cable modem when it logs on. (it
>> is an rca modem and the docs say it supports Linux.) If I understand
>> the doc right, the modem is always connected to the @home network (even
>> when the computer is off) unless the modem is powered off.
>>
>> Another thing I noticed in Windows is that SNS is disabled. The thing
>> works magically!
>>
>> I tried using dhcpcd as suggested and it returned after 30 seconds
>> without any output but neither route or inconfig show connection to
>> eth0. Dhcp was installed when I sdt up Slackware but I haven't
>> configured it (reading the dhcp how-to makes me feel I'm ok there).
>> Dhcpcd leaves an error in syslog that it timed out waiting for a valid
>> dhcp server response. Sounds like that's saying there's no dhcp server on the
>> net.
>
>No it's not saying anything, your modem is NOT talking to the ethnet card,
>the RX count =0.
>Your modem quite possably needs to be reset by your provider and
>reconfigured with the MAC address of the 3com card in the linux machine.
>
>Most modems have ONE mac address programed into them, which means if one
>changes the ethernet card the MAC address will no longer be valid so the
>MODEM will NOT talk to the computer.
>
>You have 2 chooises as i see it, one ask your ISP to change the MAC address.
>or place the ethernet card from the windows machine to the linux machine.
>
Choice 2 is implemented.
Since the MAC address is the same, the problem appears to be the card
can't talk to the modem.
My computer is a dell Optiplex 800 Mhz machine with the card integrated
on the motherboard.
Someone suggested I read the Cable-Modem HOWTO
because the Slackware distribution has a quirk where things look ok at
boot-up but the card is in Plug & Play mode and needs to be changed to
PCI mode. The HOWTO suggest getting the DOS utility from 3com to check this.
I did that but get a run-time devide-by-zero error occurs so I don't know how
the card is configured. The 3com archive is called cardfind.exe and the
executable is 3link-id.exe. The readme.txt file says it should detect
the 3c905 family.
Windows doesn't seem to care how the card is configured and I didn't find
any reference as to what mode it is in.
So the problem of whether the NIC can talk to the modem isn't resolved.
Perhaps someone familiar with how Dell configures their intigrated
network cards can tell us which mode they are in and how it can be
changed. I've asked (email) tech support, too.
>>
>> Also, since I don't know any DNS addresses, I can't make entires in
>> resolv.conf. I don't think this matters at this point.
>
>dhcpd will (or should) do this when it contacts the dhcp server from your
>ISP. Routes will also be added automaticly as well.
>
>All of the above presumes your ISP provides a dynamic IP#, IF you have been
>given a "static IP#" then you must use ifconfig to configure eth0 to talk
>to the modem and add routes yourself as well as edit /etc/resolv.conf to
>reflect the nameserver addressess.
>
I don't think there is doubt that @home in Mt. View CA supplies dynamic
IP addresses--the Windows configuration (which works) verifies this.
>>
>> The loopbabk device is installed and has it's entry in /etc/hosts and
>> shows in ifconfig and route.
>
>This has little bearing on the presant problem.
>
>>
>> Likewise, there is no entry in /etc/networks beside localnet.
>>
>> So if anyone can give me things to try, I'd appreciate.
>>
>> In regard to it's performance in Windows, I'm a bit disappointed--speeds
>> seem to average around 35 Kbytes/sec on ftp recieve transfers.
>
>30Kbytes/sec is a so called 256k link 60Kbytes/sec = 500K link, 1Mb/sec is
>then 120Kb/sec (I hope i have that correct) .
>Just what speed should the link be.?? if you dont know ask your provider.
>
@home says spped up to 100 time a 56K modem. That would means max speed
around 560Kbytes/sec. So 30Kbytes/sec is a bit disapointing and I've
been told that this speed is pretty much average.
-
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
