Horst Lueck wrote: >Mandrake 8.1; RCA 'Broadband' modem w/o obvious model#, CAT5-to-NIC > >To those of you who went to Portland last night instead of coming to the >clinic: I recently got ATT cable; the service guy got it all running on my >Win98 partition, but w/o leaving any documentation. The only info I found >is from the win registry (attached at bottom). > I am using redhat with this same (well at least similar) modem on ATT. When my installer left, I got a pink work order sheet that gave me a lot of info, IP addresses and such. Maybe you've already looked, but you could try to find this.
> My mdk 8.1 ran fine last night on the "Emerald Network"(thanks to bobVP >and Cory) with static IP using the same (and only NIC). Now, over my cable >modem (trying various settings) I was not able to get configured as DHCP >client (it fails pretty fast w/o long search). > I had problems getting DHCP to work with 'pump'. I had luck running dhcpcd (the dchcp client daemon). You can try this out on the command line try something like 'dhcpcd -h <your hostname ATT gave you> -i <your ethernet interface>. So if ATT gave you hostname c576849-d and your NIC is eth0, dhcpcd -h c576849-d -i eth0. > > The local IP I got from ATT remained the same from the beginning on >though I had my machine turned off for more than 1 day. I can even ping my >NIC under windos with the cable modem power turned off. > Is Windows configured using DHCP? It probably should be. You might want to go through the windows network configurations screens and see what you can glean from these. > > So I tried to make a static connection using the data I pulled out of the >win-registry (gateway and dns). That failed too. Interestingly again, when >I use my dialup modem to ssh to efn and then ping 'my ATT IP' from efn >shell I get a quick positive response --even if my cable modem power is >turned off!? (I can also ping some other ATT clients in the same subnet, >but not all within the subnet, so I conclude that ATT's response is >*somewhat* reasonable) > Ok, the fact that you can ping the IP you believe you have from an outside public location when your cable modem is turned off is indicating to me that you don't have the IP you think you do. The fact that it responds indicates that someone else has that IP. Remember that ATT's service is by default DHCP, and they are free to shift people around whenever they like. I got moved to a different address a couple days ago, although that's the first time since the excite@home switch. By the way, I tried your experiment just to be sure, and I cannot ping my IP from an outside location when the modem is turned off. If you want to be really sure, unplug the thing and try it again. I think you need to get DHCP working under mandrake, play around with that. Once you feel confident that it's working, if you're still having problems, I'd look at routing issues, but there is no point fixing that until you're sure you are getting the correct address assigned. > > So what does ATT do with my to-and-from IP packets ??? > - or do I need to take a class in routing 101 ? ... or in gatewading? > >Since kbob alway askes for 'route -n' and 'ifconfig' I have attached a few >clips. > >I am ready to pull my hair ... the little bit that's left! >^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >
