VLANS
-
Thanks…just before your post I did that....opt1 keeps resetting on me after I configure it??
sorry i dont know about that one sounds very odd. might want to try ifconfig on a console and see if you vlans look like they are configured correctly you can also check this out in the assign interfaces area of web gui under vlans
-
Yes the interfaces disappears after I enable OPT1.
I am using "1.2 BETA-1-Prerelease-snapshot-04-23-07"
-
Also once I enable VLANs I loose connectivity.
I have the swr2008MP –-- trunk ----- pfsense. Is there an issue with trunking in pfsense??
-
Whatever I have tried I cannot get vlans to work….I am wondering if it is a pfsense issue.
I am using swr2800mp linksys switch......I am sure if it is not a pfsense issue I would have been done if this was a Cisco IOS switch. :(
-
when you say trunk i assume u mean the port that pfsense is plugded into is configured as a trunked port.
i also assume that all vlans you configured in pfsense are in this trunk you setup on your switch.i am a bit old school but i add all the vlans i want to my switch then add all the tags i want pfsense to see the port pfsense is attached to.
then i might have port vlan tags on other port or tagged vlan ports on other ports or trunks that go between switch 802.1q is a standard and any cisco switchs i have worked with have been fine. -
Switch is trunked to pfsense and is tagged with VLAN10 annd VLAN20, and untagged VLAN1.
I can communicate with all devices on the VLAN10 no problem…..even when I connect the pfsense box with out any VLANs and just an assigned IP connected to an access port it is fine.
It is when I configure VLANS on the pfsense and connect it to the trunk it looses communications.
pfsense
I go to -interfaces - assign - create vlans 10 and 20
Then I go to LAN and assign VLAN10
Then I add OPT1 which is vlan20
*as I mentioned the pfsense box is connected to a trunk port that is tagged with vlan10 and vlan20.Everything breaks I can no longer get to the pfsense box?
-
sounds like the re driver might be havin problems you might want to check on the freebsd lists for issues with this or try to add the vlan on the command line and see if it works we have no trouble with vlans but only use sis and fxp nics
-
Do you have a link I can check out, and/or do you have the info on creating the vlans from command line.
Thanks!
-
Whatever I have tried I cannot get vlans to work….I am wondering if it is a pfsense issue.
No, it's not. VLAN's work fine, and are dead simple to setup. They were a ported feature from m0n0wall, worked fine initially and always have. Properly setting up the VLAN's on the switch is another matter entirely. If it's not working, it's your switch configuration.
It's possible, but unlikely, that it's related to a NIC driver bug. I may have time to look closer at this tomorrow, haven't had time to read all the info posted since my last post. At this point, my most specific suggestion is fix the switch.
-
I hope you are right….but the switch is configured correctly (swr2800MP Linksys unless there is issues with this switch).
I have set up vlans and trunks for years but on cisco equipment. I will try another type of switch today and see.
The nics in the pfSense box are realtek 8110sc.
Any other suggestions or help would be appreciated.
Again here is what I have setup.
--VLAN10 and VLAN20 swr2800mp switch--------Trunk (tagged 10 and 20) ------ pfsense (LAN = VLAN10 and opt1 = vlan 20) the minute i configure the pfsense I loose connectivity.
-
If you got a spare nic use that as lan… and re1 for the vlans only
here is a fast made wink vlan demo :)
http://www.mediamax.com/crazypark/Hosted/hmm.swf -
It may of been the switch although configured correctly it did die on me today…
I will let you all know once I get it replaced.
Thanks all for the info
-
I had the same issue. After assigning the lan net to vlan0 no communication over this interface was possible although the switch port was configured correctly.
While searching a solution I did a reboot of the pfsense box and after that all vlans are working fine.
First I won't believe that so I reseted the pfsense to factory defaults and I could reproduce this behavior. In the testing machine a realtek nic is used so I don't know if this behavior has to do with the rl driver or if you have to do a reboot with all nics.
I hope I will get my new intel hardware soon so I can test if there is also reboot required using an intel nic.
-
fwuser07: That reminds me! ;D I had the exact same problem with my VLAN router, though it's running an OLD release (1.0-RC3…heh). I meant to attempt to duplicate the issue I saw, where my VLAN's wouldn't work until a reboot, but forgot about it until I saw your post.
My VLAN trunk interface is a Realtek 8169 on a FX5620 donated to the project courtesy of LinITX.com.
http://linitx.com/product_info.php?cPath=4&products_id=909So maybe it is a Realtek driver issue? The interfaces are created properly, IIRC, they just didn't work until after a reboot. What pfsense version are you using?
Please let us know if you can duplicate the issue with Intel or any other NIC's. We may need to build in some logic to require a reboot after VLAN configurations.
-
I was testing with the stable version 1.0.1 and 1.2-BETA-1.
Before rebooting the following message appeared in the system log:
kernel: arp: x.x.x.x is on vlan0 but got reply from 00:0e:6d:45:80:ae on vlan1
(x.x.x.x is an internal ip address) -
realtek… :(
toss an intel in there :P $30CAD
-
I finally got the Tyan S3095 with two Intel PCIe nics onboard and the following things happened:
I also had to restart pfsense after aktivating vlans. After assigning a new vlan pfsense needs 2-3 minutes to transmit the request and it happened once that pfsense suddenly restarts after clicking the save button for a new vlan.
But the most important thing is that after assigning all vlans pfsense seems to work great :)