VLAN assigned to WAN results in Network interface mismatch



  • Hello,

    when I configure VLAN for my NIC and bind it to WAN in the initial setup it says the configuration is fine. But once I reboot, I get 'Network interface mismatch – Running interface assignment option.'

    I have VDSL and therefore need to assign WAN to VLAN ID 7 of my NIC. This worked fine in pfSense 1.2.x
    But I am having trouble in 2.0 embedded (I tried pfSense-2.0-ALPHA-ALPHA-20090611-1712.img.gz in particular) on my ALIX 2c3 board.

    Here's what it looks like in the console:

    
    Loading configuration......done.
    
    Network interface mismatch -- Running interface assignment option.
    
    Valid interfaces are:
    
    vr0     00:0d:b9:12:f3:60   (down)      VIA VT6105M Rhine III 10/100BaseTX
    vr1     00:0d:b9:12:f3:61   (down)      VIA VT6105M Rhine III 10/100BaseTX
    vr2     00:0d:b9:12:f3:62   (down)      VIA VT6105M Rhine III 10/100BaseTX
    ath0    00:0b:6b:84:aa:49   (down)      Atheros 5212
    
    Do you want to set up VLANs first?
    If you are not going to use VLANs, or only for optional interfaces, you should
    say no here and use the webConfigurator to configure VLANs later, if required.
    
    Do you want to set up VLANs now [y|n]?n
    
    VLAN interfaces:
    
    vlan7   VLAN tag 7, interface vr1
    
    *NOTE*  pfSense requires *AT LEAST* 1 assigned interfaces to function.
            If you do not have *AT LEAST* 1 interfaces you CANNOT continue.
    
            If you do not have at least 1 *REAL* network interface cards
            or one interface with multiple VLANs then pfSense
            *WILL NOT* function correctly.
    
    If you do not know the names of your interfaces, you may choose to use
    auto-detection. In that case, disconnect all interfaces now before
    hitting 'a' to initiate auto detection.
    
    Enter the WAN interface name or 'a' for auto-detection: vr1.vlan7
    
    Enter the LAN interface name or 'a' for auto-detection
    NOTE: this enables full Firewalling/NAT mode.
    (or nothing if finished): vr0
    
    Optional interface 1 description found: OPT1
    Enter the Optional 1 interface name or 'a' for auto-detection
    (or nothing if finished): vr2
    
    Optional interface 2 description found: OPT2
    Enter the Optional 2 interface name or 'a' for auto-detection
    (or nothing if finished): ath0
    
    Enter the Optional 3 interface name or 'a' for auto-detection
    (or nothing if finished):
    
    The interfaces will be assigned as follows:
    
    LAN  ->vr0
    WAN  ->vr1.vlan7
    OPT1 -> vr2
    OPT2 -> ath0
    
    Do you want to proceed [y|n]?y
    
    Writing configuration....done.
    done.
    
    Network interface mismatch -- Running interface assignment option.
    
    

    I have tried variations on the VLAN interface name, when assigning it to WAN. It won't take vlan0, vlan7 but only vr1.vlan7 (which in itself should be correct). But once rebooted I get the very same thing.

    What works is assigning the interfaces without a VLAN (but that does not help me, though):

    
    Enter the WAN interface name or 'a' for auto-detection: vr1
    
    Enter the LAN interface name or 'a' for auto-detection
    NOTE: this enables full Firewalling/NAT mode.
    (or nothing if finished): vr0
    
    Optional interface 1 description found: OPT1
    Enter the Optional 1 interface name or 'a' for auto-detection
    (or nothing if finished): vr2
    
    Optional interface 2 description found: OPT2
    Enter the Optional 2 interface name or 'a' for auto-detection
    (or nothing if finished): ath0
    
    Enter the Optional 3 interface name or 'a' for auto-detection
    (or nothing if finished):
    
    The interfaces will be assigned as follows:
    
    LAN  ->vr0
    WAN  ->vr1
    OPT1 -> vr2
    OPT2 -> ath0
    
    Do you want to proceed [y|n]?y
    

    Here it retains the settings (but this is unusable for my setup, since that cuts me off from the Internet).

    I also tried assigning it via web configuration at a later time. It correctly displayed the newly created and assigned VLAN (see this post's attachment). But upon reboot I get the exact same error…

    Thanks a lot in advance!



  • Try a new snapshot should be fixed.



  • @ermal:

    Try a new snapshot should be fixed.

    Which file should I download and try exactly (7.2-REL 2.0 only has 1712 which I tried, 8-CURRENT 2.0 says that all embedded images are broken  :().
    Can you give me an exact link? Thanks!





  • Hello ermal,

    thank you for the links. But frankly I have no idea how to integrate these code changes into one of the embedded images. I was hoping for a link to a working embedded image, that I can copy onto the CompactFlash disk directly. [Since the website sais "WARNING: Embedded images are broken", I assume that they all are… and that the only working image ist the 1712 I tried - correct me if I'm assuming wrong ;)]

    Or is there an easy way to make those two changes in a running pfSense 2.0 alpha-alpha built 1712 which is retained in the next boot? (I tried using vi on the two files, but when trying to write with w! I only get read-only filesystem)

    Thanks again for your help! I'd really like to get this working  :P



  • Before going into vi run /etc/rc.conf_mount_rw
    and after you finish with editing run /etc/rc.conf_mount_ro



  • @PWC:

    vlan7   VLAN tag 7, interface vr1

    Enter the WAN interface name or 'a' for auto-detection: vr1.vlan7

    Shouldn't it be vlan7 only without vr1. parent interface reference?

    –--
    Well, thanks Ermal, even I got it now "/* VLANs are name $parent.$vlan now */"



  • Hello ermal,

    I made the changes and the interface is now accepted (thanks for that).
    But I'm affraid I'm still out of luck with connecting to the Internet using VLAN7….

    Here's the error I get in system.log

    Jan  1 00:43:12 pfSense mpd: [pppoeclient] Cannot send a netgraph message: vr1.vlan7::Invalid argument
    Jan  1 00:43:12 pfSense mpd: [pppoeclient] PPPoE: Error creating ng_pppoe node on vr1.vlan7:
    Jan  1 00:43:12 pfSense mpd: [pppoeclient] PPPoE node for link is not initialized
    Jan  1 00:43:12 pfSense mpd: [pppoeclient] link: DOWN event
    Jan  1 00:43:12 pfSense mpd: [pppoeclient] link: reconnection attempt 30
    Jan  1 00:43:12 pfSense mpd: [pppoeclient] LCP: Down event
    Jan  1 00:43:12 pfSense mpd: [pppoeclient] pausing 5 seconds before open
    

    The complete system log directly after booting is this:

    Jan 1 00:28:35 	kernel: ehci0: [GIANT-LOCKED]
    Jan 1 00:28:35 	kernel: ehci0: [ITHREAD]
    Jan 1 00:28:35 	kernel: usb1: EHCI version 1.0
    Jan 1 00:28:35 	kernel: usb1: companion controller, 4 ports each: usb0
    Jan 1 00:28:35 	kernel: usb1: <amd cs5536="" (geode)="" usb="" 2.0="" controller=""> on ehci0
    Jan 1 00:28:35 	kernel: usb1: USB revision 2.0
    Jan 1 00:28:35 	kernel: uhub1: <amd 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usb1
    Jan 1 00:28:35 	kernel: uhub1: 4 ports with 4 removable, self powered
    Jan 1 00:28:35 	kernel: cpu0 on motherboard
    Jan 1 00:28:35 	kernel: orm0: <isa option="" rom=""> at iomem 0xe0000-0xea7ff pnpid ORM0000 on isa0
    Jan 1 00:28:35 	kernel: ppc0: parallel port not found.
    Jan 1 00:28:35 	kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x30 on isa0
    Jan 1 00:28:35 	kernel: sio0: type 16550A, console
    Jan 1 00:28:35 	kernel: sio0: [FILTER]
    Jan 1 00:28:35 	kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0
    Jan 1 00:28:35 	kernel: sio1: type 16550A
    Jan 1 00:28:35 	kernel: sio1: [FILTER]
    Jan 1 00:28:35 	kernel: Timecounter "TSC" frequency 498053327 Hz quality 800
    Jan 1 00:28:35 	kernel: Timecounters tick every 10.000 msec
    Jan 1 00:28:35 	kernel: IPsec: Initialized Security Association Processing.
    Jan 1 00:28:35 	kernel: ad0: FAILURE - SETFEATURES SET TRANSFER MODE status=51 <ready,dsc,error>error=4 <aborted>Jan 1 00:28:35 	kernel: ad0: 244MB <toshiba thncf256maa="" 1.1=""> at ata0-master BIOSPIO
    Jan 1 00:28:35 	kernel: Trying to mount root from ufs:/dev/ufs/pfSense
    Jan 1 00:28:35 	kernel: vr1: link state changed to UP
    Jan 1 00:28:35 	php: : The command '/sbin/ifconfig vr1.vlan7 destroy' returned exit code '1', the output was 'ifconfig: interface vr1.vlan7 does not exist'
    Jan 1 00:28:35 	kernel: vlan0: changing name to 'vr1.vlan7'
    Jan 1 00:28:36 	mpd: Multi-link PPP daemon for FreeBSD
    Jan 1 00:28:36 	mpd:
    Jan 1 00:28:36 	mpd: process 17425 started, version 4.4 (root@FreeBSD-7_2_RELENG_2_0-snapshots.pfsense.org 12:54 10-Jun-2009)
    Jan 1 00:29:06 	kernel: vr2: link state changed to DOWN
    Jan 1 00:29:07 	kernel: pflog0: promiscuous mode enabled
    Jan 1 00:29:14 	dnsmasq[48228]: started, version 2.45 cachesize 10000
    Jan 1 00:29:14 	dnsmasq[48228]: compile time options: IPv6 GNU-getopt BSD-bridge ISC-leasefile no-DBus no-I18N TFTP
    Jan 1 00:29:14 	dnsmasq[48228]: no servers found in /etc/resolv.conf, will retry
    Jan 1 00:29:14 	dnsmasq[48228]: no servers found in /etc/resolv.conf, will retry
    Jan 1 00:29:14 	dnsmasq[48228]: read /etc/hosts - 2 addresses
    Jan 1 00:29:15 	php: : The command '/sbin/kldunload ipfw.ko' returned exit code '1', the output was 'kldunload: can't find file ipfw.ko'
    Jan 1 00:29:17 	apinger: ALARM: wan(127.0.0.2) *** down ***. Loss 0.0%, Delay 0.000ms
    Jan 1 00:29:18 	php: : Creating rrd update script
    Jan 1 00:29:19 	dhcpd: Internet Systems Consortium DHCP Server V3.0.7
    Jan 1 00:29:19 	dhcpd: Copyright 2004-2008 Internet Systems Consortium.
    Jan 1 00:29:19 	dhcpd: All rights reserved.
    Jan 1 00:29:19 	dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
    Jan 1 00:29:20 	php: : Resyncing configuration for all packages.
    Jan 1 00:29:22 	check_reload_status: check_reload_status is starting
    Jan 1 00:29:22 	login: login on console as root
    Jan 1 00:29:22 	sshlockout[28433]: sshlockout starting up
    Jan 1 00:29:22 	sshlockout[28433]: sshlockout starting up
    Jan 1 00:29:28 	check_reload_status: reloading filter</toshiba></aborted></ready,dsc,error></isa></amd></amd>
    


  • Try this:
    https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/48315e65964500cb9f61c1cebef6f9b608b09d4d

    pppoe will not like those . in the name and i had forgot about that.


Log in to reply