OpnSense as VM WAN issue | Please help

[newsense]

You were using one NIC of everything, that's not what was discussed here.

To reproduce the issue put the two interfaces on the Internal Network in VBox, absent DHCP assign manually two IPs on the WAN and Linux VMs in the same network range.

[allebone]

Actually I set it up as per the screenshot in the OP, so it emulates the OPs description.

[allebone]

I just double checked what he said and verified my setup is similar to what was said here:


"installed Opnsene as VM on VirtualBox with 2 NICs (Bridged As WAN, Internal Network As LAN). (attachment: firewall-nics)
LAN (em1) -> v4:192.168.1.1/24
WAN (em0) -> v4/DHCP4: 192.168.3.200/24"

2 nics on host machine - check
Each nic seperately bridged - one nic bridged for lan and other nic bridged for wan to VM guest - check.
Screenshot of guest console is the same - check

He is trying to access firewall from machine hosting VM and had a problem. I test this and do not have the same problem.

" I am trying to access OPnsene from my computer hosting VM "

My setup is the same yet issue is not present.

P

[newsense]

Bridging is an entirely different conversation that I haven't addressed.

There's a false assumption in the original thread which implies a ping reply "must be" originating from a firewall that happens to be running there, yet there's no way of knowing for sure it is not the TCP/IP stack on the host that answers the ping.

Everything else I wrote in this thread still stands, yet it has nothing to do with bridged NICs whatsoever.

[allebone]

I setup a test as per the OP who started the post with a problem. If you are talking about something other than the OP's original setup then I wouldnt be able to follow that unless you post how you want me to perform the test to generate the issue as per how you have it setup. If you want me to change some settings I would be happy to do so and test again with different settings, it is no problem at all.

-P