AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
For windows instal Wireshark 4.0.101/27/2024 ![]() I added a static ARP entry and I saw it sent the ICMP packet but didn't see it arrive on eth0 of LFS Bridge. I then tried from another Linux box on my physical 10.0.0.x network and it was not getting an ARP reply for 10.0.0.1. However, I could see the MAC address of the client in the bridge configuration (brctl showmacs br0) so I knew the bridge configuration was correct. The LFS Bridge virtual machine was not responding to ARP or accepting any packets for the client on the other side of the bridge. I was not able to ping from 10.0.0.1 to 10.0.0.2 or vice-versa. VM Adapter1: Internal Network - intnet - Intel PRO/1000 MT Desktop (82540EM) VM Adapter2: Internal Network - intnet - Intel PRO/1000 MT Desktop (82540EM) VM Adapter1: Bridged Adapter - Intel 82566DM-2 Gigabit Network Connection - Intel PRO/1000 MT Desktop (82540EM) Then I tried with just two VM's (one bridge, one client) and used a Bridged Adapter on the bridge so I could test with my office LAN. The ICMP packets would arrive on one interface of the bridge but would not be forwarded out the other. Then I added static ARP entries in each client. I did a packet sniff with tcpdump and saw that the ARP request got to the other client and it replied but the LFS Bridge virtual machines were not forwarding the ARP reply. In fact, the clients were not getting an ARP reply back. I could not ping from 10.0.0.1 to 10.0.0.2 or vice-versa. VM Adapter2: Internal Network - WAN - Intel PRO/1000 MT Desktop (82540EM) VM Adapter1: Internal Network - LANB - Intel PRO/1000 MT Desktop (82540EM) VM Adapter1: Internal Network - LANA - Intel PRO/1000 MT Desktop (82540EM) I first tried with all four VM's with Internal Networks. VM Systems: Four virtual machines running LFS (Linux From Scratch). Host Systems: Tested with two separate Windows XP 32-bit and Windows 7 圆4 hosts. I want to share my experience with others in case it helps shed light on what seems to be a bug in VirtualBox. I found some posts where others are having a similar guest bridge issue after upgrading to 4.0.6, 4.0.8, or 4.0.10. I was not able to get it to work with 4.0.10. It's basically client-bridge-bridge-client. ![]() ![]() I am putting together a network setup using four virtual machines. ![]()
0 Comments
Read More
Leave a Reply. |