F5F Stay Refreshed Power Users Networks Pfsense transparent vlan trunk configuration

Pfsense transparent vlan trunk configuration

Pfsense transparent vlan trunk configuration

Pages (3): 1 2 3 Next
P
Playered_401
Member
60
06-16-2016, 05:39 AM
#1
You have a Cisco Transparent Firewall acting as a trunk port between your router and switch, but certain VLANs are blocked. You need to configure PFSense to forward all VLANs through the firewall. Set up appropriate trunk configurations for each VLAN range you listed. Ensure proper routing rules inside PFSense allow traffic from those ranges to reach the internet. Adjust ACLs or routing policies as needed.
P
Playered_401
06-16-2016, 05:39 AM #1

You have a Cisco Transparent Firewall acting as a trunk port between your router and switch, but certain VLANs are blocked. You need to configure PFSense to forward all VLANs through the firewall. Set up appropriate trunk configurations for each VLAN range you listed. Ensure proper routing rules inside PFSense allow traffic from those ranges to reach the internet. Adjust ACLs or routing policies as needed.

U
UnPetitPoney_
Member
70
06-26-2016, 05:19 AM
#2
Not sure about bridging in FreeBSD (PFSense relies on this), but in Linux you’d need to add VLANs to the bridge. A bridge acts like a software switch, and VLANs on switches must be set up manually unless the device is very simple.
U
UnPetitPoney_
06-26-2016, 05:19 AM #2

Not sure about bridging in FreeBSD (PFSense relies on this), but in Linux you’d need to add VLANs to the bridge. A bridge acts like a software switch, and VLANs on switches must be set up manually unless the device is very simple.

M
mccoop03
Posting Freak
910
07-02-2016, 03:48 PM
#3
They request a parent interface, but you have your physical interfaces, not the bridge. Got it.
M
mccoop03
07-02-2016, 03:48 PM #3

They request a parent interface, but you have your physical interfaces, not the bridge. Got it.

G
GumiBears
Senior Member
256
07-02-2016, 05:42 PM
#4
It seems FreeBSD and PFSense offer a less extensive set of bridge features compared to Linux. You’ll likely need to define your VLANs directly on the physical interfaces, then set up a separate bridge for each one—each VLAN’s members would correspond to the interfaces connected to that bridge.
G
GumiBears
07-02-2016, 05:42 PM #4

It seems FreeBSD and PFSense offer a less extensive set of bridge features compared to Linux. You’ll likely need to define your VLANs directly on the physical interfaces, then set up a separate bridge for each one—each VLAN’s members would correspond to the interfaces connected to that bridge.

1
1Kigzey1
Member
63
07-03-2016, 12:08 AM
#5
Are you connecting VLAN-LAN and VLAN-WAN, or is there another device you're linking?
1
1Kigzey1
07-03-2016, 12:08 AM #5

Are you connecting VLAN-LAN and VLAN-WAN, or is there another device you're linking?

X
XxNekoChanxX
Junior Member
19
07-03-2016, 01:54 AM
#6
Construct similar connections: -BridgeVLAN10 links LanVLAN10 with WanVLAN10; -BridgeVLAN20 connects LanVLAN20 and WanVLAN20, and so on.
X
XxNekoChanxX
07-03-2016, 01:54 AM #6

Construct similar connections: -BridgeVLAN10 links LanVLAN10 with WanVLAN10; -BridgeVLAN20 connects LanVLAN20 and WanVLAN20, and so on.

O
oOEmmaOo
Posting Freak
818
07-03-2016, 07:50 PM
#7
That's not worked, any more ideas?
O
oOEmmaOo
07-03-2016, 07:50 PM #7

That's not worked, any more ideas?

C
choppchopp
Member
156
07-15-2016, 10:26 PM
#8
The issue lies in what isn't functioning as intended.
C
choppchopp
07-15-2016, 10:26 PM #8

The issue lies in what isn't functioning as intended.

C
Crafty_02
Junior Member
5
07-22-2016, 10:14 AM
#9
I set up the VLANs and linked them to interfaces 'wan10' and 'lan10'. Then I connected them with a bridge and added the IP 10.1.10.253 without a gateway to 'vlan10br'. It seems to be working for VLAN 1 but not for others. This is confusing—why does it behave differently?
C
Crafty_02
07-22-2016, 10:14 AM #9

I set up the VLANs and linked them to interfaces 'wan10' and 'lan10'. Then I connected them with a bridge and added the IP 10.1.10.253 without a gateway to 'vlan10br'. It seems to be working for VLAN 1 but not for others. This is confusing—why does it behave differently?

N
Nicktron_
Member
199
07-24-2016, 06:45 AM
#10
You didn’t assign the VLANs as interfaces first, then edit and activate them. You also didn’t enable any interfaces afterward.
N
Nicktron_
07-24-2016, 06:45 AM #10

You didn’t assign the VLANs as interfaces first, then edit and activate them. You also didn’t enable any interfaces afterward.

Pages (3): 1 2 3 Next