Le 08/01/2017 à 17:15, Reco a écrit :
Pascal Hambourg wrote:
Actually I had in mind the behaviour of Linux bridge, not openvswitch. I
have no knowledge nor experience with openvswitch. However, I can see
that the openvswitch package adds a script in /etc/network/if-pre-up.d,
so it is likely t
Le 08/01/2017 à 17:10, Reco a écrit :
Pascal Hambourg wrote:
Le 06/01/2017 à 13:15, Reco a écrit :
DHCP is L4, IP is L3 and openvswitch cares about L2
mostly.
Self-correction. DHCP is L7.
Why ? DHCP deals with IP configuration, so I'd rather classify it as
part of layer 3, with IP and I
On Sun, 8 Jan 2017 19:10:31 +0300
Reco wrote:
> Furthermore, there are lots of dhcp options (ntp-server,
> local-proxy-config to name a few that are actually used) that deal with
> client's configuration that's not related to IP configuration directly.
And dns-servers, of course. Should not for
Hi.
On Sun, 8 Jan 2017 16:48:02 +0100
Pascal Hambourg wrote:
> Le 05/01/2017 à 22:36, Reco a écrit :
> >
> > Pascal Hambourg wrote:
> >
> >>> Bridged interfaces retain their MACs, so they would get different IPv6
> >>> ULAs, which are provided by radvd from the different host.
> >>
> >>
Hi.
On Sun, 8 Jan 2017 16:59:39 +0100
Pascal Hambourg wrote:
> Le 06/01/2017 à 13:15, Reco a écrit :
> >>
> >> DHCP is L4, IP is L3 and openvswitch cares about L2
> >> mostly.
> >
> > Self-correction. DHCP is L7.
>
> Why ? DHCP deals with IP configuration, so I'd rather classify it as
Le 06/01/2017 à 13:15, Reco a écrit :
DHCP is L4, IP is L3 and openvswitch cares about L2
mostly.
Self-correction. DHCP is L7.
Why ? DHCP deals with IP configuration, so I'd rather classify it as
part of layer 3, with IP and ICMP. AFAIK, it does not provide any
service to any application b
Le 05/01/2017 à 22:36, Reco a écrit :
Pascal Hambourg wrote:
Bridged interfaces retain their MACs, so they would get different IPv6
ULAs, which are provided by radvd from the different host.
Not if they are bridged before they are brought UP
I'm not that familiar with openvswitch to make
> To speedup obtaining a lease you should probably restart dhclient on
> usb0 addition/removal.
Right, that's basically the issue. I know I can write all this with
enough post-up scripting in /etc/network/interfaces (or even udev
.rules files), but I was hoping there was something already written
On Wed, Jan 04, 2017 at 10:34:16PM -0500, Stefan Monnier wrote:
> I have a bridge interface `br0` which usually contains jut `eth0` but
> occasionally also needs to contain `usb0`, which is an ethernet-dongle
> kind of thing.
>
> How do I setup /etc/network/interfaces for that?
>
> Currently, I j
On Fri, 6 Jan 2017 14:30:53 +0300
Reco wrote:
> Hi.
>
> On Thu, 05 Jan 2017 20:17:39 -0500
> Stefan Monnier wrote:
>
> > > But, it all changes if you replace conventional bridge with
> > > openvswitch, which *can* add new interfaces (ports as they call it) to
> > > its own bridges dynami
Hi.
On Thu, 05 Jan 2017 20:17:39 -0500
Stefan Monnier wrote:
> > But, it all changes if you replace conventional bridge with
> > openvswitch, which *can* add new interfaces (ports as they call it) to
> > its own bridges dynamically *and* it can be configured via interfaces(5).
>
> Inter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jan 06, 2017 at 02:47:32AM +0100, Sven Hartge wrote:
> Michael Biebl wrote:
>
> >> [2] Once, for a customer: inserting the right storage medium (with
> >>the right UUID) triggered a system backup.
>
> > Please don't do that. udev is a no
Michael Biebl wrote:
>> [2] Once, for a customer: inserting the right storage medium (with
>>the right UUID) triggered a system backup.
> Please don't do that. udev is a not a service manager and starting (long
> running) tasks from a udev rule is bad.
I wish someone would clue in Dell into
> But, it all changes if you replace conventional bridge with
> openvswitch, which *can* add new interfaces (ports as they call it) to
> its own bridges dynamically *and* it can be configured via interfaces(5).
Interesting. Would it work if the IP address of the bridge is acquired
dynamically via
Hi.
On Thu, 5 Jan 2017 22:17:23 +0100
Pascal Hambourg wrote:
> > Bridged interfaces retain their MACs, so they would get different IPv6
> > ULAs, which are provided by radvd from the different host.
>
> Not if they are bridged before they are brought UP
I'm not that familiar with open
Le 05/01/2017 à 22:17, Pascal Hambourg a écrit :
But according to man interfaces(5), the inet6 "auto" method ignores the
"autoconf" option. This option is specific to the "static" method.
And "dhcp".
Le 05/01/2017 à 17:32, Reco a écrit :
Joshua Schaeffer wrote:
A sample configuration would be:
allow-ovs br0
iface br0 inet4 static
address …
netmask …
ovs_type OVSBridge
allow-br0 eth0
iface eth0 inet6 auto
ovs_type OVSPort
ovs_bridge br0
allow-hotp
>> Interesting. Any hint how?
> It would be too long to explain here, but this page seems to cover the
> basics of what you need:
> http://packetpushers.net/udev/
I don't see any mechanism in there that will bring up an interface or
add it to a bridge, nor bring up the bridge.
As I said, I alrea
Interesting, thanks for the explanation.
On Thu, Jan 5, 2017 at 9:32 AM, Reco wrote:
> Hi.
>
> On Thu, 5 Jan 2017 09:19:35 -0700
> Joshua Schaeffer wrote:
>
> > >
> > >
> > > A sample configuration would be:
> > >
> > > allow-ovs br0
> > > iface br0 inet4 static
> > > address …
Hi.
On Thu, 5 Jan 2017 09:19:35 -0700
Joshua Schaeffer wrote:
> >
> >
> > A sample configuration would be:
> >
> > allow-ovs br0
> > iface br0 inet4 static
> > address …
> > netmask …
> > ovs_type OVSBridge
> >
> > allow-br0 eth0
> > iface eth0 inet6 auto
> >
>
>
> A sample configuration would be:
>
> allow-ovs br0
> iface br0 inet4 static
> address …
> netmask …
> ovs_type OVSBridge
>
> allow-br0 eth0
> iface eth0 inet6 auto
> ovs_type OVSPort
> ovs_bridge br0
>
> allow-hotplug usb0
> iface usb0 inet6 auto
>
Hi.
On Wed, 04 Jan 2017 22:34:16 -0500
Stefan Monnier wrote:
> I have a bridge interface `br0` which usually contains jut `eth0` but
> occasionally also needs to contain `usb0`, which is an ethernet-dongle
> kind of thing.
>
> How do I setup /etc/network/interfaces for that?
>
> Curren
Am 05.01.2017 um 10:29 schrieb to...@tuxteam.de:
> and delegates to specialized subsystems. In a pinch you can just sneak
> a complete shell script in an udev rule (and I'm guilty of having done
> such a thing [2]), but doing this as "system architecture" might lead to
> madness :-)
> [2] Once, fo
Le sextidi 16 nivôse, an CCXXV, Stefan Monnier a écrit :
> Interesting. Any hint how?
It would be too long to explain here, but this page seems to cover the
basics of what you need:
http://packetpushers.net/udev/
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
>> Is there something better? Like a predefined way to just say that when
>> `usb0` appears, it should be added to `br0` (and ideally, this would
>> also `ifup` the `br0` interface if it's not up yet).
> Not with /etc/network/interfaces and ifupdown, but udev can do all that.
Interesting. Any hi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jan 05, 2017 at 10:07:59AM +0100, Nicolas George wrote:
> Le quintidi 15 nivôse, an CCXXV, Stefan Monnier a écrit :
> > Is there something better? Like a predefined way to just say that when
> > `usb0` appears, it should be added to `br0` (and
Le quintidi 15 nivôse, an CCXXV, Stefan Monnier a écrit :
> Is there something better? Like a predefined way to just say that when
> `usb0` appears, it should be added to `br0` (and ideally, this would
> also `ifup` the `br0` interface if it's not up yet).
Not with /etc/network/interfaces and ifu
I have a bridge interface `br0` which usually contains jut `eth0` but
occasionally also needs to contain `usb0`, which is an ethernet-dongle
kind of thing.
How do I setup /etc/network/interfaces for that?
Currently, I just setup everything "manually": `br0` is setup `static`,
and `usb0` is setup
28 matches
Mail list logo
