Network interface mismatch on ALIX
-
As subject, I'm unable to use latest embedded snapshots on ALIX.
I'm unable to test also the the special build based on FreeBSD 6.3.Look also at the mailing list:
http://www.mail-archive.com/support@pfsense.com/msg13607.htmlTo troubleshoot I've saved system messages during booting,compared them and these are the interesting difference:
pfSense 1.2rc4 (it is old but working well)
vr0: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1000-0x10ff mem 0xe0000000-0xe00000ff irq 10 at device 9.0 on pci0 vr0: Ethernet address: 00:0d:b9:13:4a:6c vr1: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1400-0x14ff mem 0xe0040000-0xe00400ff irq 11 at device 10.0 on pci0 vr1: Ethernet address: 00:0d:b9:13:4a:6d vr2: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1800-0x18ff mem 0xe0080000-0xe00800ff irq 12 at device 11.0 on pci0 vr2: Ethernet address: 00:0d:b9:13:4a:6e</via></via></via>pfSense 1.2.1 (faulty)
vr0: <via 10="" vt6105m="" rhine="" iii="" 100basetx=""> port 0x1000-0x10ff mem 0xe0000000-0xe00000ff irq 10 at device 9.0 on pci0 vr0: Quirks: 0x2 vr0: using obsoleted if_watchdog interface vr0: Ethernet address: 00:0d:b9:13:4a:6c vr0: [ITHREAD] vr1: <via 10="" vt6105m="" rhine="" iii="" 100basetx=""> port 0x1400-0x14ff mem 0xe0040000-0xe00400ff irq 11 at device 10.0 on pci0 vr1: Quirks: 0x2 vr1: using obsoleted if_watchdog interface vr1: Ethernet address: 00:0d:b9:13:4a:6d vr1: [ITHREAD] vr2: <via 10="" vt6105m="" rhine="" iii="" 100basetx=""> port 0x1800-0x18ff mem 0xe0080000-0xe00800ff irq 12 at device 11.0 on pci0 vr2: Quirks: 0x2 vr2: using obsoleted if_watchdog interface vr2: Ethernet address: 00:0d:b9:13:4a:6e vr2: [ITHREAD]</via></via></via>I'm unsure if it is my fault or somebody experiences the same issue. An investigation is needed ::)
-
I see the same messages on 1.3 AA builds on an Alix2c3. I think it is just due to FreeBSD 7 telling you the driver needs updating. It still seems to work fine. I'm sure other drivers are showing warnings also.
-
I didn't try the 1.3 ALPHA, but with all latest embedded snapshots I'm unable to start pfSense. It enters in this 'question-loop':
Creating symlinks......done. Launching PHP init system... done. Initializing.................. done. Starting device manager (devd)...done. Loading configuration......done. Network interface mismatch -- Running interface assignment option. Valid interfaces are: vr0 XX:XX:XX:XX:XX:XX vr1 XX:XX:XX:XX:XX:XX vr2 XX:XX:XX:XX:XX:XX ath0 XX:XX:XX:XX:XX:XX 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]?I answer no by pressing 'n' and I hit enter, but it always asks the same
question. I'm forced to switch off power and reflash the old CF's content.I don't understand what happens, because I followed the same steps when I flashed pfSense 1.2rc4.
I'd like to understand what "Network interface mismatch – Running interface assignment option." exactly means. ???
The CF's content haven't got any previous configuration because it got re-flashed with new binary .img file.Are you using the embedded platform or you use a Microdrive with a Full install?
Have you also tried embedded 1.2.1 testing snapshots?I'm worried about the future of my Alix2c3...
Thank you!
-
The embedded images aren't configured for vr interfaces by default, so assigning the interfaces is a necessary step. The 1.2 release images also do this- I actually never tried rc4 on an Alix.
What happens if you assign the interfaces, say vr0 for LAN, vr1 WAN, vr2 OPT1, ath0 OPT2? -
It doesn't allow me to assign interfaces as it should be.
To do that is necessary to answer no to this question:Do you want to set up VLANs now [y|n]?…but then it asks the same question forever denying me to step over and use a newer version of pfSense on my Alix2c3.
That's why I'm curious to know what causes this 'loop'.Hence are you using 1.3AA for everyday use? Did you use 1.2 release before?
Regards
-
Strange. Are you are saying that it shows you the list of interfaces, and when you say no to setting up VLANs it loops instead of asking which interface you want to assign to WAN? Or are you trying to use VLANs and the VLAN setup is looping?
I have a dozen or so Alix's with 1.2 release in the field. I have a test Alix with 1.3AA on my desk-NOT in production. -
Are you are saying that it shows you the list of interfaces, and when you say no to setting up VLANs it loops instead of asking which interface you want to assign to WAN?
Yes. It is strange, but it happens :-\
Or are you trying to use VLANs and the VLAN setup is looping?
By answering no, it shouldn't try to use VLANs. Theoretically.
I read about VLAN problems in "KnownIssues121" , but I don't use VLAN and my problem should be unrelated to this.I have a dozen or so Alix's with 1.2 release in the field. I have a test Alix with 1.3AA on my desk-NOT in production.
Now my Alix2c3 came back to use pfSense-1.2rc4 and it is working well again. I don't understand why this happens and I'd like to hear opinions from pfSense developers, too.
-
Hmm. I'll grab the latest snap of 1.2.1, try it in my test 2c3 and see what happens.
-
Don't know what to tell you, but it works for me. Here's what I did:
- grabbed pfSense-20080711-0208.img.gz from the snapshot server
- Un-zipped it to pfSense-20080711-0208.img
- Used physdiskwrite to write the image to a 1GB cf card. (how big is your card- old images would fit on a 128, newer images need 256+)
- Put the card in my Alix and booted.
Welcome to pfSense 1.2.1-TESTING-SNAPSHOT on the 'embedded' platform…
Setting up embedded specific environment... done.
Mounting filesystems... done.
Creating symlinks......done.
Launching PHP init system... done.
Initializing.................. done.
Starting device manager (devd)...done.
Loading configuration......done.Network interface mismatch -- Running interface assignment option.
Valid interfaces are:
vr0 00:0d:b9:12:e6:bc
vr1 00:0d:b9:12:e6:bd
vr2 00:0d:b9:12:e6:be
ath0 00:11:f5:8f:3d:97Do 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
NOTE pfSense requires AT LEAST 2 assigned interfaces to function.
If you do not have two interfaces you CANNOT continue.If you do not have at least two 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 LAN interface name or 'a' for auto-detection: vr0
Enter the WAN interface name or 'a' for auto-detection: vr1
Enter the Optional 1 interface name or 'a' for auto-detection
(or nothing if finished): vr2Enter the Optional 2 interface name or 'a' for auto-detection
(or nothing if finished): ath0Enter 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 -> ath0Do you want to proceed [y|n]?y
Updating configuration…done.
-
Thank you for having tested a newer snapshot on your ALIX.
Tomorrow I'll try to reflash my CF with a newer .img, I hope it will work, because it is really strange.
Regards
-
It doesn't allow me to assign interfaces as it should be.
To do that is necessary to answer no to this question:Do you want to set up VLANs now [y|n]?…but then it asks the same question forever denying me to step over and use a newer version of pfSense on my Alix2c3.
I loaded 1.2.1 on my ALIX and it works fine. Anything you enter there other than "y" will skip VLAN assignment and move to interface assignment. No clue how you could have ended up with anything different, that code hasn't changed at all since 1.2 release.
