Hi Henry.
Quoting Henry Harpending
On Tue, Jun 22, 2004 at 12:54:14AM +0000, Jorge Manuel B. S. Vicetto wrote:
are your machines capable to ping the printers on the other subnet? From our discussion I'm supposing they can't. If not, it has to be related to routing. Can you show us the routing table on one of the machines and the ip configuration of one of the printers? And can you post a traceroute from one of the machines to a printer?
Jorge you have the patience of Job. I have converted the two subnets of my server to be 192.168.1/24 and 192.168.0/24. So here is the server routing table:
I'm not quite that patient! ;-) I just like networking and everything related to it and feel that I may be able to help others - or so I would like to think.
Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 192.168.1.2 255.255.255.0 UG 0 0 0 eth0 192.168.0.0 192.168.0.2 255.255.255.0 UG 0 0 0 wlan0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
The two network cards have addresses 192.168.1.2 (eth0) and 192.168.0.2 (wlan0).
From a machine attached to wlan0 I can ping both cards, I can ping any machine on wlan0, but I cannot ping anything attached to eth0. The failure is symmetric: from a laptop attached to eth0 I can ping anything attached to eth0, I can ping both network cards, but I cannot ping anything attached to wlan0.
Here is the routing table from a laptop attached to eth0 (i.e. the subnet where I want to put the printers):
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.0.2 0.0.0.0 UG 0 0 0 eth0
Ander has already identified the problem. Don't forget to update the netmask for all stations and printers.
I am not sure what traceroutes I should report since I can't get any routes to work!
For future reference, a traceroute from this station to a printer would
let you
see that the station wasn't contacting the gateway. Traceroutes are a very
powerful tool to discover routing problems.
Here's an example:
At home I have a server, atlantis, with the 172.28.2.5 IP address and a
gateway,
fw, with the 172.28.2.2 IP address.
fw:~ # ip addr
1: lo:
Best regards, Henry
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
I hope this helps someone to get a better understanding on networking and routing. ------------------------------------------ Jorge Manuel B. S. Vicetto Network Manager and Systems Administrator Angra do Heroísmo Nursing School (ESEnfAH) ------------------------------------------ ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.