grip

Comments

  • Thanks for the kind answers, but the only one that got near what I need is from @peter2 even if I don't know if it would fit the need to have a fully operational firewall (with NAT) and a working LAN behind it (nested NAT it's not the best I guess); the problem here is not divide the connection from a layer 2 perspective…
  • Hi Peter, I did what you suggested (I have to better understand the issue with the MTU): deleted any new interface created by the Realtek utility and created the new one with Hyper-V tools Scheda Ethernet vEthernet (VLAN10): Suffisso DNS specifico per connessione: Descrizione . . . . . . . . . . . . . : Hyper-V Virtual…
  • Hi Nami, maybe we could have some hint now: I first applied only untagged VLAN10 on port 3 and nothing changed, when I applied also PVID 10 on port 3 the communication with RPi (on VLAN 1 subnet also) stopped working. That could be because there is something wrong on the RPi side... - this is the output of lsmod | grep…
  • Hi Nami, I also have doubts that the Windows system is correctly tagging packets but I don't know how to verify this. I did what you suggested with PVID but nothing changed The Realtek utility is the one you can download from this…
  • Hi,thank you again for your time.I did what you suggested and now the situation is the following ping output to RPi on VLAN1 on windows host: Esecuzione di Ping 192.168.1.212 con 32 byte di dati: Risposta da 192.168.1.212: byte=32 durata<1ms TTL=64 Risposta da 192.168.1.212: byte=32 durata<1ms TTL=64 Risposta da…
  • the diagram is above and what I'd like to do is to be able to ping from one host to the other over VLAN10.Right now it works only on VLAN1.
  • Hi Peter,thanks for you kind reply. I'm not trying to route btw vlans. I'm trying to reach from eth0.10 (VLAN10 - port 3) to Windows PC (VLAN10 - port 7)so the communication will be over the same subnet: 192.168.10.10 <--> 192.168.10.100 I've tried from RPi with ping -I eth0.10 192.168.10.100 but with no success, even…
Default Avatar