• second gateway problem

    2
    0 Votes
    2 Posts
    328 Views
    N
    Never mind, I fix it forgot to give lan access to wan1 in outbound
  • Does any of Pfsense Firewall Support IP NAT to Vlan

    Moved
    2
    0 Votes
    2 Posts
    137 Views
    GrimsonG
    https://docs.netgate.com/pfsense/en/latest/book/ have fun reading.
  • Fundemental concept question - Router on a stick with L3 inter-vlan

    1
    0 Votes
    1 Posts
    104 Views
    No one has replied
  • Kill WAN2 states on WAN1 back up?

    1
    0 Votes
    1 Posts
    120 Views
    No one has replied
  • Load balancing between 4G and VDSL, random stalls and network errors

    2
    0 Votes
    2 Posts
    281 Views
    A
    Done further checking as my VDSL line has an MTU of 1500 but the 4G only handles 1440. Could it be the constant switch between the two that is tripping up the web browser?
  • [SOLVED] Dual WAN failover, can't access 99% of the websites. Need help

    Moved
    12
    0 Votes
    12 Posts
    1k Views
    pfrickrollP
    @grimson Ok, I see it now. Lots of things makes sense, thank you.
  • Stretched LAN cannot 'route' to other VLANS

    1
    0 Votes
    1 Posts
    381 Views
    No one has replied
  • Dpinger: sendto error: 55 under Gateways Log

    1
    0 Votes
    1 Posts
    333 Views
    No one has replied
  • VPN and Layer 3 Switch

    Moved
    2
    0 Votes
    2 Posts
    292 Views
    johnpozJ
    First thing is make sure you not pulling routes from your vpn service. Doesn't matter if the vlans are directly connected to pfsense or not, still just a simple policy route. Just set your firewall rules for your policies for your downstream vlans on your transit interface that connects to yoru downstream router. BTW moved this to routing section, has zero to do with openvpn.. What your asking about is policy routing.
  • No default route after reboot using Gateway Groups.

    32
    0 Votes
    32 Posts
    5k Views
    0daymaster0
    @rico This fix works for both IPv4 and IPv6. Thanks.
  • Asymmetric routing with VTI

    17
    0 Votes
    17 Posts
    2k Views
    B
    Came here to backup @candlerb. We're used to ECMP routing across two VTI tunnels on ASRs and such, but the ASA (due to the asymmetric path check) doesn't allow this. This seems to be due to the ASA assigning an outbound VTI interface (E.g. VTI1) to the flow state table and mandating that return traffic also return on that external interface, when in realty BGP will load balance return flows to VTI2. It definitely presents a confusing issue at first. Our way around this is to disable multi-pathing by decreasing outbound MED advertisements and increasing LOCAL_PREF for a designated 'primary' VTI interface.
  • Real multi-WAN bonding through remote firewall

    2
    0 Votes
    2 Posts
    285 Views
    L
    Are you trying to setup a L2 site-to-site connection with your suggested VPS?
  • Invalid static routes

    7
    0 Votes
    7 Posts
    1k Views
    S
    Hi Actually VPC's DHCP server issued non-canonical interface address 10.162.0.10/32 with gateway 10.162.0.1 for network 10.162.0.0/20 I think the reason is that VM attached not to real (not to emulated) ethernet. and all communication should performed via GW Routing table looks (look at vtnet1 routes): Internet: Destination Gateway Flags Netif Expire default 10.200.0.1 UGS vtnet0 10.162.0.0/20 10.162.0.1 UGS vtnet1 10.162.0.1/32 42:01:0a:a2:00:0a US vtnet1 10.162.0.10 link#2 UHS lo0 10.162.0.10/32 link#2 U vtnet1 10.200.0.0/24 10.200.0.1 UGS vtnet0 10.200.0.1/32 42:01:0a:c8:00:0a US vtnet0 10.200.0.10 link#1 UHS lo0 On linux (another instance) qq@vm-1:~$ ip r default via 10.162.0.1 dev ens4 proto dhcp metric 100 10.162.0.1 dev ens4 proto dhcp scope link metric 100 qq@vm-1:~$ ip n 10.162.0.1 dev ens4 lladdr 42:01:0a:a2:00:01 REACHABLE @vm-1:~$ ifconfig ens4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1460 inet 10.162.15.221 netmask 255.255.255.255 broadcast 0.0.0.0 inet6 fe80::4001:aff:fea2:fdd prefixlen 64 scopeid 0x20<link> ether 42:01:0a:a2:0f:dd txqueuelen 1000 (Ethernet) RX packets 383 bytes 502096 (502.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 365 bytes 49133 (49.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
  • Multi-Pfsense firewall CARP and NAT Help

    3
    0 Votes
    3 Posts
    438 Views
    DerelictD
    You need a WAN CARP VIP on each WAN and set Outbound NAT to use that. What you have is an invalid HA configuration. Both WANs should be on both firewalls in a Multi-WAN configuration.
  • (Install) files blocked when downloading via shell (browser OK)

    4
    0 Votes
    4 Posts
    220 Views
    jimpJ
    "No address record" means one of two things: It can't reach the Internet, typically because there is no default gateway in the routing table. Check your gateway settings, make sure the default is set as expected, then save/apply. If you are using a gateway group as default, try it with a single WAN gateway. Look under Diagnostics > Routes and see if you have a default listed. Your DNS settings are not correct or it otherwise cannot reach upstream DNS servers.
  • pfSense on WMware Workstation

    2
    0 Votes
    2 Posts
    387 Views
    N
    I read a bit more about it and I think I must use vSphere Hypervisor. Thank you
  • L2TP over PPPoE - still not possible?

    1
    0 Votes
    1 Posts
    245 Views
    No one has replied
  • Virtual IPs and Blackhole/Static Routing

    1
    0 Votes
    1 Posts
    243 Views
    No one has replied
  • Multicast routes not being received through IGMPproxy

    3
    0 Votes
    3 Posts
    557 Views
    M
    Fun fact, if I start pimd without a proper configuration (only interfaces are correct), kill it and then start again igmpproxy, it works. Multicast routes are correctly received. Does anyone know the reason of this behaviour ?
  • Gateway group tier priority not being followed

    5
    0 Votes
    5 Posts
    391 Views
    S
    See down below for screenshots of router1. So I have done some more testing and have narrowed it down. When using a PC on this router1's LAN, downloading is using WIFILink1 and uploading is using WIFILink2. So I changed the Firewall rules not to use the gateway group but to use only the WIFI2_GW on both routers. Router1:[image: 1550870097765-07a1e25f-edcb-43bc-8c74-1b156950e876-image.png] Router2:[image: 1550870865462-71e4ffd4-949d-495b-9292-45bdee09f186-image.png] Some traffic is still using WIFILink1. I am not sure how. See traffic graphs on router1 after I disabled the WIFILink1 interface and then enabled in on router2 with the above rules to use WIFI2_GW and WIFI_GW_2: [image: 1550870648617-3d806ef3-a5bc-458e-93ad-9c6940e2d28e-image.png] Maybe I am missing something in my settings or my understanding. Router1 screenshots: [image: 1550790414172-4b984daa-0422-4924-a48c-a5262e12a007-image-resized.png] [image: 1550790448682-ec6ded53-07eb-4fcd-b0e7-be4665ed1796-image-resized.png] [image: 1550790758303-b40b524e-5191-470d-a5bf-3d3e9540cda2-image.png] [image: 1550790796184-2db95bef-d01a-433f-aab2-98f9fd59a9ed-image.png]
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.