A "cable = true" means the cable has been disconnected and reconnected at least once. Scottgus1 wrote:So if "cable = false/true" is not in the XML for a network card, it would mean that the cable is in its default state of being connected and has never been disconnected since the beginning of the VM (unless a manual edit was done). The problem appears to appear when the Bridged adapter is inserted. All of the pfSense network's cables are "true", none of the Web Server's network cables (including Internal "dmz") are "true", yet access to the web server is possible from Kali (whose "dmz" cable is also not "true" ) vbox file's cable="true" does not apparently always mean 'cable is connected' (at least I have not figured out the pattern). I cannot tell which of these Internal networks have their "cables" connected, as the. It is also connected to the pfSense through the following separate but parallel Internal networks: The Ubuntu "Web Server" is Bridged to the host's Wi-Fi. Since "External" is supposed to represent the internet, this should be connected to pfSense's WAN port (which can't be determined from the. I also see the "External" Internal network between Kali and pfSense, which continues through Internal "dmz" to the Ubuntu Web Server. But in one of my own setups, I'm using an Intel Wireless-AC 9560 without problems, so I also don't expect any problems with the Intel Wireless-AC 9260 either. Regarding bridging over the Intel Wireless-AC 9260, there could be problems. You can also create Wireshark captures in VirtualBox (search the VirtualBox User Manual for "nictrace"). I'd use Wireshark on all three VMs to see where the ICMP echo request or the ICMP echo reply gets stuck. Last but not least, the Ubuntu VM has a Bridged Network which gets an IP address from your host network (192.168.1.96/24 in your initial posting, 192.168.0.66/26 at some time in the past, note the different netmasks).Īn HTTP(S) connection from 1.1.1.2 to 10.0.0.69 and a ping from 10.0.0.69 to 1.1.1.2 do work, but a ping from 1.1.1.2 to 10.0.0.69 does not work. Then there is an Internal Network named "dmz" between the Kali VM (10.0.0.1/24) and the Ubuntu VM (10.0.0.69/24). There is an Internal Network named "external" between the Kali VM (1.1.1.2/30) and the pfSense VM (1.1.1.1/30). ![]() vbox files, they solved some misunderstandings (for me at least). ![]() Internal Network adapter (DMZ) 3-6-vbox-2.PNG (11.88 KiB) Viewed 7832 times (Please let me know if I'm not giving enough details in this post) Thanks in advance!ġ. The following are my adapter settings on my Ubuntu machine. I just want to be able to get Internet connection but also be able to ping the network at the same time.Īny help would be appreciated! I'm literally going to get white hairs from this. However, I really need the bridged adapter for gaining an internet connection on my Ubuntu machine. The moment I remove the bridged adapter, the pings are able to work again. ![]() ![]() What makes this even weirder is that, I can ping my Kali from my Ubuntu machine but not the other way round. I also used iptables to make sure ICMP echo requests are not getting blocked on both the Ubuntu and Kali machines. To ensure that this isn't a firewall issue, I allowed all ICMP requests to flow from the External zone to the DMZ zone vice versa on the router. In addition, I am able to ping the Ubuntu machine from a shell on my PFSENSE-HP router. However, I can access the website on 10.0.0.69 via my browser on Kali. The issue is that when I use the Bridged adapter on my Ubuntu machine, my Kali can't ping the IPv4 address of the Internal Network (DMZ) adapter anymore. TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0īetween these two machines, I am using PFSENSE-HP 2.6.0 as my router.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |