Tom Eastep wrote:
Joshua Perry wrote:
Tom Eastep wrote:
Joshua Perry wrote:
I'm getting an error when shorewall is trying to add the default routes
for my multi-isp configuration. I've attached a shorewall dump... If
anyone can give some input I'd appreciate it.
RTNETLINK answers: Invalid argument
ERROR: Command "ip -4 route replace default scope global table 254
nexthop via 67.110.119.245 dev eth3 weight 1 nexthop via 66.29.181.113
dev eth2 weight 1" Failed
Are you running a routing daemon? I note that many of your routes have
'proto zebra'.
-Tom
Yes, we're using Quagga OSPF for routing traffic between our three
locations which are connected in a star configuration via IPSEC tunnels.
Well, I don't know what to tell you. The command is valid and, as close
as I can come to reproducing the environment here, it works for me.
If you delete the default route and then restart Shorewall, does it work?
-Tom
This turned out to be a kernel config issue. "IP: equal cost multipath"
(CONFIG_IP_ROUTE_MULTIPATH) must be enabled in order for equal cost
routes to be added to the routing table.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
