Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #176334

Re: hotpluggable member of a bridge

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Interesting, thanks for the explanation.

On Thu, Jan 5, 2017 at 9:32 AM, Reco <recoverym4n@gmail.com> wrote:

>         Hi.
>
> On Thu, 5 Jan 2017 09:19:35 -0700
> Joshua Schaeffer <jschaeffer0922@gmail.com> 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-hotplug usb0
> > > iface usb0 inet6 auto
> > >         ovs_type OVSPort
> > >         ovs_bridge br0
> > >
> > > Reco
> > >
> > >
> > Pardon my ignorance, can you explain why you set an IPv4 address on your
> > bridge and an IPv6 address on your bridge interfaces? I've never seen
> this
> > before and would like to know what this accomplishes. Perhaps its a typo
> as
> > I thought IPv4 was just set with "inet" and IPv6 was set with "inet6".
>
> It's simple, although isn't obvious from this abridged example.
> I need a single IPv4 for both interfaces, so I set it on a bridge.
> I don't need distinct IPv4 on ports, so I don't set it there.
>
> Bridged interfaces retain their MACs, so they would get different IPv6
> ULAs, which are provided by radvd from the different host.
> And I don't need these IPv6 either.
>
> So, I can do:
>
> allow-br0 eth0
> iface eth0 inet manual
>          ovs_type OVSPort
>          ovs_bridge br0
>
> And get myself all kinds of unneeded trouble, or I can do:
>
> allow-br0 eth0
> iface eth0 inet6 auto
>         autoconf 0
>         accept_ra 0
>         ovs_type OVSPort
>         ovs_bridge br0
>
> Barring this IPv4/IPv6 difference, there should be no noticeable
> outcome between 'inet manual' and 'inet6 auto'.
>
> Reco
>
>

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

hotpluggable member of a bridge Stefan Monnier <monnier@iro.umontreal.ca> - 2017-01-05 04:40 +0100
  Re: hotpluggable member of a bridge Nicolas George <george@nsup.org> - 2017-01-05 10:10 +0100
    Re: hotpluggable member of a bridge <tomas@tuxteam.de> - 2017-01-05 10:30 +0100
      Re: hotpluggable member of a bridge Michael Biebl <biebl@debian.org> - 2017-01-05 16:30 +0100
        Re: hotpluggable member of a bridge Sven Hartge <sven@svenhartge.de> - 2017-01-06 03:00 +0100
          Re: hotpluggable member of a bridge <tomas@tuxteam.de> - 2017-01-06 09:40 +0100
    Re: hotpluggable member of a bridge Stefan Monnier <monnier@iro.umontreal.ca> - 2017-01-05 16:30 +0100
      Re: hotpluggable member of a bridge Nicolas George <george@nsup.org> - 2017-01-05 16:40 +0100
        Re: hotpluggable member of a bridge Stefan Monnier <monnier@IRO.UMontreal.CA> - 2017-01-05 18:30 +0100
        Re: Congratulations Danielle , Your Roof is Covered - FREE!GYfb Danielle Gregory <danielle.k.gregory@gmail.com> - 2017-01-05 22:10 +0100
        Re: Congratulations Aileen , Your Roof is Covered - FREE!PHYi tazzygirl tazzygirl <saratazmtz77@gmail.com> - 2017-01-05 22:10 +0100
        RE: Congratulations Emmanuel , Your Roof is Covered - FREE!44OO Jennyetta Washington <manolofimbres@gmail.com> - 2017-01-05 22:20 +0100
  Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-05 17:10 +0100
    Re: hotpluggable member of a bridge Joshua Schaeffer <jschaeffer0922@gmail.com> - 2017-01-05 17:20 +0100
      Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-05 17:40 +0100
        Re: hotpluggable member of a bridge Joshua Schaeffer <jschaeffer0922@gmail.com> - 2017-01-05 18:10 +0100
        Re: hotpluggable member of a bridge Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-01-05 22:20 +0100
          Re: hotpluggable member of a bridge Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-01-05 22:30 +0100
          Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-05 22:40 +0100
            Re: hotpluggable member of a bridge Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-01-08 16:50 +0100
              Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-08 17:20 +0100
                Re: hotpluggable member of a bridge Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-01-08 18:00 +0100
    Re: hotpluggable member of a bridge Stefan Monnier <monnier@iro.umontreal.ca> - 2017-01-06 02:20 +0100
      Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-06 12:40 +0100
        Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-06 13:20 +0100
          Re: hotpluggable member of a bridge Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-01-08 17:00 +0100
            Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-08 17:20 +0100
              Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-08 17:30 +0100
              Re: hotpluggable member of a bridge Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-01-08 17:30 +0100
        Re: hotpluggable member of a bridge Stefan Monnier <monnier@iro.umontreal.ca> - 2017-01-06 22:50 +0100
  Re: hotpluggable member of a bridge Jonathan Dowland <jmtd@debian.org> - 2017-01-06 18:20 +0100

csiph-web