Pfs VM Not picking up WAN IP - Solved by Updating to pfs 1.2.2 VM



  • I rewrote this post because I think my jpg was too small to explain the issue.
    Setting up pfs (1.2.1) VM as a firewall running under WinXP & WMserver 2.0. The WAN is a wifi connection to my current router.

    After setting up pfs, I can access the web interface but there is no IP reported on the WAN. I have tried assigning a fixed IP, which also fails.

    pfs shows:    WAN*    ->    le0   ->   None
          LAN*    ->    le1   ->   192.168.229.1

    On the host the wifi nic (intended for pfs WAN) is set to use ONLY the VMware bridge protocol. (wifi is connected to my external router and if I turn on the IP protocol, it picks one up.)

    In VMware;
    First nic is bridged to VMnet0
    Wfi nic is bridged to VMnet2.

    In pfs:
    First nic / VMnet0 goes to pfs lan
    WiFi nic / VMnet2 goes to pfs WAN

    pfs Interface:WAN
       Type DHCP    - have also tried assigning a fixed IP
       Disable the userland FTP   -  Unchecked
       Block private networks    -  Unchecked
       Block bogon networks    -  Unchecked
       All other options unchecked

    Questions:
    How do I get pfs to recognize the WAN address?

    After starting the VM, it shows a drop down for USB connections. It is titled “Plugged into Host” & shows the Wifi nic with a check box. I have tried it both checked & unchecked so I don’t think that is the problem. But should it be checked or not?

    Any help would be appreciated!!



  • You need to bridge the connection to the PF-Sense box.
    RC



  • Thanks for the reply - but I am still confused. I thought setting le1 to the WAN in pfs did the bridging? If not perhaps you could provide me a description of what is needed?

    Thanks!



  • I was seeing this on 1.2.1 also, but thought it was something weird going on with my system as it worked on other systems and nobody else has reported any issues after a few thousand downloads.

    The 1.2.2 VM is available now and it doesn't do that for me at least.



  • @cmb:

    I was seeing this on 1.2.1 also, but thought it was something weird going on with my system as it worked on other systems and nobody else has reported any issues after a few thousand downloads.

    The 1.2.2 VM is available now and it doesn't do that for me at least.

    That solved it!!  I spend close to a week trying to understand what was going on, it worked first try with 1.2.2

    Thanks


Locked