401'd on assign interfaces after restore

dotdash

Doing some testing, and I imported a 1.2 config into 2.0. The config was for a machine with different interfaces, so it tried to go to the re-assign interface page. Instead, I got a 401 Unauthorized.
Using embedded pfSense-2.0-ALPHA-ALPHA-20081121-1118.img

Rebooting from the console resulted in assign interfaces coming up on the console.

sullrich

Not sure I am following this report. Which page showed a 401 error?

dotdash

I restored the config, and the interfaces were different. Usually this redirects to a screen which lets you re-assign the interfaces before it reboots. The re-assign interfaces page resulted in the 401. I'll do it again and get the exact url in a min.
EDIT: /interfaces_assign.php

sullrich

Just tested this here with Firefox 3 and it works fine. Please give specific instructions on how to replicate the issue. Different browser?

dotdash

Here is what I did:
Test lab, PC is a crusty laptop running PCBSD 1.5.1, Firefox 2.0.0.14
Saved the config from a machine running a full-install of 1.2. Interfaces were em0,em1,fxp for LAN,WAN,OPT1
Loaded a new CF card with the 2.0alpha snap and put in an Alix 2c3. Assigned the interfaces via console cable (vr0, vr1, vr2 L/W/O). Opened a browser, logged in, restored the old config. Did the exact thing on 1.2.1RC2 earlier. On 1.2.1RC2, I press the button to restore and the browser redirects to the assign interfaces page, I pick vr0,1,2 for my interfaces and save. Then the firewall reboots. On the 2.0 snap, the config is restored but I get the 401 when it tries to redirect so I can fix the mismatched interfaces. If I reboot, it comes up on the new config, but the interfaces are still em0, em1, fxp0. I get the interface mismatch on the console, re-assign and everything is fine.

dotdash

Tested with an XP box and Firefox 2, getting the same behavior. I'll load FF3 and do some more tests.

sullrich

I think its firefox 2 related. Also please test with the latest snapshot.

dotdash

I tested it with FF 3.0.4 and IE6 on XP. Same 401. Perhaps something due to the page redirect happening after the config has been restored? I'll grab the new snapshot and see what happens.

sullrich

I believe it was due to a bug I fixed. Hopefully latest snap doesn't cause it any more.

dotdash

Finally got around to checking this again. This time I tried a full install using pfSense-2.0-ALPHA-ALPHA-20081205-0927.iso. Workstation is XP, FF3.0.4. Saved the config, edited config to change em0 to rl0 and restored (to trigger an interface mismatch). This time I got:
http://192.168.1.1/interfaces_assign.php
201
No page assigned to this user! Click here to logout.

nocer

Hi,

It doesn't happen to me on 01:45:00 EST 2008 build. I have moved several configs back and forth, never seen the situation you mentioned. All I played as admin with FF2/3, IE6/7/8, Opera 9.xx, Safari, Chrome, pretty much the browsers around.

cheers,

dotdash

@nocer:

Hi,

It doesn't happen to me on 01:45:00 EST 2008 build. I have moved several configs back and forth, never seen the situation you mentioned. All I played as admin with FF2/3, IE6/7/8, Opera 9.xx, Safari, Chrome, pretty much the browsers around.

cheers,

What date was your tested snap? Iso or img? Just to clarify, you restored a config with interfaces that were not physically present and successfully got to the interface re-assignment page before reboot?
I'll grab the newest img and try it on an Alix again.

dotdash

I'm doing some more testing, but this seems to only happen when restoring a 1.2 config (with mis-matched interfaces) to 2.0AA.

nocer

Hello,

What date was your tested snap? Iso or img? Just to clarify, you restored a config with interfaces that were not physically present and successfully got to the interface re-assignment page before reboot?
I'll grab the newest img and try it on an Alix again.

I was running Full-20081209-0145.tgz, so that the situation a little bit different from yours. Yes, I moved around among the 3 machines with config/build/interfaces are all different and never stuck at 401/201.

cheers,

nocer

Hello,

@dotdash:

I'm doing some more testing, but this seems to only happen when restoring a 1.2 config (with mis-matched interfaces) to 2.0AA.

Oh, yes, I noticed that several times. Restoring 1.2 config to 2.0-AA triggers automatic config translation/upgrade(?) while booting but it sometimes forget something and I had to start again from the scratch, moving 2.0-AA around is okay though. Never mind, it's still -AA.

cheers,