> root@test:~ # dhclient vtnet0.101
> DHCPDISCOVER on vtnet0.101 to 255.255.255.255 port 67 interval 3
> DHCPDISCOVER on vtnet0.101 to 255.255.255.255 port 67 interval 5
> DHCPDISCOVER on vtnet0.101 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on vtnet0.101 to 255.255.255.255 port 67 interv
--- Original Message ---
On Friday, April 29th, 2022 at 09:53, Benoit Chesneau
wrote:
>> To quickly test, I created an interface added to the bridge that get its IP
>> from DHCP: The IP is correctly given by the DHCP server, but I can't ping
>> from the same server (the router with the
> To quickly test, I created an interface added to the bridge that get its IP
> from DHCP: The IP is correctly given by the DHCP server, but I can't ping
> from the same server (the router with the DHCP server) to this device.
>
> ```
> # ngctl mkpeer public: eiface link2 ether
> # dhclient ngeth
To quickly test, I created an interface added to the bridge that get its IP
from DHCP: The IP is correctly given by the DHCP server, but I can't ping from
the same server (the router with the DHCP server) to this device.
```
# ngctl mkpeer public: eiface link2 ether
# dhclient ngeth1
DHCPDISCOVE
I have an issue with the way the nomatch hook is working. I have linked the
nomatch hook from a lan to a bridge but I can only get the native vlan in it. I
can't even ping new link added to this bridge. Maybe I am missing some
connection?
My goal is to be able to catch non filtered vlan in an n
