Ok, it's not dhcp, 'cause cox@home and cox@work doesn't use that and it is turned off on the win box that works just fine. All the IP addresses are just hard coded. No WINS no DHCP. Its not the cable modem reset 'cause there is no reset button on the back and I've power cycled the modem and it makes no difference. The Linux documentation project cable modem howto is filled with all kinds of good information on cable providers other than cox@home/work. I bought the Linux Network Administrator's Guide, even though it doesn't seem to have much on this, but does have a lot on other things and a nice quick reference for all the *nix type commands that I'm not used to. Tonight I will try to get the ifconfig eth0 result and Andy K.'s suggestions:
route del 0.0.0.0 - gets rid of that 0.0.0.0 entry route del 24.15.132.128 - gets rid of that false entry route add 24.15.132.129 dev eth0 - adds 24.15.132.129 via eth0 route add default gw 24.15.132.129 dev eth0 - adds default gw 24.15.132.129 and interface eth0
...except that I know that first route del will generate some error message... I'll get the exact text this time.... Is there anyone who has done this in the San Diego area that I could offer to pay a small amount to (or dinner, or some sort of trade) in return for coming over to the house and saying "Oh, here's the problem, you have the framastan cross linked with the whatsit..." I'm really frustrated. --- James Newton mailto:jamesnewton@geocities.com 1-619-652-0593 -----Original Message----- From: pic microcontroller discussion list [mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of James Newton Sent: Tuesday, June 06, 2000 09:05 To: PICLIST@MITVMA.MIT.EDU Subject: Re: [OT]: Sucking linux at 1am Importance: Low How is the cable modem connected to the Linux box? Is it via an ethernet card? the Cable modem, and each of the machines (the Linux box and two Windows boxes) are all connected at a 5 port hub. All that is known good. I have the Windows boxes turned off while working with the Linux box How does it set up the pc in the previous config? As described. The Win server is 24.15.132.183 with a netmask of 255.255.255.128 gateway 24.15.132.129 you just type it in and it works... Is it using DHCP? If I remember correctly, the Win server has DHCP and WINS off... but I will check that. I'll also check the /etc/hosts file Right now, I'm just trying to get the Linux box to talk to the cable modem and internet... there IS NO internal network. When I get to that point, I'd like to avoid a second ethernet card, but it may be worth it for IP masq. I'm not trying to start mail or httpd at this point. I will look at the Cable Modem How To, thanks for reminding me of its existance, I'll bet that will do it for me. --- James Newton mailto:jamesnewton@geocities.com 1-619-652-0593 -----Original Message----- From: pic microcontroller discussion list [mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of John C. Frenzel Sent: Tuesday, June 06, 2000 07:43 To: PICLIST@MITVMA.MIT.EDU Subject: Re: [OT]: Sucking linux at 1am > Ok, I've got lots of cool things working on the Linux box but I could see > that running the Linux box behind a Windows proxy was going to prevent > several of the next steps from getting taken... so... shut down the Windows > server, reconfig the Linux box to directly connect to the cable modem and... > > ..why does it keep adding a route that is completely wrong? > > Cox@Home says that I'm to be 24.15.132.183 with a netmask of 255.255.255.128 > broadcast 24.15.132.255 gateway 24.15.132.129 How is the cable modem connected to the Linux box? Is it via an ethernet card? How does it set up the pc in the previous config? Is it using DHCP? If it is, then the easiest way to interface it to the linux box is directly with a second ethernet card. eth1 to the cable modem and eth0 to the local hub for the internal network. Take a look at the Cable Modem How To if you haven't done so. It is packed with ideas. > > So I put all that in to the nice xwindows version of linixconf under eth0 > (well..no.. the gateway was under what? basic host information?) host name > nix.massmind.org default gateway 24.15.132.129 and I restart the box. Until the routing is working don't even mess with mail and Apache you are just wasting your time. > > mail and httpd won't start. Three finger salute, interactive boot, skip > those two, start looking for what I did wrong. > ifconfig eth0 looks just peachy. route -n shows (I can't run the Linux box > at the same time and I'm doing this from memory at 1am) > Destination Gateway Genmask Flags Metric Ref iface > 24.15.132.183 0.0.0.0 255.255.255.0 UH 0 0 eth0 > 24.15.132.128 0.0.0.0 255.255.255.128 U 0 0 eth0 > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 lo > 0.0.0.0 24.15.132.129 0.0.0.0 UG 0 0 eth0 > > I can ping 24.15.132.183 and 127.0.0.1 but not 24.15.132.129 or anything > else. That is all within your own machine. 127.0.0.1 is the loopback interface and the other is the eth0 card. 0.0.0.0 is the representation of the default route. > > So the questions are: What the hell is that 24.15.132.128 0.0.0.0 > 255.255.255.128 line and where is it coming from and why can't I delete it? > I'm trying 10000 variations of route del 24.15.132.128 and I always get some > "process doesn't exist" message. Get out of the X-windows interface and go to the command line. Look at the /etc/hosts file. This is read at startup to make your routing table. If this is a DHCP setup, then DHCP is possibly putting it there. > > Could some one please point out the obvious stupid mistake or nix-newbie > misunderstanding I'm trapped in this time? I know this just isn't that hard. > It can be this hard. This is a rather complex deal. I would break the problem down like this: 1) Bring up the Linux machine and get it working to the point of being able to ping it from another machine on the local net. Win95/98 is easy to use to do this. That way you know the routing table is heading in the right direction. 2) Find out what the cable modem is expecting in terms of DHCP and what you need to talk to it. If you got Win95/98 working with it, look at the settings. You will need to emulate this by running DHCP on the linux box. When this is working, you will be able to ping the outside world. You will need to config the DNS stuff also. 3) Get the howto's and read them. 4) Look at www.linuxrouter.org The archives are full of stuff like this 5) Books by O'Reilly are a lifesaver esp. TCP/IP Network Administration (the crab) and Linux Network Administrator's Guide Good Luck, John