Linux-kernel mailing list archive 1999-41,: 2.2.12 routing oddity

# 2.2.12 routing oddity

George Bonser (grep@shorelink.com)
Mon, 11 Oct 1999 22:42:57 -0700 (PDT)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Avenger: "Kernel Modules in 2.3.20"
- Previous message: yodaiken@chelm.cs.nmt.edu: "Re: SCHED_YIELD again"

Two linux routers A and B .... both are on the 192.168.50/24 and
172.16/16 nets

Router A is at 192.168.50.1 and has a WAN connection to 192.168.10/24

Router B has a route:

192.168.10.0 192.168.50.1 255.255.255.0 UG 0 0 eth1

Problem is that if a workstation on the 172.16.0.0/16 net tries to use
Router B as its default gateway, it can not get to 192.168.10/24 even
though packet rules specificly allow forwarding between 172.16/16 and
192.168/16 in both directions.

If I add a second route

192.168.10.0 172.16.0.1 255.255.255.0 UG 0 0 eth2

It works.

Why do I need both routes on the router?

Why won't packets arriving on 172.16.0.254 be forwarded to 192.168.10.2
via 192.168.50.1 ???

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

- Next message: Avenger: "Kernel Modules in 2.3.20"
- Previous message: yodaiken@chelm.cs.nmt.edu: "Re: SCHED_YIELD again"