NAT/Portforward VIPs block
-
I have two static IP blocks one is 63.232.xxx.xxx/26 used solely for the Pfesense and 65.155.xxx.xxx/28 (For VIPs on VLAN6). So Im using VLAN 6 for the /28 and would like to get the IPs port forward or using NAT because clients will be using their own routers and they will be using it for FTPs and etc. I don't want to worry about doing port forwards all the time. Would like to port forward or do a NAT on the IP address I give them from the VIPs block so all the outside traffic for that address will only go to that specific device. Would like to have a separate GW just for the /28 but using the same WAN interface? The /28 is routed to the /26 from the ISP. How would be the best way of doing this? screen shots would be a huge help and thank you.
-
You should be able to do this without NATing at all. Just use the /28 directly in VLAN6 if it's routed to you.
Use the first IP in the subnet on the VLAN6 interfaces in pfSense and other IPs directly on the clients. They will use the interface IP as their gateway.
Just set outbound NAT to manual mode and then remove the NAT rule for the /28 subnet.
Then add firewall rules on your WAN to allow traffic into the /28 as required.
Steve
-
Thank you Stephen. I'm just having an issue with the rules now. I able to get incoming traffic but outgoing to blocked. For example, have a laptop I'm using to test it and I'm able to remote into it. But when I go to a website it fails to connect. How would I set up the firewall for outgoing traffic?
-
You need a firewall rule (or rules) on the vlan6 interface to allow traffic from clients on that to reach external services.
On LAN there is a default rule to pass that traffic but on all other internal interfaces it must be added.
Steve
-
Steve,
Im still having an issue with the rules. Could you help/explain to me how to set up source/destination for the rules for this? I'm kind of struggling with it. Thank you.
-
To just allow traffic out from clients on the VLAN6 subnet you just need a single rule on the VLAN6 interface.
Action: Pass
Interface: VLAN6
Protocol: any
Source: VLAN6net
Destination: anyThat will allow clients to reach any other IP.
Steve
-
Would I have to do any rules on the LAN since its a VLAN using the LAN interface? Still getting a NO_TRAFFIC:SINGLE on the VLAN6.
Current LAN rules allow all. But not sure I have to be more specific for that VLAN so I'm using it for a direct connection.
-
If you created a vlan, the rules on the parent interface - ie lan say has ZERO to do with traffic on vlan
-
Is there a dump file I can do that you could look at to see if I'm overlooking something?
-
you can sniff sure, just use tcpdump.. if you use -e with tcpdump you can see the vlan tags..
If if the rule on the parent physical interface had anything to do with the traffic on the vlan - then vlans would be completely USELESS nonsense since you wouldn't actually be isolating the traffic. Might as well just run multiple layer 3 on the same layer 2 in such scenario..
You can also sniff using the diag / packet capture web gui.. But doesn't allow you to see the vlan tags because you can not call out -e
Where exactly are you seeing
"NO_TRAFFIC:SINGLE on the VLAN6."What state exactly... That info doesn't mean much without more context.
What exactly is not working? What do you have configured on your switch to allow for the vlan6 you setup, guessing you used vlan ID 6 when you setup that vlan in pfsense? So you have trunk connected to your physical interface on pfsense frm your switch, and then port where you laptop connected via untagged access port in vlan 6, etc.
-
Have you actually created a VLAN6 interface in Interfaces > Assignments > VLANs?
Steve
-
When I look at the "States Detail" under rules for VLAN its stating NO_TRAFFIC:SINGLE" Im unable to get online.
I have a trunk port setup on my switch and my other VLANs are working properly but using a local subnet. I do have Port 6 tagged for VLAN 6.I disabled all the NAT for VLAN 6 and keep the rest all the same.
Steve: Yes I have VLAN 6 created and I have the public IP block assigned to that interface.
What specific rules I would have to create on the WAN?
-
You shouldn't need any rules on WAN to allow traffic out from the VLAN6 subnet.
Try to ping out from Diag > Ping choosing the VLAN6 interface as the source address.
It sounds like maybe your ISP is not actually routing that subnet to your WAN IP.
Steve
-
I cant ping from that interface. this is what the ISP sent to me
set routing-options static route 65.15X.XXX.X44/29 next-hop 67.1XX.XXX.198
set routing-options static route 63.23X.XXX.X76/28 next-hop 67.1XX.XXX.198
So I used the /29 for the WAN and the /28 for VLAN6
-
So they directly attached it to you... Not routed it..
-
Ok knowing that now. How would I go about configuring the IPs then?
-
Get them to actually route it to you... Or you would have to use vips and port forwarding.
They are also having you set gateways outside the IP block... Not very good idea to be honest as well.
-
If i were to use VIP and port forwards would I have to port forward any devices they use on the network or can you they do that through there firewall? Also with the portforward what IP would be used for the gateway?
-
@johnpoz
Could I just assign another nic interface for that second IP block? then Have the VLAN go to that? -
No. The ISP should route 63.23X.XXX.X76/28 to an address in 65.15X.XXX.X44/29. They should provision your service properly.
