• 0 Votes
    1 Posts
    5k Views
    No one has replied
  • splitting a subnet, moving from LAN to WAN

    9
    0 Votes
    9 Posts
    79 Views
    S

    When I try to ping an IP that has not been used before and in the LAN-part (10.96.25.128/25) from "upstream"/"outside", it gets logged on the pfsense as blocked by the firewall (which is OK in terms of fw-rules).

    So the pfsense seems to take over traffic pointed to these IPs.

    Could I modify NAT-rules maybe? Is that related to Outbound NAT? Could I somehow exclude

    I requested a DNS-change from their network admins. If the new vms are located in the lower /25 things should work and I can go on with my actual work ;-)

    (but I'd be happy to learn about the reasons for this behavior anyway)

    EDIT: DNS-change requested, so I don't have to actually do something on the pfsense right now. Still interested, though. thanks all.

  • Intermittent Failover to Backup WAN – Unable to Reach Firewall GUI/SSH

    1
    0 Votes
    1 Posts
    6 Views
    No one has replied
  • 0 Votes
    2 Posts
    92 Views
    N

    @E-I
    I'll second that.
    I get the same issue.

  • sticky connections ignored

    1
    0 Votes
    1 Posts
    20 Views
    No one has replied
  • Load Balancing with Multiple ISP

    1
    0 Votes
    1 Posts
    34 Views
    No one has replied
  • Traffic flows to wan not other subnet

    1
    0 Votes
    1 Posts
    46 Views
    No one has replied
  • VoWiFi slow failover when using GW Groups

    1
    0 Votes
    1 Posts
    32 Views
    No one has replied
  • Routing problem?

    1
    0 Votes
    1 Posts
    49 Views
    No one has replied
  • New PPPoE module (if_pppoe) causes high cpu usage and cause lagging

    9
    0 Votes
    9 Posts
    408 Views
    w0wW

    @cust
    You don't need to wait anything.
    You can apply this patch via system patches package, just use commit id 62b1bc8b4b2606d3b20a48a853ef373ff1d71e26

  • Ubiquiti Wave Pro Routing

    1
    0 Votes
    1 Posts
    66 Views
    No one has replied
  • Policy based routing via two IPSEC gateways.

    2
    0 Votes
    2 Posts
    76 Views
    D

    Resolved by implementing BGP peering over IPSEC.

  • Routing instead of NAT between sites

    6
    0 Votes
    6 Posts
    210 Views
    I

    Thanks again for the video. It solved my problem.

    If anyone bumps into this thread in the future, the static route showed in a screenshot above here was correct, however here's what I did wrong:

    On site2 I had set "IPv4 Upstream gateway" in the interface config to the gateway on site1. This makes pfsense NAT the traffic instead of routing it. Here's a timestamped link to the video where this is explained.

  • Multiple IPs for Monitor IP Under Gateways

    8
    0 Votes
    8 Posts
    518 Views
    M

    I really wish I could do the same here. I get some false positive failovers because the single IP monitor becomes offline, but the gateway is working fine...

    Gateway 1 monitor 8.8.8.8
    Gateway 1 monitor 1.1.1.1

    Gateway 2 monitor 8.8.4.4
    Gateway 2 monitor 1.0.0.1

    Gateway 3

    Then prioritize them and route following this order.

  • Tailscale Connections

    2
    0 Votes
    2 Posts
    77 Views
    W

    OK, I think I just figured it out!! I didn't have the subnet enabled. Not sure how it happened, but it now seems to be working. I can open the printer's web page!!

    Now I can revisit things.

  • 0 Votes
    47 Posts
    3k Views
    stephenw10S

    Do you see errors on the parent interface?

    You can try the dtrace commands shown in this thread and see if you're hitting some error other than 55 (no buffers).

  • Truenas VLAN jellyfin return route wrong

    2
    0 Votes
    2 Posts
    102 Views
    4

    @4o4rh i am struggling to get policy based routing working on truenas scale.
    either i get the situation where non-media vlans can access the jellyfin server on the media vlan (but then the truenas/smb vlan is not accessible, or the truenas/smb vlan is accessible by not the jellyfin vlan (other than from a device on the vlan).

    It both cases the non-accessible vlan is appearing on the wrong pfsense interface.

    so, it seems truenas is returning via the default route rather than the desired return route

  • PPPoE module (if_pppoe) in DSL environment

    1
    0 Votes
    1 Posts
    57 Views
    No one has replied
  • WAN2 on Netgate SG-2100 not working

    2
    0 Votes
    2 Posts
    63 Views
    I

    Ignore this

    For anyone maybe suffering with similar issues, I went through the guide again and realised I'd forgotten to update the Port VID under Interfaces > Switch > Ports as well as updating the VLAN Tag under Interfaces > Switch > VLANs

    Once that was done it got an IP and I could use it as a WAN port.

  • Tailscale to pfsense forwarding to another site connecte

    1
    0 Votes
    1 Posts
    47 Views
    No one has replied
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.