PfSense 2.0.1 on Nokia IP530

sensepf

Hello,

I am trying to install pfSense on a Nokia IP530
http://forum.pfsense.org/index.php?topic=22579.msg119905

When I put the hard disk back in the Nokia, pfSense boots but then stays blocked with that message :
network interface mismatch - running interface assignment option

It doesn't go further : impossible to configure the interfaces manually.

Has anybody already successfully run pfsense 2.0.1 with this hardware ?

Regards

stephenw10

I'm not familiar with that hardware but reading the thread you linked to is this box serial console only? Are you using an appropriate image for serial console?

When you say

impossible to configure the interfaces manually.

are you given the option to select an interface?

Steve

sensepf

Yes it is serial console only, so I had to select embedded image during install.

I think I have the correct image because the boot seems to start well and I have no problem in selecting pfsense's boot options (default, acpi, verbose, …) by using the serial console.

The problem is that after seeing "network interface mismatch -running interface assignment option", I am not given the option to select an interface : the box seems to be frozen. So I am forced to use the power switch to restart (what leads me in the end to the same error message).

I just installed 1.2.3, with that version I don't have this problem. I get the option to select and assign the interfaces correctly. From there I can finish the basic network configuration and access the web config.

As I am blocked with version 2 for the moment, I am trying to configure 1.2.3 to see if all works well. I am thinking about trying an upgrade after having configured it completely (probably not the most elegant solution).

I'll add some logs (from boot to error message) tomorrow, if maybe you wish to have a look.

Regards

A Former User

I have the exact same issue, the way I have worked around it is by seeding the installation with pre-selected interfaces. The issue lies in the usage of the "dc0" interface, which in version 1.2.3 caused a lot of "interrupt storm detected" messages in the log files but still worked fine. Starting in version 2.0/2.0.1 it completely freezes the machine when to assign an interface to "dc0", any of the others work fine "dc1-3".

To assign the interfaces you have to do the following:
1. Boot from CD or USB stick with HD attached.
2. Get through the interface selection from the live boot.
3. Select "8. Shell" option
4. Mount the drive on /mnt (mount /dev/ad0s1a /mnt)
5. Edit /mnt/cf/config/config.xml
6. Find the sections "<wan>" and "<lan>" and modify the "<if>INTERFACE</if>" line with one of dc1,dc2 or dc3. On my boxes the NICs are (left to right) dc2, dc3, dc0, dc1.
7. Save the file.
8. Shutdown machine and put drive back in the IP 530.

Make sure you do not try to assign anything to dc0 using the web-interface since it will freeze up on you.

Let me know if you have any issues.

Robbert</lan></wan>

sensepf

I unassigned dc0 interface and upgraded to 2.0.1 : it works !
(The nics in my box appear in the same order as yours : dc2,dc3,dc0,dc1)

I then just had to disable "device polling" that I used with 1.2.3 to prevent interrupts messages and that made the cpu use reach 100% with 2.0.1.

I didn't test thoroughly but it seems to work well.

Thanks very much for the help.

rdcosta

hy guys…

after see this post i decided power on my ip530 again! ;) but the box still get stuck on "network interface mismatch -running interface assignment option" with green light of dc0 on!!!
first, the steps i'm using a 4Gb CF Card, and 2.0.1 RELEASE 4g i386 nanobsd imgage!

past image to cf card
in a VM load live cd pfsense...go to shell (8)
mount card /mnt
change assign interfaces to wan dc1 and lan dc2
save put card back to ip530 load system and "BANG!!" the machine freeze again on dc0..

Please, do you guys have another tips, or how to put this working... ?

Regards
R.C.

FlashPan

Hi Apologies in advance but am not sure if you are using a hard drive or a cf card or the option to use either?

What I did for a box with only a seriel connection and hard drive was:

Install hd into a laptop with vga, mouse, keyboard etc Installed the full x86 version and made no changes to nic assignments. After the installed completed and pf fully booted up, enter the webgui (via another laptop) and enable to serial console port. Shutdown pf. Move the drive back into the serial only box, boot up and watch the startup process as normal via a console session. Now at this point I cannot remember if pf detected the new/different nics and prompted to install/assign automatically or if I had to assign the nics via the menu.

Hope this helps in someway?

Cheers

rdcosta

Hi FlashPan,

i have my ip530 running with cf card only with 1.2.3 image for embedded machines.

with 2.0.1 i try use same way, copy image to cf card and try aswell in normal pc install to cf card with a normal instalation (option 99 :-\ ??)

both fail on boot when try to detect the nic's cards, light on dc0 get green and freeze!
when i saw this topic i decide give a try, edit config file to jump dc0 and set dc1/2 or 3 insted but with no result.

thanks.
R.C

provels

See my post on the ip530. http://forum.pfsense.org/index.php/topic,22579.0.html
Try enabling device polling in a slave machine before you put the CF into into the Nokia. HTH.

EDIT: Ignore me. Tried 2.0.1 on my 530, fails same way. Looks like another uphill battle with the 530.

A Former User

I have successfully installed 2.0 and 2.0.1 on three IP530's using the procedures I described above. The procedures do not specifically state this, but make sure your using another machine for the procedures below, and make sure you are updating the config file on the attached HD, not the RAM disk, and make sure you re-assign both the LAN and the WAN interfaces otherwise you will get the prompt when you boot.

@rrijkse:

To assign the interfaces you have to do the following:
1. Boot from CD or USB stick with HD attached.
2. Get through the interface selection from the live boot.
3. Select "8. Shell" option
4. Mount the drive on /mnt (mount /dev/ad0s1a /mnt)
5. Edit /mnt/cf/config/config.xml
6. Find the sections "<wan>" and "<lan>" and modify the "<if>INTERFACE</if>" line with one of dc1,dc2 or dc3. On my boxes the NICs are (left to right) dc2, dc3, dc0, dc1.
7. Save the file.
8. Shutdown machine and put drive back in the IP 530.

Make sure you do not try to assign anything to dc0 using the web-interface since it will freeze up on you.</lan></wan>