Not familiar with what fx(4) em(4) refers to.  Heres the layout.
Console Output
WAN > xl0 > x.x.x.x DHCP
Op1 (WAN2) > rl1 > x.x..x.x (static ip on dsl line)
Opt2 (Bench) > vlan0 > 192.168.10.1
LAN > vlan1 > 192.168.5.1

Pfsense has 1 nic rlo going to port 25 on Dell switch.
Switch config. port24 on vlan1.. ( Port 25 Tagged, Port24 untagged)
Port 1 untagged Port25 untagged ( Vlan3)

Vlan1 works without issue and gets dhcp to nic.
Vlan3 times out on dhcp. Put in static ip and cant ping on it either.Made a rule in the pfsense on the Bench section of Source (Bench) any Destination any to allow but no change. If I put port 1 onto vlan1 it will get an ip rom vlan1 so I know its working. I made sure the dhcp was turned on and the interface enabled.

If there is something elese that would help I can get it.

Hope this helps. As I am anxious to get it working properly so I can implement it into our network. and everyones input is appreaciated


Rainer Duffner wrote:
Mousemen schrieb:
on the NIC's 2 are surplus realtek and not sure on the 3rd one. The lan nic is on the realtek though. Might there be an issue with the nic passing the vlan tagging even though the pfsense states only nics capable of it are listed.

Use fxp(4) or em(4), when in doubt.

Can you list the console-output of pfSense, so that we see which VLAN is which? I wouldn't connect the switch to multiple ports of the pfSense (I'm not sure if you did this).
Just use one port and trunk all VLANs on it.

Would you be able to draw a little ASCII-chart of what your setup looks like? So that we see which physical interface (and which pfSense VLAN interface) connects to which switch-port (and what configuration the switch has on that port).



cheers,
Rainer

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to