1. Home
  2. pfSense® Software
  3. NAT
Log in to post
Load new posts
  • N

    Strange redirect rule

    2
    0 Votes
    2 Posts
    617 Views
    KOMK
    What do you have for Firewall - NAT - Port Forward?
  • E

    Multiple Source IP addresses

    3
    0 Votes
    3 Posts
    2k Views
    E
    KOM, Perfect. Thanks, ~eric
  • jimpJ

    MOVED: NAT vers deux IP Interne

    Locked
    1
    0 Votes
    1 Posts
    541 Views
    No one has replied
  • C

    Nat 1:1 and limit vpn trafic

    1
    0 Votes
    1 Posts
    640 Views
    No one has replied
  • C

    How to create logical subnets with a single Lan interface without VLAN?

    30
    0 Votes
    30 Posts
    8k Views
    H
    @cceraja: Hello Derelict, I agree that it may not be a standard way. But still when a feature is there why not exploit it? Look at the advantage it has… You don't need additional switches and additional nic for subnets. Regards, Raja That's not a feature, it's an undefined configuration that is highly recommended against. Kind of like people using a high or low IP address of a subnet. It can work in some setups, but expect strange stuff to happen.
  • E

    Problem whit NAT on different subnet

    3
    0 Votes
    3 Posts
    1k Views
    E
    Many thanks for your reply, Ok with the manual outbound nat enabled and the rule of SNAT I reach perfectly the server on port 81 from the outside However, though the subnet 192.168.2.x / 24 does not reach server 192.168.1.200 on port 80. Instead, if I enable automatic outbound nat perfectly reach the server 192.168.1.200 on port 80 but not the server 192.168.10.230 on port 81. I forget what? thanks again
  • P

    PROBS: HA setup (carp) with uplink failover and SIP-traffic not switching uplink

    3
    0 Votes
    3 Posts
    1k Views
    P
    We upgraded to 2.1.5. If I am right there was something about that in the version-info. With the new version it works because they changed things in the behavior on CARP failover regarding to deleting states. Best regards Patrick
  • O

    Configuring static port numbers

    2
    0 Votes
    2 Posts
    850 Views
    KOMK
    1.  If you have Auto NAT Rule generation on, which it is by default I believe, then the required rule should be created. 2.  If you have Manual enabled before you created your port forward then you will have to create the firewall rule. I had an issue like this where I had to ensure VoIP packets leaving WAN had to be within a specified port range.  I think I just had to create the WAN rule and that was it.  I'll check in the morning.
  • jimpJ

    MOVED: NAT nao funciona

    Locked
    1
    0 Votes
    1 Posts
    552 Views
    No one has replied
  • R

    Suggestion for double nat

    7
    0 Votes
    7 Posts
    2k Views
    R
    THANKS A LOT!!!! really I'm very happy to have always answers from someone, so this is one reason more to install pfsense and to know any problems u can ask in forum and someone is ready to help u. bye and again thanks. roberto
  • 0

    NAT and OpenVPN - trying to understand how this works

    6
    0 Votes
    6 Posts
    2k Views
    0
    Yeah, that's how much I understood of it as way. I just don't understand why that "default route" is nowhere to be seen in the GUI. That made it so much more harder to understand what's happening. Thanks for the explanation though
  • R

    Website access works for some but not others

    3
    0 Votes
    3 Posts
    725 Views
    R
    It worked right up to the moment I added the pfsense box. So I knew it's not the ISP. Its a setting blocking it somewhere. I'll just have to keep poking around. Thanks, Rick
  • panzP

    Manual Outbound NAT rule generation not automatically populated with Automatic

    3
    0 Votes
    3 Posts
    1k Views
    panzP
    For a reason that I don't know, NAT reflection was disabled. When I enabled it, the Outbound rules came back. Why?
  • M

    [2.1.5] Firewall rule generated by NAT page ignored

    2
    0 Votes
    2 Posts
    701 Views
    P
    From pfSense side that all looks good. Are there settings in TeamSpeak that would restrict it to responding only to connects from local LAN IPs? Or some subnet of "all"?
  • J

    SSH Portforward doesn't work, still get pfSense ssh.

    2
    0 Votes
    2 Posts
    917 Views
    ?
    Set up the interface as the modem's vlan. Can't get the rule to fire up if it's not listening on the right interface.
  • S

    Port forward external port to different internal port [SOLVED]

    6
    0 Votes
    6 Posts
    5k Views
    S
    @Wolf666: Should be: port forwarding WAN  TCP  *  *  WAN address  8888  192.168.0.100  80 With firewall rule on WAN tab: IPv4 TCP  *  *  192.168.0.100  80  *  none The firewall rule did it.  That seems kind of weird how you have to do that.  Dest 192.168.0.100 dest port 80. Makes me feel like I'm opening up port 80 to the world, even though I'm not.  So I just did some testing, it seems like the rule only needs to be written like that if your doing port redirection. Just before I read this I was looking in the logs, and saw it blocking my public source, with destination of 192.168.0.100:80. Thanks for the help!
  • M

    Pfsense NAT Before VPN

    2
    0 Votes
    2 Posts
    1k Views
    dotdashD
    You would have to BINAT on both sites.
  • J

    NAT over OpenVPN to IPSEC

    3
    0 Votes
    3 Posts
    764 Views
    DerelictD
    Can this diagram be used to describe what you're wanting to do? https://forum.pfsense.org/index.php?topic=82732.0
  • I

    [SOLVED] Outbound NAT - ModemAccess

    Locked
    12
    0 Votes
    12 Posts
    2k Views
    johnpozJ
    And now your pfsense thinks it has a WAN connection going to your gateway device "My Modem".. No modems have seen have that IP ;) Dude I am not talking about a portforward, I am talking about an outbound NAT from your lan to your new opt1 interface, this is not the same inbound nat or portforward for devices on your lan from the internet.  Change your outbound nat from auto to manual and post your rules.  You will see a nat from your inside network to your opt1 network.  With all due respect its not rocket science here ;) I don't really care how you setup your system - just pointing out that the instructions are correct, if followed correctly ;)  You don't set a gateway on a interface that is just talking to that segment, a gateway on an interface is a WAY off that segment..  That is not needed to talk from 192.168.0.5/24 to 192.168.0.1/24 for example
  • D

    GW IP address that publishes the pfsense LAN interface

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