Thanks for your reply.
If I remember well openvswitch keeps the configuration even after a
reboot, perhaps the issue is caused by netctl which tries to erase
everything again? (then if it is the case it should have a difference
between reboot and starting from a cold start).
By the way speaking about netctl I am using this :
nano /etc/netctl/vswitch_trust
Description='Trusted Virtual Switch'
Interface=vswitch_trust
Connection=openvswitch
BindsToInterfaces=(eth1 eth2 eth3)
IP=static
Address=('10.20.8.10/24')
#Routes=('192.168.0.0/24 via 192.168.1.2')
Gateway='10.20.8.254'
DNS=('80.67.169.12')
Do you know if it is possible to indicate some vlan tag for eth1 eth2
eth3 directly in netctl conf?
I am asking this because apparently openvswitch is supported as I am
using Connection=openvswitch.
Many thanks
Ben
On 07/06/15 17:52, Ben Pfaff wrote:
It's hard for me to guess whether this is an issue related to netctl or
to openvswitch. It could be either one, but I would be inclined to
consider netctl first because Open vSwitch doesn't have any problems
with reboots when properly integrated to the software that controls it.
On Sun, Jun 07, 2015 at 02:15:27AM +0200, Ben wrote:
Hi Ben,
I have probably not been too accurate, let me try to explain:
I am using netcl to manage my network connection.
I have created one file in /etc/netctl named vswitch_trust
nano /etc/netctl/vswitch_trust
Description='Trusted Virtual Switch'
Interface=vswitch_trust
Connection=openvswitch
BindsToInterfaces=(eth1 eth2 eth3)
IP=static
Address=('10.20.8.10/24')
#Routes=('192.168.0.0/24 via 192.168.1.2')
Gateway='10.20.8.254'
DNS=('80.67.169.12')
Then I activated it with netctl enable vswitch_trust, then I should be able
to retrieve everything when my computer boots.
I can confirm that it is working correctly when my computer is poweroff and
I power on then all my openvswitch configuration came back with the
information I put on my vswitch_trust file.
The problem is when I am on my computer and decide to do a reboot (shutdown
-r now), then when the computer is rebooting all the rules are back but
impossible to ping it not to ping external from the computer.
To summarize when my computer goes from poweroff to power on everything is
ok but when I decide to reboot the computer then after the reboot my
interface is not responding at all. (I need to do a manual netctl stop
vswitch_trust and netctl start vswitch_trust to make it work)
On 06/06/15 21:41, Ben Pfaff wrote:
On Sat, Jun 06, 2015 at 06:13:32PM +0200, Ben wrote:
Working with openvswitch with netctl and I notice a problem when I shutdown
-r now (strange thing is that I don't have this error when I poweroff my
unit and start it again in this situation everything is working well).
When I shutdown -r now, I am unable to reach my unit, it is like netctl
tries to add everything again but it has not been deleted correctly before.
I'm confused. It sounds like you're turning off your computer and
complaining that it no longer works. Presumably this is not what you
are actually doing, can you explain?
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
