On 12-12-09 12:00 PM, Jo-Philipp Wich wrote:
> I fail to see how that requires changes to shorewall, it would continue
> doing whatever it does (routes added without explicit metric get
> automatically metric 0).
Because shorewall builds a routing system that looks like this:
root@OpenWrt:~# ip r
I fail to see how that requires changes to shorewall, it would continue
doing whatever it does (routes added without explicit metric get
automatically metric 0).
~Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.or
On 12-12-08 04:32 PM, Jo-Philipp Wich wrote:
> Did you consider to set "option metric" on the two interfaces, e.g.
> metric 10 and 11 and thne just install oyur own preferred defualt
> route with metric 0?
That's just not how the software (shorewall) that manages the routing
does things. I'd rath
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Did you consider to set "option metric" on the two interfaces, e.g.
metric 10 and 11 and thne just install oyur own preferred defualt
route with metric 0?
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with
On 12-12-08 01:34 PM, Jo-Philipp Wich wrote:
> Hi.
Hi,
> Yeah, but note that it is in the inactive table, means the protocol
> provides a defaultroute but it is suppressed by netifd,
Ahhh.
> probably due
> to "option defaultroute 0" in the uci config.
Yes, indeed. The reason for this is that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> In AA-rc1 I am trying to get the gateway of an interface:
>
> root@OpenWrt:~# (. /lib/functions/network.sh; network_get_gateway
> foo wan0; echo $foo)
>
> That returns nothing however. wan0 however does have a route
> configuration: [...]
Y
In AA-rc1 I am trying to get the gateway of an interface:
root@OpenWrt:~# (. /lib/functions/network.sh; network_get_gateway foo wan0;
echo $foo)
That returns nothing however. wan0 however does have a route
configuration:
root@OpenWrt:~# ubus call network.interface.wan0 status
{
"up": t
