Which card needs to support it? The equipment on the end (computer) or
the card in the pfsense box.
Kevin Benton wrote
What you have setup is a trunk port. A trunk port is just a term used
(when referring to VLANS) to describe a link that is tagging egress
packets with VLAN id's so a device on the other end can differentiate
the frames from the unique VLANs.
It looks like you have the switch correctly configured. Just to be
clear, the port on the switch that connects to the pfSense should pass
*tagged *traffic from both VLANs. Make sure the switch is set to use
802.1q VLAN tagging rather than port based VLANs or ISL VLANs. Also be
sure to check that the VLAN numbers that you enter in pfSense match up
with the numbers of the VLANs on the switch.
Otherwise, be sure the card you are using supports VLAN tagging, I
wasted a reasonable amount of time troubleshooting a card that turned
out to not support it.
On Tue, Jun 3, 2008 at 2:16 PM, Paul Peziol <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
- Hide quoted text -
Not sure if anyone had looked at the config file but since i have not
heard back I decided to start over. Did a clean install of pfsense.
Not sure if I have the dell powerconnect switch configured correctly
but get different stories. There is only 1 switch and some say I need
a trunk port some say no.
Heres the Layout for now that I want to get working
[Pfsense]
_______|________________
| |rl0 (wan2 later) |
{WAN-xl0-Dhcp} {Network} LAN (
vlan1 on rl1), Opt1(vlan2 on rl1)
|
|
Dell
PowerConnect 3024
|\
Port25
(Links to pfsense box) Port24- test port1( vlan1 - port25 tagged,
port24 untagged) / Port1 test port 2 (vlan2 port25 tagged, port1 untagged)
In the pfsense box set LAN to vlan1 on rl0, Switch set port25 tagged
and port 24 untagged and unable to get traffic across. Before I was
able to set LAN to vlan1 and move traffic across port 24 but then when
added the 2nd vlan and setup vlan2 as tagged on port25 untagged port1,
Port1 would not get a dhcp address, Set manually still no traffic. I'm
almost at the point in thinking something is wrong with the switch
passing vlan traffic. I did update the firmware to the newest version.
Never have worked with vlan's before and I am trying to learn this so
I could implement it at work by the time our phone system gets put in
place which will be based on asterisk and therefore want to separate
the clients computers that are viruses infected from our network that
also has a server on it. Currently running on 2 differenent routers to
separate the 2. Thank you in advance.
On Wed, May 28, 2008 at 2:28 PM, Mousemen <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
config-pfSense.local-20080528142627.xml
<http://?ui=2&ik=72a65a1505&attid=0.1&disp=emb&view=att&th=11a3100cb4bc3c07>
Reset pw to the factory default
I took out the WAN2 ip as that is a static ip. The WAN is set to dhcp
for now. Let me know if I need to do anything anything else. The lan
ip I'm not worried about as it is a test network for now and will
change once in production
/Wed, 28 May 2008 09:14:30 -0500 (Central Daylight Time), Curtis
LaMasters <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>:/
Please send your config.xml with passwords and IPs changed.
--
Curtis LaMasters
http://www.curtis-lamasters.com
http://www.builtnetworks.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
