josephmhiggins
commented
1 year ago The default mode for a bridged adapter is deny all - not promiscuous. While the gns3 vm was shutdown, I changed the bridged adapter to promiscous mode and it worked, power up - it worked. While the gns3 vm was running, I changed the bridged adapter to deny all - and pings failed changed the bridge. While the gns3 vm was shutdown, I changed the bridged adapter to promiscous mode and it worked, power up - it worked. While the gns3 vm was shutdown, I changed the bridged adapter to deny all, power up - and it worked??? I have no idea; it is working now.
oh, i put the bridged adapter back to promiscuous mode - after reading the manual - that looks best for me
From over here: https://gns3.com/community/featured/cant-ping-gns3-network
windows 10 gns3 2.2.39 virtualbox 7.0.10
trying to ping external lan with gns3-endhost wireshark shows arps pass through the gns3 vm both ways
I do not know what any of this means: Aug 8 13:37:47 gns3vm systemd-udevd[2100]: Using default interface naming scheme 'v245'. Aug 8 13:37:47 gns3vm networkd-dispatcher[683]: WARNING:Unknown index 9 seen, reloading interface list Aug 8 13:37:47 gns3vm kernel: [ 1111.528699] eth0: renamed from tap-gns3-e0 Aug 8 13:37:47 gns3vm systemd-udevd[2100]: tap-gns3-e0: Failed to get link config: No such device Aug 8 13:37:47 gns3vm networkd-dispatcher[683]: ERROR:Unknown interface index 9 seen even after reload Aug 8 13:37:47 gns3vm libvirtd[772]: Failed to open file '/sys/class/net/tap-gns3-e0/operstate': No such file or directory Aug 8 13:37:47 gns3vm libvirtd[772]: unable to read: /sys/class/net/tap-gns3-e0/operstate: No such file or directory
I will switch gns3 profiles and try to find out what that /sys/class/net stuff is.
This looks like a bug to me.