Please see inline.. On Fri, May 26, 2017 at 1:15 AM, Toshiaki Makita <makita.toshiaki@xxxxxxxxxxxxx> wrote: > On 2017/05/26 14:08, Manohar Kumar wrote: >> On Wed, May 24, 2017 at 6:11 PM, Toshiaki Makita >> <makita.toshiaki@xxxxxxxxxxxxx> wrote: >>> On 2017/05/25 3:05, Manohar Kumar wrote: >>>> Thanks, Toshiaki. >>>> >>>> What is the right way to set the default_pvid using the bridge command >>>> ? I tried this, which fails.. >>>> >>>> root@net-3:~# ip link set dev vxlan0 name untagged type vlan id 0 >>>> RTNETLINK answers: Operation not supported >>>> root@net-3:~# >>>> >>>> All the interfaces in the bridge are untagged. >>> >>> # ip link set br0 down >>> # echo 0 > /sys/class/net/br0/bridge/default_pvid >>> >> >> I have the bridge inside a network namespace. There is no >> /sys/class/net entry for the bridge interface inside the namespace. >> >> I see online references to this concept of 'tagged' sysfs directories >> to support namespaces. But its not clear how to access the sysfs >> entries for a particular namespace. > > Did you remount /sys after entering netns? No, that was the problem. Mounting /sys did the trick. Appreciate your help. Trying to understanding this better. How is the sysfs tree maintained per network namespace ? I assume only the /sys/class/net is per network namespace and the rest of the /sys is shared with the host namespace ? Also, how does mounting /sys in the network namespace make the new /sys/class/net tree visible ? thanks, Manohar. > If not, remount /sys or use "ip netns" which automatically do it. > >> Is there any other way to set the default_pvid for the bridge >> interface inside namespace ? > > No, as of 3.19. > > > Toshiaki Makita >
