Hello, Jesse,
Thank you SO MUCH for pointing this out. I inherited an init script that
must have been older than the version in 2.3.1, and did not have the
iptables rules.
Now, it JUST WORKS, as it's supposed to :)
For anyone interested, the OpenSUSE LEAP 42.1 packages are in
https://build.merpr
On Thu, Jul 7, 2016 at 10:55 AM, Bolesław Tokarski
wrote:
> Hello,
>
> I installed Ubuntu 16.04 on the hostB to check the behaviour between the two
> OSes.
>
> The setup is the same as with two hosts running OpenSUSE:
>
>
>>> >
>>> > hostA:
>>> >
>>> > ovs-vsctl add-br secure
>>> > ip link set sec
Hello,
I installed Ubuntu 16.04 on the hostB to check the behaviour between the
two OSes.
The setup is the same as with two hosts running OpenSUSE:
>
>> > hostA:
>> >
>> > ovs-vsctl add-br secure
>> > ip link set secure up
>> > ip addr add 192.168.20.1/24 broadcast 192.168.20.255 dev secure
>>
Hello, Jesse,
Thank you for the advice on using normal GRE interfaces in OVS. I am yet to
try this approach.
However, my apologies for not giving all the background - I am running the
ovs-monitor-ipsec script, which I ported from Debian. Not many changes were
required (racoon init script executio
On Tue, Jul 5, 2016 at 4:04 PM, Bolesław Tokarski
wrote:
> Hello,
>
> For some reason machine receiving traffic through ipsec_gre is not putting
> it through to the LOCAL interface.
>
> I have a basic test setup:
>
> hostA - ip network - hostB
>
> Both hosts have just a single eth0 interface. I ma
Hello,
For some reason machine receiving traffic through ipsec_gre is not putting
it through to the LOCAL interface.
I have a basic test setup:
hostA - ip network - hostB
Both hosts have just a single eth0 interface. I managed to get a regular
gre tunnel working (thanks to Mathy Vanvoorden's bl
