Re: [SLE] routing between subnets

newer
SMBFS too many open files

older
KDM - How configure sessions?

Henry Harpending

21 Jun 2004 21 Jun '04

01:58

On Sunday 20 June 2004 18:13, Jorge Manuel B. S. Vicetto wrote:

...

Hi Henry.

Quoting Henry Harpending :

...
We recently converted our home to wireless, orphaning 2 hp-jetdirect printers. I would like to make them accessible by wiring them to one of our computers. Here is what I did:

Our wireless network has addresses 192.168.. with the server being 192.168.0.2. I ran a cable to one printer from our server from the internet card, assigning it the ip number 10.0.0.1/24 and naming 10.0.0.1 as gateway. I attached the jetdirect to this card as 10.0.0.5 and everything works fine from the server. But how do I access this 10.0.. net from another computer?

I tried telling another machine that it could reach 10.0.. via the gateway 192.168.0.2 and no luck. It can ping 10.0.0.1, the card, but it can't ping the 10.0.0.5 printer. I tried adding a route to 10.0.0.5/32 gateway 10.0.0.1 to the other computer's routing table, but no go.

Is your routing table ok ?

netstat -nr or ip route

...
I have the same failure to reach 10.0.0.5 whether or not IP forwarding is turned on at the server 192.168.0.2.

Are you setting the ip forwarding by

cat 1 > /proc/sys/net/ipv4/ip_forward

?

If this doesn't help, try using traceroute to find what's going on.

Here are the results of what you suggest, from the server 192.168.0.2:; #cat /proc/sys/net/ipv4/ip_forward 1 #netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.0.0.0 10.0.0.1 255.255.255.0 UG 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 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 #traceroute 10.0.0.5 traceroute to 10.0.0.5 (10.0.0.5), 30 hops max, 40 byte packets 1 10.0.0.5 1.748 ms 1.779 ms 1.777 ms I can't see anything wrong here but I really don't know what I am doing. BTW does anyone know what 169.254.0.0 is? Thanks, Henry Harpending

Show replies by date

Anders Johansson

21 Jun 21 Jun

02:06

New subject: [SLE] routing between subnets

On Monday 21 June 2004 03.58, Henry Harpending wrote:

...

10.0.0.0 10.0.0.1 255.255.255.0 UG 0 0 0 eth0

This line looks odd. Does this machine have 10.0.0.1 assigned to eth0?

...

I can't see anything wrong here but I really don't know what I am doing.

What does the routing table look like on 10.0.0.5? Does it know how to reach 192.168.0.0?

...

BTW does anyone know what 169.254.0.0 is?

Something suse dreamed up for 9.1 to help it communicate with windows machines. Win-boxes default to that subnet if they aren't configured

Jorge Manuel B. S. Vicetto

02:18

New subject: [SLE] routing between subnets

Quoting Henry Harpending :

...

On Sunday 20 June 2004 18:13, Jorge Manuel B. S. Vicetto wrote:

...
Hi Henry.

<snip>

...

Here are the results of what you suggest, from the server 192.168.0.2:;

#cat /proc/sys/net/ipv4/ip_forward 1

So the server is forwarding packets.

...

#netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.0.0.0 10.0.0.1 255.255.255.0 UG 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 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 #traceroute 10.0.0.5 traceroute to 10.0.0.5 (10.0.0.5), 30 hops max, 40 byte packets 1 10.0.0.5 1.748 ms 1.779 ms 1.777 ms

Try the traceroute from one of the stations so that we can see what's going on with the routing. If you could put a station on the switch and do a traceroute on the other way, would also help. BTW, did you remember to configure the default gateway of the PRINTERS as the server? If not, that's your problem! Packets go from the stations to the printers, but don't return!

...

I can't see anything wrong here but I really don't know what I am doing. BTW does anyone know what 169.254.0.0 is?

Isn't it the IP class that Microsoft uses to automatically assign IP addresses to stations connected to a network without DHCP servers?

...

Thanks, Henry Harpending

-- 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

------------------------------------------ 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.

Henry Harpending

17:19

