1) i set the ports as "tagged egress members" which means (from what I understood) the port is aware that the device connected has to manage tagging and it uses the vlan table to forward packets to the right port/s (but maybe I'm wrong)
jeeeeez you were alright!
changed the port to untagged and reconfigured network properly and everything went fine!!! no way!
by the way... it can be the crappy ethernet adapter who is not managing the extra load in the ethernet packet, even if other stuff is working (ssh, gui etc...) ...i'm realizing now
damn it was soooo easy thank you for pointing me to the right path!!!!
i want to go deep into this and i truly believe it's the network card right now!
i confirm it's the ethernet card, i switched port reverting network config and all came back working as expected!
marking this as solved and big, tremendous thanks to @tempacc346235 for helping in this
i confirm it's the ethernet card, i switched port reverting network config and all came back working as expected!
marking this as solved and big, tremendous thanks to @tempacc346235 for helping in this
Glad you got it working! It could have been multiple things, really, but not apt, weird things can happen with MTUs, VLAN tagging, bridging, etc. that only manifest with certain frames. The more in-depth way would have been to e.g. use tshark and capture some of the packets, see what was wrong with them. But sometimes a shot in the dark is faster. Enjoy!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.