Hey all,
I am setting up a new Firewall with
Shorewall Version 4.5.20
iptables v1.4.18
Kernel 3.10.10
perl v5.16.3
v6.19, protocol version: 6
quagga 0.99.22.3
providers file is
ISP110x100-vlan1010.0.11.1 track,loose -
ISP220x200-vlan11
:
vlan11eth?detectoptional
On Thu, Sep 12, 2013 at 8:11 AM, HL <mailto:freemail.grha...@gmail.com>> wrote:
Hey all,
I am setting up a new Firewall with
Shorewall Version 4.5.20
iptables v1.4.18
Kernel 3.10.10
perl v5.16.3
v6.19, p
On 13/09/2013 04:35 μμ, Tom Eastep wrote:
> On 9/13/2013 6:01 AM, HL wrote:
>> After endless tries the only way that I have managed to feed zebra
>> routes into kernel is ..
>> #NAME NUMBER MARKDUPLICATE INTERFACE GATEWAY
>> OPTIONS
On 13/09/2013 04:35 μμ, Tom Eastep wrote:
> On 9/13/2013 6:01 AM, HL wrote:
>> After endless tries the only way that I have managed to feed zebra
>> routes into kernel is ..
>> #NAME NUMBER MARKDUPLICATE INTERFACE GATEWAY
>> OPTIONS
On 13/09/2013 05:52 μμ, Tom Eastep wrote:
> On 9/13/2013 7:08 AM, HL wrote:
>
>> For instance in your case you only need to install zebra with *no* other
>> daemon to test it.
>>
>> In my case
>> zebra GETS Blocked. Why?
> I'll try it over the wee
On 14/09/2013 08:57 μμ, Tom Eastep wrote:
> But there is no point in even using Shorewall's Multi-ISP this way since
> the above route is completely useless on an Ethernet interface.
Hi, Tom
As promised
before shorewall start
#ip r
default proto zebra
nexthop via 10.0.11.1 dev eth1 weight
In Multi ISP env having a static route on the FW itself impies that the
remote host is forced to communicate over the same path that the static
route indicates ??
In other words,
If ip route add 173.194.39.212/32 via ISP1 is placed on the fw,
and
provided that there is static ip prefix vv.
Hi,
I am facing a peculiar situation with a new 10G (HP) L3 switch + Cisco
catalyst ,
shorewall runs on a machine that has a few interfaces,
in particular
2 bonded interfaces to to a cisco catalyst 1G
and
2 bonded 10G interfaces to an hp 10G
all bonds are 802.3ad mode
When I boot the m