[TriLUG] Linux routing problem (RTnetlink answers: network is unreachable)

[Chris Bullock]

no IPsec or VPN stuff, just packet routing.  Don't know how much more in detail i could go except interface 172.0.0.1 is eth0 and 172.0.1.1 is eth1

Jon Carnes <jonc at nc.rr.com> wrote:On Fri, 2005-03-11 at 17:30, Chris Bullock wrote:
> have a router with 2 interfaces. 172.0.0.1 and 172.0.1.1. 
> Routing currently works, but just added another Internet
> connection. I can add all the routes I want that point 
> to a device connected on the 172.0.0.X/24 network but 
> every time I try to add a route to the other interface 
> I get "RTnetlink answers: network is unreachable." 
> traffic is routed between the 2 networks fine but for 
> some reason I can not add a route to any host on the 172.0.1.x subnet.
>
> Example /sbin/ip r add 69.69.69.69/32 via 172.0.0.254 would work, but 
> /sbin/ip r add 68.68.68.68/32 via 172.0.1.254 would not.
> Any help would be greatly appreciated.
> Chris

Sounds like a mis-configuration in an IPsec setup, where the
"leftnexthop" is not setup properly for the connections. But it could be
any number of errors. We would need more info to help out.

Jon

-- 
TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com