Nub question about bridging with Win7 + Virtualbox


  • Ok, this may seem nubbish, but here it goes:

    Windows 7 is hosting Virtualbox with pfs
    em0 = physical NIC (cable connected to DSL) = WAN
    em1 = physical NIC (wifi for wifi AP) = LAN

    Now, my windows 7 machine itself, I am connected to the internet. Does it matter HOW I'm connected? Bridging just shares the adapter, not the host's IP addresses, right?

    In other words, pfsense WAN is set to 38.external.WAN.IP (with 192.168.1.1 as DSL gateway), and LAN on pfsense is set to 192.168.0.2 ….....

    But in Windows, my physical NIC is 192.168.1.25 with 192.168.1.1 (DSL) gateway .... and my WiFi is connected is 192.168.0.25 with gateway 192.168.0.2 (wifi AP) ..

    In Windows, does it matter what my IP address setup is? I mean, should I point it to Pfsense?

  • LAYER 8 Global Moderator

    As your other thread about this..

    "and my WiFi is connected is 192.168.0.25 with gateway 192.168.0.2 (wifi AP) .."

    You DO NOT SET GATEWAYS on lan interfaces on your router!!  And it sure an the hell would not be your wireless AP!!


  • @johnpoz:

    As your other thread about this..

    "and my WiFi is connected is 192.168.0.25 with gateway 192.168.0.2 (wifi AP) .."

    You DO NOT SET GATEWAYS on lan interfaces on your router!!  And it sure an the hell would not be your wireless AP!!

    When you say you don't set gateways on WINDOWS, what do you suggest? I think you are misunderstanding my question… In WINDOWS, the PC hosting virtualbox with pfsense... if I am any at all connected to an AP (if my cable is plugged in, or if my wifi nic is connected to wifiAP), i'll have some form of address/gateway no matter what. And if I don't assign it something, pfsense won't ping anywhere at all.

    Because when I change gateways/IP's/connections from windows, it effects pfsense. When I read your comment, this is what I"m thinking, if we're on the same page: "no gateways...?":

    If I'm not connected to a gateway, then….. the bridge is useless because it can't reach any network O__o

  • LAYER 8 Global Moderator

    I did not say you don't set a gateway on windows.. If you had your details in 1 freaking thread vs all over the board..  You don't set a gateway on PFSENSE LAN interfaces!!!

    "You DO NOT SET GATEWAYS on lan interfaces on your router!!"

    Where did you get windows from that?  Look in your other thread where I posted a picture of your pfsense lan showing a gateway of your AP?? :rolleyes:


  • @johnpoz:

    I did not say you don't set a gateway on windows..

    I assumed that, but that's my entire question, though: What should the IP+gateway be in Windows?

    If you had your details in 1 freaking thread vs all over the board..

    Well, no one helped, maybe overwhelmed with too much information – breaking down into smaller questions at least gets me somewhere. You responded here and not my mega-thread, so I suppose that answers your question.

    You don't set a gateway on PFSENSE LAN interfaces!!!

    Well yea .. there is no gateway set for LAN interface. I type in 192.168.0.1 for LAN interface and there's a drop-down box beside it for gateway and [None] is selected. Got this part.

    "You DO NOT SET GATEWAYS on lan interfaces on your router!!"

    On my router LAN Router (Wifi AP)? It literally won't let me set a gateway, just a static IP address (192.168.0.2 for wifi AP on LAN subnet).  (??)

    Where did you get windows from that?  Look in your other thread where I posted a picture of your pfsense lan showing a gateway of your AP?? :rolleyes:

    Oh, you mean from like a week ago? O__o I've updated a lot since my first post. Pfsense lan has no gateway. Here is my most updated network layout (wayyy cleaner than my epic thread's 1st post): https://docs.google.com/presentation/d/1tkv4f54K9KuRVhPLdwBzgcaeBpYM4kzgtFTgbtkMA_w/edit?usp=sharing

    But most importantly:
    My question was still not answered about Windows setup (on the SERVER hosting PFSENSE via VIRTUALBOX). What do you think the IP (which subnet)/gateways should be? The outside gateways, or pfsense (if it's pfsense and it's a bridged connection, doesn't it sort of…loop to itself without ever connecting to the gateway?):


  • If your LAN interface is 192.168.0.1, then your Windows client on LAN should have 192.168.0.2 or something else in the 192.168.0.x range.  His gateway is the pfSense LAN interface 192.168.0.1.  For your WiFi, same thing but using the OPT1 subnet 192.168.1.x.  Your WiFi client should use 192.168.1.2 with a gateway of 192.168.1.1 (the pfSense OPT1 interface IP address).


  • @KOM:

    If your LAN interface is 192.168.0.1, then your Windows client on LAN should have 192.168.0.2 or something else in the 192.168.0.x range.  His gateway is the pfSense LAN interface 192.168.0.1.  For your WiFi, same thing but using the OPT1 subnet 192.168.1.x.  Your WiFi client should use 192.168.1.2 with a gateway of 192.168.1.1 (the pfSense OPT1 interface IP address).

    This is great – thanks mate!


  • Don't mention it, and don't take anything said above personally.  You gotta roll with the punches in the tech trenches.