8.2 Can't get to network or network get in
Hi ALL, Have an odd prob. I had to replace my DSL Gateway Router with a similar model from SMC. The new router is a DHCP server like the old one and issues IP addrs of different values than the old one. I have two 8.2 SuSE PCs and as I boot them I see each ask for and get IP addrs 192.xxx.xxx.180 and 192.xxx.xxx.181 These are not the ones that the old router issued to these machines. Now the prob== One 8.2 pc works fine but the other one (181) can't get to the net, but looking at ifconfig for each looks the same! 181 can't ping or be pinged but while pinging I see the NIC LED flash in time with the ping. "Unknown host" is what the browsers say. I can't think of anything that changed on the failing PC except the IPaddr; it used to get ...xxx.185 Can anyone offer some suggestions? -- -- Proud to use SuSE Linux, since 5.2 Loving using SuSE Linux 8.2 MyBlog http://vancampen.org/blog/ "Non Sanz Capsicum" "Not Without Cayenne" --
On Tuesday, July 22, 2003, at 10:33 PM, Peter B Van Campen wrote:
Hi ALL,
Have an odd prob. I had to replace my DSL Gateway Router with a similar model from SMC. The new router is a DHCP server like the old one and issues IP addrs of different values than the old one. I have two 8.2 SuSE PCs and as I boot them I see each ask for and get IP addrs 192.xxx.xxx.180 and 192.xxx.xxx.181 These are not the ones that the old router issued to these machines.
Now the prob== One 8.2 pc works fine but the other one (181) can't get to the net, but looking at ifconfig for each looks the same! 181 can't ping or be pinged but while pinging I see the NIC LED flash in time with the ping. "Unknown host" is what the browsers say. I can't think of anything that changed on the failing PC except the IPaddr; it used to get ...xxx.185
Can anyone offer some suggestions? -- --
Proud to use SuSE Linux, since 5.2 Loving using SuSE Linux 8.2
MyBlog http://vancampen.org/blog/
"Non Sanz Capsicum" "Not Without Cayenne"
Just as a double check, make sure the cables a fully seated. If that's not it try another port on the switch. I might have a bad port. Not trying to belittle. I just know those are the most common problems and I have to be reminded to check them all the time. will
On Wednesday 23 July 2003 09:42 am, The Purple Tiger wrote:
On Wednesday 23 July 2003 04:33, Peter B Van Campen wrote:
get to the net, but looking at ifconfig for each looks the same! 181
What is the output of route -n for both machines? Hi ,
Working 8.2 PC: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.123.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.123.254 0.0.0.0 UG 0 0 0 eth0 Failing 8.2 PC is same PeterB -- -- Proud to use SuSE Linux, since 5.2 Loving using SuSE Linux 8.2 MyBlog http://vancampen.org/blog/ "Non Sanz Capsicum" "Not Without Cayenne" --
On Tuesday 22 July 2003 10:33 pm, Peter B Van Campen wrote:
Hi ALL,
Have an odd prob. I had to replace my DSL Gateway Router with a similar model from SMC. The new router is a DHCP server like the old one and issues IP addrs of different values than the old one. I have two 8.2 SuSE PCs and as I boot them I see each ask for and get IP addrs 192.xxx.xxx.180 and 192.xxx.xxx.181 These are not the ones that the old router issued to these machines.
Now the prob== One 8.2 pc works fine but the other one (181) can't get to the net, but looking at ifconfig for each looks the same! 181 can't ping or be pinged but while pinging I see the NIC LED flash in time with the ping. "Unknown host" is what the browsers say. I can't think of anything that changed on the failing PC except the IPaddr; it used to get ...xxx.185
Can anyone offer some suggestions? Hi Again,
New info: I went to YAST2 >Security and Users>Firewall and turned off the firewall and removed it from the bootup. YAST turned the firewall off and the system now gets to the network and internet via it's new DHCP assigned IPaddr. So how can I get the firewall to run with this new IPAddr? The only thing that changed in this situation is that the DHCP Server issues this machine a different IPAddr than before. This feels suspiciously like a BUG; is it not reasonable to expect off-board DHCP servers to issue different IPAddrs from time to time? Ideas? Info? RTF (pls specify correct)M! ..........PeterB -- -- Proud to use SuSE Linux, since 5.2 Loving using SuSE Linux 8.2 MyBlog http://vancampen.org/blog/ "Non Sanz Capsicum" "Not Without Cayenne" --
On Fri, 2003-07-25 at 02:47, Peter B Van Campen wrote:
New info: I went to YAST2 >Security and Users>Firewall and turned off the firewall and removed it from the bootup. YAST turned the firewall off and the system now gets to the network and internet via it's new DHCP assigned IPaddr. So how can I get the firewall to run with this new IPAddr? The only thing that changed in this situation is that the DHCP Server issues this machine a different IPAddr than before. This feels suspiciously like a BUG; is it not reasonable to expect off-board DHCP servers to issue different IPAddrs from time to time? Ideas? Info? RTF (pls specify correct)M! ..........PeterB
Have you told SuSEfirewall that it's a dhcp client machine? /etc/sysconfig/SuSEfirewall2 -> FW_SERVICE_DHCLIENT ?
On Thursday 24 July 2003 07:52 pm, Anders Johansson wrote:
On Fri, 2003-07-25 at 02:47, Peter B Van Campen wrote:
New info: I went to YAST2 >Security and Users>Firewall and turned off the firewall and removed it from the bootup. YAST turned the firewall off and the system now gets to the network and internet via it's new DHCP assigned IPaddr. So how can I get the firewall to run with this new IPAddr? The only thing that changed in this situation is that the DHCP Server issues this machine a different IPAddr than before. This feels suspiciously like a BUG; is it not reasonable to expect off-board DHCP servers to issue different IPAddrs from time to time? Ideas? Info? RTF (pls specify correct)M! ..........PeterB
Have you told SuSEfirewall that it's a dhcp client machine?
/etc/sysconfig/SuSEfirewall2 -> FW_SERVICE_DHCLIENT Dear Anders,
HAH! it was set to 'no'. But that beggs a quest. ==I just went thru the YAST2 firewall setup suite, answered all questions and there was nothing there regarding DHCP. Another Q = The Firewall was running all along; but before getting this new IPAddr from the DHCPD in the gateway router it worked fine with FW_SERVICE_DHCPCLIENT=no. hmmmm Curiosior and curiosior. But I am learning PeterB -- -- Proud to use SuSE Linux, since 5.2 Loving using SuSE Linux 8.2 MyBlog http://vancampen.org/blog/ "Non Sanz Capsicum" "Not Without Cayenne" --
participants (4)
-
Anders Johansson -
Peter B Van Campen -
The Purple Tiger -
will