LAN DHCP + VPN=OK + MGM static cant route?



  • Hello,
    I just switched to pfSense and i just love the product and it feels very competent, i have now stumbled over some issues:

    pfSense latest stabile version hosted virtually in VMware.
    2.4.4-RELEASE-p3 (amd64)
    built on Wed May 15 18:53:44 EDT 2019
    FreeBSD 11.2-RELEASE-p10

    Network Layout:
    WAN = vmnic1 = vSwitch as "WAN pfSense" added over pfSense VM
    LAN = vmnic0 - vSwitch as "VM Network" added over pfSense VM
    MGM = virtual Network Card connected to "VM Network" added over pfSense VM

    I have now successfully setup LAN and 1WAN and 3 VPNS: Interface Overview

    The traffic works but i have a feeling this product is really sensitive on blocking ports (blocks to much)
    I have a LAN with an DHCP of subnet 192.168.1.0/24.

    I added a Management Network of 172.21.3.0/24 with an own interface and itself as uplink adress.
    Just wanted a static network for servers that can route out in one of the VPNs.
    But i cannot get the traffic through, have tested via DHCP as well as test according to dums.

    nslookup works over google.se 192.168.1.1 or 172.21.3.1 but the traffic or ping wont get pass as static IP of 172.21.3.10 or as under DHCP enabled in that interface with 172.21.3.1 as DNS. I guess its the routing that is messed up?

    If i set upstream gateway over MGM interface to 172.21.3.1 i cannot run nslookup to any of above but the ip 192.168.1.60 (default of LAN DNS server)

    Screendumps of Settings

    DNS Resolver is used over all Networks and outgoing interfaces.
    Its like the subnet of 172.21.3.0/24 does not have any route or is completly isolated. I have read several guides and forum posts without luck.

    Any tip is mosly welcome sine the MGM network is isolated :)
    'Thanks



  • Hello,

    Actually this post helped me
    And this one with check if the outbound NAT rule is set on Automatic.


Log in to reply