Strange networking woes
Hi all, I am trying to install Debian Etch on a Pentium III machine. It is connected to a switch which is connected to a router. Both switch and router are confirmed to be working perfectly. Debian, however, is acting strangely with the network. The machine sees the network hardware. That is, lspci returns the ethernet controller, and plugging the ethernet cord in and out returns a message indicating that it was detected. However, pinging anyone inside the network (including 192.168.1.1 -- the router) returns in Destination Host Unreachable errors. Ideally, I'd like the machine to use a static IP address (192.168.1.154), like my other Etch server, but I would be content with DHCP if need be. Currently, /etc/network/interfaces says: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp Running dhclient eth0 does not work (although ifconfig does show it, it does not have either inet addr nor inet6 addr in it). Does anyone have any ideas? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Strange networking woes
What is in the /etc/resolv.conf file? Does it point to the router or the switch? -- Rodney D. Myers [EMAIL PROTECTED] Registered Linux User #96112 ICQ#: AIM#: YAHOO: 18002350 mailman452 mailman42_5 They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. Ben Franklin - 1759 signature.asc Description: PGP signature
Re: Strange networking woes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/23/06 17:37, Leonid Grinberg wrote: Hi all, I am trying to install Debian Etch on a Pentium III machine. It is connected to a switch which is connected to a router. Both switch and router are confirmed to be working perfectly. Debian, however, is acting strangely with the network. The machine sees the network hardware. That is, lspci returns the ethernet controller, and plugging the ethernet cord in and out returns a message indicating that it was detected. However, pinging anyone inside the network (including 192.168.1.1 -- the router) returns in Destination Host Unreachable errors. Ideally, I'd like the machine to use a static IP address (192.168.1.154), like my other Etch server, but I would be content with DHCP if need be. Currently, /etc/network/interfaces says: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp Try it with a static address. Define the netmask, gateway, etc. Here's what mine looks like: auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.1.10 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.251 dns-nameservers 68.11.16.25 68.11.16.30 68.1.208.25 dns-search homelan Running dhclient eth0 does not work (although ifconfig does show it, it does not have either inet addr nor inet6 addr in it). Does anyone have any ideas? - -- Ron Johnson, Jr. Jefferson LA USA Is common sense really valid? For example, it is common sense to white-power racists that whites are superior to blacks, and that those with brown skins are mud people. However, that common sense is obviously wrong. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFFcI1S9HxQb37XmcRApEdAKCtOJJD0j2/brmEQxRjxYcP0n7BRQCfbZBf bil67ITFGdCaj5mggAM9kCs= =1stX -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Strange networking woes
Thank you for your support, everyone! After some experimentation, I realized that the problem was that the computer was not realizing that it was on a switch. Connecting it directly to the router fixed the problem. However, I would still like it better on the switch. The problem I think is that it needs a different gateway than the 192.168.1.1 of the router. Does anyone know how I would tell it to use the switch? -- Leonid -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Strange networking woes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/23/06 21:05, Leonid Grinberg wrote: Thank you for your support, everyone! After some experimentation, I realized that the problem was that the computer was not realizing that it was on a switch. Connecting it directly to the router fixed the problem. However, I would still like it better on the switch. The problem I think is that it needs a different gateway than the 192.168.1.1 of the router. Does anyone know how I would tell it to use the switch? Huh? Switches don't have IP addresses. (Well, ok, managed switches do, but that's only for managing them...) My LAN is configured like you want yours to be: PCs plug into switch, and the switch plugs into the router. What might be the problem is that you are using the uplink port (on the switch) when you shouldn't, or are using a cross-over cable when you shouldn't. - -- Ron Johnson, Jr. Jefferson LA USA Is common sense really valid? For example, it is common sense to white-power racists that whites are superior to blacks, and that those with brown skins are mud people. However, that common sense is obviously wrong. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFFe4pS9HxQb37XmcRAsRDAJ9zPQ99nljTpAG/3dydr1G/bwjrBgCfb8J+ CsWyVx5k7SaggY+O7FQH4bM= =70Io -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Strange networking woes
[sorry Ron, forwarding to list] Huh? Switches don't have IP addresses. (Well, ok, managed switches do, but that's only for managing them...) OK, that's what I thought. My LAN is configured like you want yours to be: PCs plug into switch, and the switch plugs into the router. What might be the problem is that you are using the uplink port (on the switch) when you shouldn't, or are using a cross-over cable when you shouldn't. Actually, that fixed it (the uplink port)! My mistake. Thanks a lot! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