New subject: [SLE] routing between subnets

On Mon, Jun 21, 2004 at 02:18:51AM +0000, Jorge Manuel B. S. Vicetto wrote:

...

Quoting Henry Harpending :

...
Here are the results of what you suggest, from the server 192.168.0.2:;

#cat /proc/sys/net/ipv4/ip_forward 1

So the server is forwarding packets.

...
#netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.0.0.0 10.0.0.1 255.255.255.0 UG 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 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 #traceroute 10.0.0.5 traceroute to 10.0.0.5 (10.0.0.5), 30 hops max, 40 byte packets 1 10.0.0.5 1.748 ms 1.779 ms 1.777 ms

Try the traceroute from one of the stations so that we can see what's going on with the routing. If you could put a station on the switch and do a traceroute on the other way, would also help. BTW, did you remember to configure the default gateway of the PRINTERS as the server? If not, that's your problem! Packets go from the stations to the printers, but don't return!

I put a laptop on the 10.0.0.1 network card, set it up the same as the printer with gateway 10.0.0.1, and experience the same behavior. 192.168.0.2 on wlan0, server / other 192.168.0. machines DSL = 192.168.0.1 \ 10.0.0.1 on eth0 printer attached as 10.0.0.5 Perhaps I need to try to give the DSL router a second IP address? Thanks, Henry

Jorge Manuel B. S. Vicetto

18:02

New subject: [SLE] routing between subnets

Henry, once more sorry you getting this twice!!! Reply to the list and not to the author!!! If I just didn't forgot it. ;-) Quoting Henry Harpending : <snip>

...

192.168.0.2 on wlan0, server / other 192.168.0. machines DSL = 192.168.0.1 \ 10.0.0.1 on eth0 printer attached as 10.0.0.5

Perhaps I need to try to give the DSL router a second IP address?

Henry, are you trying to route at the DSL? If so, you must configure the router and use its address as the gateway! Your DSL must support acting as a router or you won't be able to do that. I am currently wainting for a Linksys WRT54G just to have a similar configuration to yours - it's coming... ;-) I had interpreted that your server was doing the routing. It does have a wireless nic and a wired nic, right? If not, then you can't use it as a router!!!

...

Thanks, 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

Henry Harpending

22 Jun 22 Jun

00:34

New subject: [SLE] routing between subnets

On Mon, Jun 21, 2004 at 06:02:16PM +0000, Jorge Manuel B. S. Vicetto wrote:

...

are you trying to route at the DSL? If so, you must configure the router and use its address as the gateway! Your DSL must support acting as a router or you won't be able to do that. I am currently wainting for a Linksys WRT54G just to have a similar configuration to yours - it's coming... ;-) I had interpreted that your server was doing the routing. It does have a wireless nic and a wired nic, right? If not, then you can't use it as a router!!!

No, the DSL is working fine. My problem remains that I can't get traffic on my eth0 card to be forwarded out the wlan0 card to the DSL. Interestingly I cannot get traffic on wlan0 to be forwarded out via eth0 either. [For those coming late to this disaster, my home network is wireless, and I am trying to hook up several jetdirect printers via eth0 on my home server. So I have two network cards in the server, and machines on each subnet can ping each other, they can ping both cards in my server, but the server won't route traffic between the two cards. I do have IP forwarding turned on.] There has to be something simple I am missing...... Thanks, Henry

Jorge Manuel B. S. Vicetto

00:54

New subject: [SLE] routing between subnets

Quoting Henry Harpending :

...

On Mon, Jun 21, 2004 at 06:02:16PM +0000, Jorge Manuel B. S. Vicetto wrote:

...
are you trying to route at the DSL? If so, you must configure the router and use its address as the gateway! Your DSL must support acting as a router or you won't be able to do that. I am currently wainting for a Linksys WRT54G just to have a similar configuration to yours - it's coming... ;-) I had interpreted that your server was doing the routing. It does have a wireless nic and a wired nic, right? If not, then you can't use it as a router!!!

No, the DSL is working fine. My problem remains that I can't get traffic on my eth0 card to be forwarded out the wlan0 card to the DSL. Interestingly I cannot get traffic on wlan0 to be forwarded out via eth0 either.

