Vlan(Optional Interface problems



  • I am having issues with VLANs and OPT interfaces. I have several VLANs configured in the shell and assigned to the respective OPT interfaces. I can activate and assign IPs to the OPT interfaces. However the following image is what I get when I try to reassign the vlans to OPT interfaces.

    Also I don't know if this stems from the faulty VLAN coverage but it seems like DHCP Relay isn't working on these interfaces either…. More testing to come on that

    EDIT: After Checking my DHCP logs it seems that the requests are not being passed on from pfsense. I am able to ping pfsense, the dhcp server and the internet from the PC on the respective interface, so it would appear that it is a problem with the relay. I haven't been able to find anything in the logs about it though.



  • FreeBSD 7 handles VLANs slightly differently, and this appears to have broken something. This has been confirmed as an issue in 1.2.1 and 1.3, fix will be coming soon.



  • Cool. I'm kinda new to pfsense, is there another place to look to try to find information on known issues?

    Also, with some more testing the DHCP relay works if I uncheck Append Circuit ID. I don't know why this matters, as I had it checked on my old 1.2 machine.



  • you can find the open bugs on 1.3 here.
    http://cvstrac.pfsense.org/rptview?rn=34

    the vast majority of those are rare edge cases. The VLAN issue will be resolved shortly, that's one that just popped up and doesn't have a ticket at the moment.



  • Grab another image after 1 hour or 2 should be fixed.

    Ermal



  • Downloaded pfSense-20080709-1959.iso.gz and am still getting the same issue.



  • Do you see on console any of "ifconfig vlanX does not exist" message?



  • Oh can you please give me the output of "ifconfig -l" too and a snippet from config.xml of the "vlans>" section.

    Ermal



  • ifconfig -l output :

    ifconfig -l

    le0 le1 le2 plip0 lo0 enc0 pflog0 pfsync0 vlan0 vlan1 vlan2 vlan3 vlan4 vlan5 vlan6 vlan7 vlan8 vlan9

    config.xml vlan section

     <vlans><vlan><if>le1</if>
    			<tag>103</tag></vlan> 
    		 <vlan><if>le1</if>
    			<tag>204</tag></vlan> 
    		 <vlan><if>le1</if>
    			<tag>205</tag></vlan> 
    		 <vlan><if>le1</if>
    			<tag>206</tag></vlan> 
    		 <vlan><if>le1</if>
    			<tag>207</tag></vlan> 
    		 <vlan><if>le2</if>
    			<tag>100</tag></vlan> 
    		 <vlan><if>le2</if>
    			<tag>102</tag></vlan> 
    		 <vlan><if>le2</if>
    			<tag>201</tag></vlan> 
    		 <vlan><if>le2</if>
    			<tag>202</tag></vlan> 
    		 <vlan><if>le2</if>
    			<tag>203</tag></vlan></vlans> 
    

    It isn't like the vlans aren't functioning. It would just seem to be an issue with how the web gui handles them. If you guys would like some help, I have some free time and would just need a bit of info about associated files



  • Seems like your config has not been upgraded by the upgrade code.
    I commited a fix for this please try a snapshot after 1/2 hours and report back.

    Beaware, that you need to use the old config from 1.2 or open up /etc/inc/globals.inc, after the upgrade to the new snapshot, and search in there for "latest_config" and give it a value less or equal to 4.4.

    You will know when your config gets converted since it the "vlans" sections should look like
    <vlan><if>le1</if>
    <tag>103</tag>
                          <vlanif>vlan0</vlanif></vlan>

    Surely, tell me how it goes.

    Ermal



  • Beaware, that you need to use the old config from 1.2 or open up /etc/inc/globals.inc, after the upgrade to the new snapshot, and search in there for "latest_config" and give it a value less or equal to 4.4.

    Sorry you have to edit your config.xml end change the version tag there to something less or equal to 4.4.
    Must have been somewhere  else with my head when i wrote this.

    Ermal



  • Sorry, I've been out of town all weekend, so I haven't had access to my pfsense box or to the boards. I will download the latest version over lunch and upgrade it. I will also try a fresh install.



  • The problem was solved when booting from CD, running a fresh install off the HD, and when upgrading from 1.2.


Log in to reply