401'd on assign interfaces after restore
-
Tested with an XP box and Firefox 2, getting the same behavior. I'll load FF3 and do some more tests.
-
I think its firefox 2 related. Also please test with the latest snapshot.
-
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.
-
I believe it was due to a bug I fixed. Hopefully latest snap doesn't cause it any more.
-
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. -
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,
-
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. -
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.
-
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,
-
Hello,
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,
