Re: 60+% ping packet loss on Pi3 under -current and stable-13

2022-04-29 Thread Mark Millard
On 2022-Apr-29, at 19:12, bob prohaska wrote: > Since about December of 2021 I've been noticing problems with > wired network connectivity on a pair of raspberry pi 3 machines > using wired network connections. One runs stable-13.1, the other > runs -current, both are up to date as of a few days

Re: 60+% ping packet loss on Pi3 under -current and stable-13

2022-04-29 Thread bob prohaska
Since about December of 2021 I've been noticing problems with wired network connectivity on a pair of raspberry pi 3 machines using wired network connections. One runs stable-13.1, the other runs -current, both are up to date as of a few days ago. Essentially both machines fail to respond to inbou

Re: issue with ng_vlan nomatch connected to the bridge

2022-04-29 Thread Benoit Chesneau
> 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

Re: issue with ng_vlan nomatch connected to the bridge

2022-04-29 Thread Benoit Chesneau
--- 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

Re: issue with ng_vlan nomatch connected to the bridge

2022-04-29 Thread Benoit Chesneau
> 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

Re: issue with ng_vlan nomatch connected to the bridge

2022-04-29 Thread Benoit Chesneau
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

issue with ng_vlan nomatch connected to the bridge

2022-04-29 Thread Benoit Chesneau
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