search for: lldpd

...> There are other use cases that want to hide a device from userspace. I >> >> What usecases do you have in mind? > > As mentioned in a previous response some kernel drivers create control > netdevs. Just as in this case users should not be mucking with it, and > S/W like lldpd should ignore it. I'm still not sure I understand your case: why you want to hide the control netdev, as I assume those devices could choose either to silently ignore the request, or fail loudly against user operations? Is it creating issues already, or what problem you want to solve if not ma...

...hat want to hide a device from userspace. I >> >> What usecases do you have in mind? > >As mentioned in a previous response some kernel drivers create control >netdevs. Just as in this case users should not be mucking with it, and virtio_net. Any other drivers? >S/W like lldpd should ignore it. It's just a matter of identification of the netdevs, so the user knows what to do. > >> >>> would prefer a better solution than playing games with name prefixes and >>> one that includes an API for users to list all devices -- even ones >>&...

...> There are other use cases that want to hide a device from userspace. I >> >> What usecases do you have in mind? > > As mentioned in a previous response some kernel drivers create control > netdevs. Just as in this case users should not be mucking with it, and > S/W like lldpd should ignore it. > >> >>> would prefer a better solution than playing games with name prefixes and >>> one that includes an API for users to list all devices -- even ones >>> hidden by default. >> >> Netdevice hiding feels a bit scarry for me. This s...

...Those modules use a > netdev (call it a master netdev, a control netdev, cpu port, whatever) > to pull packets from the ASIC and deliver to virtual netdevices > representing physical ports. The master netdev should not be mucked with > by a user. It should be ignored by certain s/w with lldpd as just an > *example*. Two approaches: 1) Add an IFF_CONTROL and make userspace understand this. It is probably long overdue. 2) Design the driver properly. Have a non-netdev master device like mlxsw does, and control it using devlink or similar. This is exactly how this stuff wa...

...Those modules use a > netdev (call it a master netdev, a control netdev, cpu port, whatever) > to pull packets from the ASIC and deliver to virtual netdevices > representing physical ports. The master netdev should not be mucked with > by a user. It should be ignored by certain s/w with lldpd as just an > *example*. Sorry, the linux kernel maintainers have a clear well defined attitude about out of tree kernel modules...

...a device from userspace. I >>>> >>>> What usecases do you have in mind? >>> >>> As mentioned in a previous response some kernel drivers create control >>> netdevs. Just as in this case users should not be mucking with it, and >>> S/W like lldpd should ignore it. >>> >>>> >>>>> would prefer a better solution than playing games with name prefixes and >>>>> one that includes an API for users to list all devices -- even ones >>>>> hidden by default. >>>> >>&gt...

...rt, whatever) > to pull packets from the ASIC and deliver to virtual netdevices > representing physical ports. Sounds a lot like DSA. Please ask the vendor to contribute the drivers :-) > The master netdev should not be mucked with by a user. It should be > ignored by certain s/w with lldpd as just an *example*. I have come across occasional problems with the master device in DSA. But nothing too serious. Generally the switch will just toss frames it gets which don't have the needed header, when they come direct from the master device, rather than via the slave devices. Andr...