Re: [opensuse] Home network problem
Sorry about that. I did not intend for this to be a private response.
I have a problem with suse 8.2 and my home network. There is a windoze> XP machine on the network that is not experiencing any
the internet.
The suse box can ping the router and open the administration of the network through the default gateway of the router. Any attempt to reach the internet results is www..... can not be found. /etc/resolv.conf changes dynamically and shows the ISP in the search line and
On Monday 04 December 2006 20:04, eharrison@tampabay.rr.com wrote: problems reaching their 2
nameservers, also. Still not joy.
Any ideas?
Can you ping outside the router? Like, ping 207.69.188.186 (an Earthlink nameserver), or ping google.com?
No. I get one of 2 errors. Network unreachable, or ping just sits there with 100% packet loss.
On Monday 04 December 2006 20:36, eharrison@tampabay.rr.com wrote:
No. I get one of 2 errors. Network unreachable, or ping just sits there with 100% packet loss. Does the machine have a hard IP address, or does it get it from dhcp?
Can you ping the suse box from your XP box? Can you ping the XP box from your suse box? If yes to both the above, then your router is not forwarding the packets from your suse box. Is this setup a dialin router, or cable modem? -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
----- Original Message -----
From: M Harris
On Monday 04 December 2006 20:36, eharrison@tampabay.rr.com wrote:
No. I get one of 2 errors. Network unreachable, or ping just sits there with 100% packet loss. Does the machine have a hard IP address, or does it get it from dhcp?
Can you ping the suse box from your XP box?
Can you ping the XP box from your suse box?
If yes to both the above, then your router is not forwarding the packets from your suse box.
Is this setup a dialin router, or cable modem?
The connection is through a cable modem. I didn't try pinging the boxes back and forth. BTW, what setting would keep the router from forwarding the linux packets? Ed -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 04 December 2006 20:48, eharrison@tampabay.rr.com wrote:
The connection is through a cable modem. I didn't try pinging the boxes back and forth. Make sure that your internal network is working first, then outbound.
BTW, what setting would keep the router from forwarding the linux packets? That depends on the router. Mine is another Linux box through a shylink switch to the internal net, and nic to the outside... is your router home-made (linux box, other) or is it a hardware package like the linksys, or other?
-- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
----- Original Message -----
From: M Harris
The connection is through a cable modem. I didn't try pinging
On Monday 04 December 2006 20:48, eharrison@tampabay.rr.com wrote: the boxes
back and forth. Make sure that your internal network is working first, then outbound.
BTW, what setting would keep the router from forwarding the linux packets?
That depends on the router. Mine is another Linux box through a shylink switch to the internal net, and nic to the outside... is your router home-made (linux box, other) or is it a hardware package like the linksys, or other?
It is a linksys router with dhcp and firewall. Ed -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 04 December 2006 21:30, eharrison@tampabay.rr.com wrote:
home-made (linux box, other) or is it a hardware package like the linksys, or other?
It is a linksys router with dhcp and firewall. ok. well, give me a note when you get back home. I can have you check a couple of things.
-- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 04 December 2006 22:30, eharrison@tampabay.rr.com wrote:
That depends on the router. Mine is another Linux box through a shylink switch to the internal net, and nic to the outside... is your router home-made (linux box, other) or is it a hardware package like the linksys, or other?
It is a linksys router with dhcp and firewall.
What is the result of a route -n command. Sounds like your routing in the linux box may be screwed up. Try adding: route add default gw <ip of router> ethx where x is usually eth0 or eth1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
M Harris wrote:
On Monday 04 December 2006 20:48, eharrison@tampabay.rr.com wrote:
The connection is through a cable modem. I didn't try pinging the boxes back and forth.
Make sure that your internal network is working first, then outbound.
BTW, what setting would keep the router from forwarding the linux packets?
That depends on the router. Mine is another Linux box through a shylink switch to the internal net, and nic to the outside... is your router home-made (linux box, other) or is it a hardware package like the linksys, or other?
If the box passes packets from Windows, it should also do so for Linux. There's no such thing as "Linux packets". The problem is either routing or DNS resolution in the system with the problem. If you can ping by IP address, but not host name, it's DNS. If you can't by IP either, it's routing. If you can't even ping a local IP, then it's some configuration issue with the NIC. A useful tool to find out what the problem is, is Ethereal. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 05 December 2006 07:25, James Knott wrote: > M Harris wrote: > > On Monday 04 December 2006 20:48, eharrison@tampabay.rr.com wrote: > >> The connection is through a cable modem. I didn't try pinging the boxes > >> back and forth. > > > > Make sure that your internal network is working first, then outbound. > > > >> BTW, what setting would keep the router from forwarding the linux > >> packets? * see next comment > > That depends on the router. Mine is another Linux box through a shylink > > switch to the internal net, and nic to the outside... is your router > > home-made (linux box, other) or is it a hardware package like the > > linksys, or other? > > If the box passes packets from Windows, it should also do so for Linux. > There's no such thing as "Linux packets". I interpreted this question to be shorthand for "... packets from the Linux box?" > The problem is either routing > or DNS resolution in the system with the problem. If you can ping by IP > address, but not host name, it's DNS. If you can't by IP either, it's > routing. If you can't even ping a local IP, then it's some > configuration issue with the NIC. A useful tool to find out what the > problem is, is Ethereal. I /do/ recall a thread in the last year or two here where we discovered a small but significant difference between Linux and M$ "ping" ... one being accepted and the other ignored, causing great consternation to the OP. This may not be the case here, but forewarned is forearmed. I think /usr/sbin/mtr was the solution. Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 05 December 2006 7:48 am, Carl Hartung wrote:
I /do/ recall a thread in the last year or two here where we discovered a small but significant difference between Linux and M$ "ping" ... one being accepted and the other ignored, causing great consternation to the OP.
This may not be the case here, but forewarned is forearmed. I think /usr/sbin/mtr was the solution.
Carl
The ping issue between Windows vs Linux is the size of the ICMP packet. I believe a router (in that thread a while back) was refusing Linux pings, based on the size. As far as I know, this would only affect equipment requiring Windows based pings. A ping to a normal router should return as expected regardless of the OS. - James W. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
James Wright wrote:
On Tuesday 05 December 2006 7:48 am, Carl Hartung wrote:
I /do/ recall a thread in the last year or two here where we discovered a small but significant difference between Linux and M$ "ping" ... one being accepted and the other ignored, causing great consternation to the OP.
This may not be the case here, but forewarned is forearmed. I think /usr/sbin/mtr was the solution.
Carl
The ping issue between Windows vs Linux is the size of the ICMP packet. I believe a router (in that thread a while back) was refusing Linux pings, based on the size. As far as I know, this would only affect equipment requiring Windows based pings. A ping to a normal router should return as expected regardless of the OS.
- James W.
Yep, the only difference is the size. In general, Microsoft systems use 32 bytes as default packet size, Unix systems 64 and Netware systems 40. Usually, increasing packet size reveals router issue. You can check it using the -L option in Windows and the -s option in Linux. Jan Kalcic -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 07:25 AM 12/5/2006 -0500, James Knott wrote:
M Harris wrote:
On Monday 04 December 2006 20:48, eharrison@tampabay.rr.com wrote:
The connection is through a cable modem. I didn't try pinging the boxes back and forth.
Make sure that your internal network is working first, then outbound.
BTW, what setting would keep the router from forwarding the linux packets?
That depends on the router. Mine is another Linux box through a shylink switch to the internal net, and nic to the outside... is your router home-made (linux box, other) or is it a hardware package like the
linksys, or
other?
If the box passes packets from Windows, it should also do so for Linux. There's no such thing as "Linux packets". The problem is either routing or DNS resolution in the system with the problem. If you can ping by IP address, but not host name, it's DNS. If you can't by IP either, it's routing. If you can't even ping a local IP, then it's some configuration issue with the NIC. A useful tool to find out what the problem is, is Ethereal.
I've been following this thread for a while, and one thing that hasn't been mentioned, is incompatibility of Linux with the Ethernet "card" in the machine. This machine has a Broadcom ethernet connection built into the MOBO, and Linux 10.0 apparently doesn't like it. Whatever is in the other computer, Linux likes fine. (I'm almost sure that SuSE 8.2 worked with the Broadcom components, but that's quite a while ago, and I don't even think I have a disk for that anymore, to test it out.) --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Doug McGarrett wrote:
M Harris wrote:
On Monday 04 December 2006 20:48, eharrison@tampabay.rr.com wrote:
The connection is through a cable modem. I didn't try pinging the boxes back and forth.
Make sure that your internal network is working first, then outbound.
BTW, what setting would keep the router from forwarding the linux packets?
That depends on the router. Mine is another Linux box through a shylink switch to the internal net, and nic to the outside... is your router home-made (linux box, other) or is it a hardware package like the
At 07:25 AM 12/5/2006 -0500, James Knott wrote: linksys, or
other?
If the box passes packets from Windows, it should also do so for Linux. There's no such thing as "Linux packets". The problem is either routing or DNS resolution in the system with the problem. If you can ping by IP address, but not host name, it's DNS. If you can't by IP either, it's routing. If you can't even ping a local IP, then it's some configuration issue with the NIC. A useful tool to find out what the problem is, is Ethereal.
I've been following this thread for a while, and one thing that hasn't been mentioned, is incompatibility of Linux with the Ethernet "card" in the machine. This machine has a Broadcom ethernet connection built into the MOBO, and Linux 10.0 apparently doesn't like it. Whatever is in the other computer, Linux likes fine. (I'm almost sure that SuSE 8.2 worked with the Broadcom components, but that's quite a while ago, and I don't even think I have a disk for that anymore, to test it out.)
--doug
I wish I knew, but have you checked if the gateway value is set correctly. I found out that uner 10.1 AMD64 bit version, the gateway is not set properly. Unit yu manually enter the gateway, you could not ping outside even though the DNS was setup correctly. -- Joseph Loo jloo@acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Bruce Marshall -
Carl Hartung -
Doug McGarrett -
eharrison＠tampabay.rr.com -
James Knott -
James Wright -
Jan Kalcic -
Joseph Loo -
M Harris