NAT/Portforward VIPs block
-
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.
-
Thank you all for your help. I got the ISP to route the IPs and it worked how you all explained it.
-
Nice.