[For those coming late to this disaster, my home network is wireless, and I am trying to hook up several jetdirect printers via eth0 on my home server. So I have two network cards in the server, and machines on each subnet can ping each other, they can ping both cards in my server, but the server won't route traffic between the two cards. I do have IP forwarding turned on.]

Henry, 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?

...

There has to be something simple I am missing......

Thanks, 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

Henry Harpending

01:15

New subject: [SLE] routing between subnets

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: 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 I am not sure what traceroutes I should report since I can't get any routes to work! Best regards, Henry

Anders Johansson

01:25

New subject: [SLE] routing between subnets

On Tuesday 22 June 2004 03.15, Henry Harpending wrote:

...

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

The netmask is wrong. It should be 255.255.255.0, otherwise the machine thinks both your networks matches this rule

Henry Harpending

02:15

New subject: [SLE] routing between subnets

On Tue, Jun 22, 2004 at 03:25:23AM +0200, Anders Johansson wrote:

...

On Tuesday 22 June 2004 03.15, Henry Harpending wrote:

...
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

The netmask is wrong. It should be 255.255.255.0, otherwise the machine thinks both your networks matches this rule

I changed it, no change in behavior. I also can't get rid of the mysterious 169.254.0.0 entry: is there a file on disk where this information is kept? Thanks, Henry

Anders Johansson

03:21

New subject: [SLE] routing between subnets

On Tuesday 22 June 2004 04.15, Henry Harpending wrote:

...

On Tue, Jun 22, 2004 at 03:25:23AM +0200, Anders Johansson wrote:

...
On Tuesday 22 June 2004 03.15, Henry Harpending wrote:

...
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

The netmask is wrong. It should be 255.255.255.0, otherwise the machine thinks both your networks matches this rule

I changed it, no change in behavior.

Strange, but could you post the routing table of a machine on the other LAN? If it has a similar error, it won't know how to reply

...

I also can't get rid of the mysterious 169.254.0.0 entry: is there a file on disk where this information is kept?

Edit /etc/sysconfig/network/config, towards the end you have ## Type: string ## Default: "eth*[0-9]|tr*[0-9]|wlan[0-9]|ath[0-9]" # # Automatically add a linklocal route to the matching interfaces. # This string is used in a bash "case" statement, so it may contain # '*', '[', ']' and '|' meta-characters. # LINKLOCAL_INTERFACES="eth*[0-9]|tr*[0-9]|wlan[0-9]|ath[0-9]" You could comment it out and replace it with LINKLOCAL_INTERFACES=""

Henry Harpending

04:11

New subject: [SLE] routing between subnets

On Tue, Jun 22, 2004 at 05:21:59AM +0200, Anders Johansson wrote:

...

Strange, but could you post the routing table of a machine on the other LAN? If it has a similar error, it won't know how to reply

Here is the routing table of a W2K machine on wlan0 (192.168.0.2) of the server: Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.129 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.0 192.168.0.129 192.168.0.129 1 192.168.0.129 255.255.255.255 127.0.0.1 127.0.0.1 1 192.168.0.255 255.255.255.255 192.168.0.129 192.168.0.129 1 192.168.1.0 255.255.255.0 192.168.0.2 192.168.0.129 1 224.0.0.0 224.0.0.0 192.168.0.129 192.168.0.129 1 255.255.255.255 255.255.255.255 192.168.0.129 192.168.0.129 1 Default Gateway: 192.168.0.1 This machine can ping anthing on 192.168.0.0/24, it can ping the gateway 192.168.0.1, and it can ping eth0 in the server 192.168.1.2. It cannot ping anything on the 192.168.1.0/24 subnet attached to eth0. For reference here again is the routing table of my server: $sudo /sbin/route -n Kernel IP routing table 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 Thanks, Henry

Anders Johansson

04:52

New subject: [SLE] routing between subnets

On Tuesday 22 June 2004 06.11, Henry Harpending wrote:

...

On Tue, Jun 22, 2004 at 05:21:59AM +0200, Anders Johansson wrote:

...
Strange, but could you post the routing table of a machine on the other LAN? If it has a similar error, it won't know how to reply

Here is the routing table of a W2K machine on wlan0 (192.168.0.2) of the server:

Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.129 1

I wish I knew more about the routing logics of windows. Having this entry first in the table seems strange, since it's a catchall Could you try a tracert on this windows machine to the ip of the laptop you fixed earlier? Also, on that laptop, could you do "/sbin/tracepath 192.168.0.129"

Henry Harpending

15:25

New subject: [SLE] routing between subnets

On Tue, Jun 22, 2004 at 06:52:46AM +0200, Anders Johansson wrote:

...

Could you try a tracert on this windows machine to the ip of the laptop you fixed earlier?

Tracing route to 192.168.1.9 over a maximum of 30 hops 1 <10 ms <10 ms <10 ms HARPEND [192.168.0.2] 2 <10 ms <10 ms <10 ms 192.168.1.9 Trace complete.

...

Also, on that laptop, could you do "/sbin/tracepath 192.168.0.129"

I doesn't complete: I get 1: dellaptop.kenrey.net (192.168.1.9) 1.000ms pmtu 1500 and then it hangs. Something is working suddenly: I can communicate between the two subnets in my house. However I still cannot get from the inhouse ethernet past my server to the dsl. To recap, all IPs have prefix 192.168 DSL IP=0.1 ---------- Server wlan0 IP=0.2 Wife'sMac IP=0.22 Windows machine IP=0.DHCP eth0 IP=1.2 Jetdirect IP=1.5 Laptop IP=1.9 I can ping both ways between [0.22 or 0.DHCP] and [1.5 or 1.9]: I have no idea why I could not do this yesterday. I still cannot ping the DSL from either 1.5 or 1.9. Best regards, Henry

The Purple Tiger

18:12

New subject: [SLE] routing between subnets

On Tuesday 22 June 2004 03:15, Henry Harpending wrote:

...

I also can't get rid of the mysterious 169.254.0.0 entry: is there a file on disk where this information is kept? That might be zeroconf - I don't have a running copy of 9.1 to tell you where the files are located, but check in the networking section of YaST.

Hope this helps, Jon

Jorge Manuel B. S. Vicetto

02:15

New subject: [SLE] routing between subnets

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: mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo inet6 ::1/128 scope host 2: sit0@NONE: <NOARP> mtu 1480 qdisc noop link/sit 0.0.0.0 brd 0.0.0.0 3: eth0: mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:04:76:0f:99:59 brd ff:ff:ff:ff:ff:ff inet 172.28.2.2/24 brd 172.28.2.255 scope global eth0 inet6 fe80::204:76ff:fe0f:9959/64 scope link 4: eth1: mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:01:02:fa:e0:9e brd ff:ff:ff:ff:ff:ff inet 10.0.0.5/24 brd 10.0.0.255 scope global eth1 inet6 fe80::201:2ff:fefa:e09e/64 scope link fw:~ # If I try to contact atlantis from fw, this is what I get: fw:~ # traceroute 172.28.2.5 traceroute to 172.28.2.5 (172.28.2.5), 30 hops max, 40 byte packets 1 atlantis.acores.pt (172.28.2.5) 0.240 ms 0.000 ms 0.000 ms fw:~ # If I had two subnets with a /26 mask, so that 172.28.2.100 would be on another subnet, but didn't use the proper mask I would get something as: fw:~ # traceroute 172.28.2.100 traceroute to 172.28.2.100 (172.28.2.100), 30 hops max, 40 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 fw.acores.pt (172.28.2.2)(H!) 2970.290 ms (H!) 2968.341 ms (H!) 2966.382 ms fw:~ # At work I have some servers on a DMZ and a router at the border. When I try to traceroute an external address, my server starts by contacting my router - with the 62.48.177.209 IP address. So this resembles what you should see if your netmask and gateway were correctly configured: zeus:~ # traceroute www.yahoo.com traceroute to www.yahoo.com (216.109.118.75), 30 hops max, 40 byte packets 1 router.esenfah.pt (62.48.177.209) 2.170 ms 1.275 ms 1.504 ms 2 62.48.131.160 63.160 ms 73.028 ms 75.513 ms 3 62.48.131.81 83.119 ms 83.065 ms 85.997 ms 4 adsl-plus-PCS1.ptprime.net (62.48.131.222) 89.454 ms 92.606 ms 101.435 ms 5 lisbon2-br1-a411.cprm.net (195.8.10.81) 96.232 ms 99.979 ms 102.336 ms 6 lisbon1-cr1-p50.cprm.net (195.8.0.89) 105.986 ms 108.902 ms 111.396 ms 7 if-0-0.core1.Miami.Teleglobe.net (207.45.197.197) 187.447 ms 190.679 ms 194.556 ms 8 if-6-0.core2.Ashburn.Teleglobe.net (207.45.223.114) 189.886 ms 193.121 ms 195.806 ms 9 ix-11-0.core2.Ashburn.teleglobe.net (209.58.27.38) 187.925 ms 190.910 ms 194.086 ms 10 vlan221-msr2.dcn.yahoo.com (216.115.96.167) 165.366 ms 165.171 ms 165.422 ms 11 vl33.bas2-m.dcn.yahoo.com (216.109.120.154) 169.381 ms 173.566 ms UNKNOWN-216-109-120-202.yahoo.com (216.109.120.202) 175.928 ms 12 p12.www.dcn.yahoo.com (216.109.118.75) 179.120 ms 182.773 ms 184.482 ms zeus:~ #

...

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.

Henry Harpending

03:06

New subject: [SLE] routing between subnets

On Tue, Jun 22, 2004 at 02:15:46AM +0000, Jorge Manuel B. S. Vicetto wrote:

...

...
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: mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo inet6 ::1/128 scope host 2: sit0@NONE: <NOARP> mtu 1480 qdisc noop link/sit 0.0.0.0 brd 0.0.0.0 3: eth0: mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:04:76:0f:99:59 brd ff:ff:ff:ff:ff:ff inet 172.28.2.2/24 brd 172.28.2.255 scope global eth0 inet6 fe80::204:76ff:fe0f:9959/64 scope link 4: eth1: mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:01:02:fa:e0:9e brd ff:ff:ff:ff:ff:ff inet 10.0.0.5/24 brd 10.0.0.255 scope global eth1 inet6 fe80::201:2ff:fefa:e09e/64 scope link fw:~ #

I notice that your output from "ip addr" says that eth0 is "PROMISC". What does this mean? My eth0 is "NOTRAILERS" and I don't know what this means either! #ip addr 1: lo: mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlan0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:09:5b:ba:65:c9 brd ff:ff:ff:ff:ff:ff inet 192.168.0.2/24 brd 192.168.0.255 scope global wlan0 inet6 fe80::209:5bff:feba:65c9/64 scope link valid_lft forever preferred_lft forever 3: sit0: <NOARP> mtu 1480 qdisc noqueue link/sit 0.0.0.0 brd 0.0.0.0 4: vmnet8: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff 5: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:e0:81:28:73:f9 brd ff:ff:ff:ff:ff:ff inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0 inet6 fe80::2e0:81ff:fe28:73f9/64 scope link valid_lft forever preferred_lft forever # Here is a traceroute to a printer traceroute to 192.168.1.5 (192.168.1.5), 30 hops max, 40 byte packets 1 192.168.1.5 3.252 ms 2.896 ms 4.236 ms and to my wife's mac on the other subnet traceroute to 192.168.0.22 (192.168.0.22), 30 hops max, 40 byte packets 1 192.168.0.22 9.513 ms 12.508 ms 9.897 ms As I said in another message I changed the netmask on the laptop and printer to /24 but nothing seems to have improved. Can you suggest something I should be reading? I usually rely on Welsh et al "Running Linux" but I think I have exhausted it in this case. Thanks to you and Anders, Best regards, Henry Harpending

Örn Hansen

24 Jun 24 Jun

11:53

New subject: Viruses, and the like

I just received the follwing email, since it originates from a DE location, and this list is the only remotely equivalent to a contact I have with anyone in DE, I'm going to post it here. For those interested, take a look at the "route" of the "original" letter. An inhouse created message, of the sending server who has faked my email in the from line... then sent it to itself, to have it bounce. ----------------------------------------------------------------------------------- Return-Path: <> Received: from mailfe05.swip.net ([130.244.240.105]) by fep40-svc.swip.net with ESMTP id <20040624111326.VMP16034.fep40-svc.swip.net@mailfe05.swip.net> for ; Thu, 24 Jun 2004 13:13:26 +0200 Received: from email.eva.mpg.de ([194.94.96.130] verified) by mailfe05.swip.net (CommuniGate Pro SMTP 4.2b5) with ESMTP id 76297719 for orn.hansen@swipnet.se; Thu, 24 Jun 2004 13:13:23 +0200 Received: by email.eva.mpg.de (MPI EVAN Mailserver) via BOUNCE id 80C8920672; Thu, 24 Jun 2004 13:13:17 +0200 (CEST) Date: Thu, 24 Jun 2004 13:13:17 +0200 (CEST) From: MAILER-DAEMON@eva.mpg.de (Mail Delivery System) Subject: Undelivered Mail Returned to Sender To: orn.hansen@swipnet.se MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="522572055C.1088075597/email.eva.mpg.de" Message-Id: <20040624111317.80C8920672@email.eva.mpg.de> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on citadel.sigtun.homelinux.net X-Spam-Level: ** X-Spam-Status: No, hits=2.1 required=5.0 tests=BAYES_20,HTML_20_30,MLM, UPPERCASE_25_50,WEIRD_QUOTING autolearn=no version=2.63 X-UID: Status: R X-Status: NT X-KMail-EncryptionState: X-KMail-SignatureState: X-KMail-MDN-Sent: This is a MIME-encapsulated message. --522572055C.1088075597/email.eva.mpg.de Content-Description: Notification Content-Type: text/plain This is the MPI EVAN Mailserver program at host email.eva.mpg.de. I'm sorry to have to inform you that the message returned below could not be delivered to one or more destinations. For further assistance, please send mail to <postmaster> If you do so, please include this problem report. You can delete your own text from the message returned below. The MPI EVAN Mailserver program <".2020603+virus"@eva.mpg.de>: unknown user: ".2020603+virus" --522572055C.1088075597/email.eva.mpg.de Content-Description: Delivery error report Content-Type: message/delivery-status Reporting-MTA: dns; email.eva.mpg.de Arrival-Date: Thu, 24 Jun 2004 13:13:17 +0200 (CEST) Final-Recipient: rfc822; ".2020603+virus"@eva.mpg.de Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; unknown user: ".2020603+virus" --522572055C.1088075597/email.eva.mpg.de Content-Description: Undelivered Message Content-Type: message/rfc822 Received: from eva.mpg.de (localhost [127.0.0.1]) by email.eva.mpg.de (MPI EVAN Mailserver) with ESMTP id 522572055C for <.2020603+virus@eva.mpg.de>; Thu, 24 Jun 2004 13:13:17 +0200 (CEST) Received: from eva.mpg.de (unknown [210.5.125.242]) by email.eva.mpg.de (MPI EVAN Mailserver) with ESMTP id 100AB20531 for <.2020603@eva.mpg.de>; Thu, 24 Jun 2004 13:13:11 +0200 (CEST) From: orn.hansen@swipnet.se To: .2020603@eva.mpg.de Subject: Infected *** Re: approved information Date: Mon, 14 Jun 2004 07:17:51 -0700 X-Virus-Infected: YES MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0016----=_NextPart_000_0016" X-Priority: 3 X-MSMail-Priority: Normal Message-Id: <20040624111311.100AB20531@email.eva.mpg.de>

7248

Age (days ago)

7251

Last active (days ago)

List overview

Download

17 comments

5 participants

participants (5)

Anders Johansson
Henry Harpending
Jorge Manuel B. S. Vicetto
The Purple Tiger
Örn Hansen