Hardware

Got an old Nokia IP290 firewall appliance to boot with M0n0wall 1.8.0b499.
However, the network adapters em0 thru em5 are not properly recognized.

Is there a way to enable the Intel(R) PRO/1000 Network adapters for M0n0wall to use?

Here's the console logfile of a boot process:

FreeBSD/x86 bootstrap loader, Revision 1.1
(root@almeida.cse.buffalo.edu, Fri Feb 18 01:25:00 UTC 2011)
data=0xd6854+0xa4fe0
Copyright (c) 1992-2011 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.2-RELEASE-p6 #0: Tue Feb 21 18:05:19 CET 2012
    root@builder82.m0n0.ch:/usr/m0n0wall/build82/tmp/sys/i386/compile/M0N0WALL_GENERIC i386
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Celeron(R) M processor         1.50GHz (1499.25-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x6d8  Family = 6  Model = d  Stepping = 8
  Features=0xafe9fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE>
real memory  = 2145943552 (2046 MB)
avail memory = 2051993600 (1956 MB)
wlan: mac acl policy registered
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
pcib0: <Host to PCI bridge> pcibus 0 on motherboard
pci0: <PCI bus> on pcib0
pci0: <base peripheral> at device 1.0 (no driver attached)
pcib1: <PCI-PCI bridge> irq 11 at device 2.0 on pci0
pci1: <PCI bus> on pcib1
pcib2: <PCI-PCI bridge> irq 11 at device 4.0 on pci0
pci2: <PCI bus> on pcib2
em0: <Intel(R) PRO/1000 Network Connection 7.1.9> port 0x4020-0x403f mem 0x80200000-0x8021ffff,0x80220000-0x8023ffff irq 11 at device 0.0 on pci2
em0: No MSI/MSIX using a Legacy IRQ
em0: Invalid MAC address
device_attach: em0 attach returned 5
em1: <Intel(R) PRO/1000 Network Connection 7.1.9> port 0x4000-0x401f mem 0x80240000-0x8025ffff,0x80260000-0x8027ffff irq 11 at device 0.1 on pci2
em1: No MSI/MSIX using a Legacy IRQ
em1: Invalid MAC address
device_attach: em1 attach returned 5
pcib3: <PCI-PCI bridge> irq 11 at device 5.0 on pci0
pci3: <PCI bus> on pcib3
em2: <Intel(R) PRO/1000 Network Connection 7.1.9> port 0x3020-0x303f mem 0x80100000-0x8011ffff,0x80120000-0x8013ffff irq 11 at device 0.0 on pci3
em2: No MSI/MSIX using a Legacy IRQ
em2: Invalid MAC address
device_attach: em2 attach returned 5
em3: <Intel(R) PRO/1000 Network Connection 7.1.9> port 0x3000-0x301f mem 0x80140000-0x8015ffff,0x80160000-0x8017ffff irq 11 at device 0.1 on pci3
em3: No MSI/MSIX using a Legacy IRQ
em3: Invalid MAC address
device_attach: em3 attach returned 5
pcib4: <PCI-PCI bridge> irq 11 at device 6.0 on pci0
pci4: <PCI bus> on pcib4
em4: <Intel(R) PRO/1000 Network Connection 7.1.9> port 0x2020-0x203f mem 0x80000000-0x8001ffff,0x80020000-0x8003ffff irq 11 at device 0.0 on pci4
em4: No MSI/MSIX using a Legacy IRQ
em4: Invalid MAC address
device_attach: em4 attach returned 5
em5: <Intel(R) PRO/1000 Network Connection 7.1.9> port 0x2000-0x201f mem 0x80040000-0x8005ffff,0x80060000-0x8007ffff irq 11 at device 0.1 on pci4
em5: No MSI/MSIX using a Legacy IRQ
em5: Invalid MAC address
device_attach: em5 attach returned 5
pcib5: <PCI-PCI bridge> at device 28.0 on pci0
pci5: <PCI bus> on pcib5
uhci0: <UHCI (generic) USB controller> port 0x5040-0x505f irq 11 at device 29.0 on pci0
uhci0: [ITHREAD]
usbus0: <UHCI (generic) USB controller> on uhci0
uhci1: <UHCI (generic) USB controller> port 0x5020-0x503f irq 11 at device 29.1 on pci0
uhci1: [ITHREAD]
usbus1: <UHCI (generic) USB controller> on uhci1
pci0: <base peripheral> at device 29.4 (no driver attached)
ehci0: <Intel 6300ESB USB 2.0 controller> mem 0x80301400-0x803017ff irq 11 at device 29.7 on pci0
ehci0: [ITHREAD]
usbus2: waiting for BIOS to give up control
usbus2: timed out waiting for BIOS
usbus2: EHCI version 1.0
usbus2: <Intel 6300ESB USB 2.0 controller> on ehci0
pcib6: <PCI-PCI bridge> at device 30.0 on pci0
pci6: <PCI bus> on pcib6
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel 6300ESB UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x5070-0x507f mem 0x80301000-0x803013ff irq 11 at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
atapci1: <Intel 6300ESB SATA150 controller> port 0x5088-0x508f,0x50a4-0x50a7,0x5080-0x5087,0x50a0-0x50a3,0x5060-0x506f irq 11 at device 31.2 on pci0
atapci1: [ITHREAD]
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
cpu0 on motherboard
p4tcc0: <CPU Frequency Thermal Control> on cpu0
pmtimer0 on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
uart0: <Non-standard ns8250 class UART with FIFOs> at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
uart0: [FILTER]
uart0: console (9600,n,8,1)
uart1: <Non-standard ns8250 class UART with FIFOs> at port 0x2f8-0x2ff irq 3 on isa0
uart1: [FILTER]
atrtc0: <AT Real Time Clock> at port 0x70 irq 8 on isa0
Timecounter "TSC" frequency 1499248246 Hz quality 800
Timecounters tick every 1.000 msec
IPsec: Initialized Security Association Processing.
IP Filter: v4.1.34 initialized.  Default = block all, Logging = enabled
musbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
ugen0.1: <Intel> at usbus0
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
usbus2: 480Mbps High Speed USB v2.0
d0: Preloadugen2.1: <Intel> at usbus2
uhub2: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
ed image </mfsroot> 38707200 bytes at 0xc0d7b4d4
ad0: 122MB <STI Flash 8.0.0 01/17/07> at ata0-master PIO4
Root mount waiting for: usbus2 usbus1 usbus0
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
Root mount waiting for: usbus2
uhub2: 4 ports with 4 removable, self powered
Trying to mount root from ufs:/dev/md0
kern.coredump: 1 -> 0
net.enc.in.ipsec_filter_mask: 0x00000001 -> 0x00000002
Found configuration on ad0.


*******************************************************************************
* None of the assigned network interfaces could be found.                     *
* This usually happens when installing on a new system, or when moving an     *
* existing configuration to a different hardware. In that case, it does not   *
* indicate a problem.                                                         *
*                                                                             *
* The logical interfaces (LAN/WAN/OPT) will be reconfigured automatically     *
* using the available physical network interfaces. Please review the          *
* assignments and change them if necessary.                                   *
*******************************************************************************

ERROR: fewer than two network interfaces found. You need at least two interfaces (for LAN and WAN).

Initializing timezone... done
Configuring firewall... done
Configuring LAN interface... done
Configuring WAN interface... done
Starting syslog service... done
Starting webGUI... done
Starting DNS forwarder... done
Starting NTP client... done
Starting DHCP service... done


*** This is m0n0wall, version 1.8.0b499
    built on Tue Feb 21 17:55:04 CET 2012 for generic-pc-serial
    Copyright (C) 2002-2012 by Manuel Kasper. All rights reserved.
    Visit http://m0n0.ch/wall for updates.
   
   
    LAN IP address: 192.168.1.1
    WAN IP address: (unknown)
   
    Port configuration:
   
    LAN   -> sis0
    WAN   -> sis1


m0n0wall console setup
**********************
1) Interfaces: assign network ports
2) Set up LAN IP address
3) Reset webGUI password
4) Reset to factory defaults
5) Reboot system
6) Ping host

Enter a number: 1

Valid interfaces are:


Note that wireless LAN interfaces are not included in the list above;
they can be set up through the webGUI later on.

Do you want to set up VLANs first?
If you're not going to use VLANs, or only for optional interfaces, you
should say no here and use the webGUI to configure VLANs later, if required.

Do you want to set up VLANs now? (y/n) n

If you don't know the names of your interfaces, you may choose to use
auto-detection. In that case, disconnect all interfaces before you begin,
and reconnect each one when prompted to do so.

Enter the LAN interface name or 'a' for auto-detection: em0

Invalid interface name 'em0'

Enter the LAN interface name or 'a' for auto-detection: a

Connect the LAN interface now and make sure that the link is up.
Then press ENTER to continue.

No link-up detected.

Google: "m0n0wall Nokia IP" and read thru a few of the findings. The method to spoof MAC addresses may work with m0n0 1.8. If not, try with 1.33.

Good luck and let us know how it turns out.

This is exactly what I did...

The IP290 box has Gigabit Ethernet, all other older IP* boxes running with M0n0wall have 10/100 Megabit Ethernet.

The issue is different as there are no "ff:ff:ff:ff:ff:ff" interfaces.
The ethernet interfaces are recognized as devices but cannot be used.

FreeBSD 8.2 should be able to use Intel Gigabit ethernet according to the FreeBSD documentation:
http://www.freebsd.org/releases/8.2R/hardware.html#ETHERNET

Could it be that the Intel Gigabit driver is not linked into the current M0n0wall beta version?

The NICS are being recognized to the point that the em driver is being selected, so it has to be in the m0n0wall code. The problem is that there is no MAC address reported at all which is different. These Nokia IP290 boxes are old enough that is shouldn't be a matter of the hardware being too new for the software.

Are you saying you have manually edited config.xml to specify interfaces like this, but putting valid hex numbers in for xy?

<lan>
                       <if>em0</if>
                       <ipaddr>192.168.1.1</ipaddr>
                       <spoofmac>xy:xy:xy:xy:xy:xy</spoofmac>
                       <subnet>24</subnet>
</lan>


pfsense 2.0 is reported to work with Nokia IP290. You might try that, and if it works, have a look at its config.xml file for clues regarding interfaces and also the boot messages.

OK, I edited the config.xml file within the boot image to contain the desired <spoofmac> entries:

<lan>
<if>em0</if>
<ipaddr>192.168.1.1</ipaddr>
<spoofmac>2c:a3:52:9f:aa:01</spoofmac>
...
<wan>
<if>em1</if>
<ipaddr>dhcp</ipaddr>
<spoofmac>2c:a3:52:9f:aa:02</spoofmac>
...

The IP290 appliance now reports the proper interface names for LAN and WAN, but still refuses to use them.

The list of valid interfaces is empty as before:

*** This is m0n0wall, version 1.8.0b499
    built on Tue Feb 21 17:55:04 CET 2012 for generic-pc-serial
    Copyright (C) 2002-2012 by Manuel Kasper. All rights reserved.
    Visit http://m0n0.ch/wall for updates.
   
   
    LAN IP address: 192.168.1.1
    WAN IP address: (unknown)
   
    Port configuration:
   
    LAN   -> em0
    WAN   -> em1


m0n0wall console setup
**********************
1) Interfaces: assign network ports
2) Set up LAN IP address
3) Reset webGUI password
4) Reset to factory defaults
5) Reboot system
6) Ping host

Enter a number: 1

Valid interfaces are:


Note that wireless LAN interfaces are not included in the list above;
they can be set up through the webGUI later on.

Do you want to set up VLANs first?
If you're not going to use VLANs, or only for optional interfaces, you
should say no here and use the webGUI to configure VLANs later, if required.

Well, I'm fresh out of ideas.

But as someone who recently was also up against interface problems in 1.8, I was lucky enough to have both Manuel and brushedmoss notice my posts about it, and they were able to get it fixed and a new 1.8 version released.

I hope they see this thread too, and rise to the challenge :-)

If you haven't tried v1.33 yet, please do, and mention it if it works. That version always worked for me on the problematic hardware that failed with the new 1.8, and that fact aided tracking down the problem.

I tried with 1.33, but not with the <spoofmac>ed config yet. Same result as with 1.8.0b499 so far.
I just noticed that there is a new 1.8.0b500, but it does not mention driver changes.

Worth a try to see if editing config.xml will fix 1.33, and to try 1.80b500.

I mentioned that pfsense 2.0 is purported to work on Nokia IP 290. If so, that might be helpful.

Meanwhile, I tried both 1.33 and 1.8.0b500 with <spoofmac>ed config.xml files - with the same results as before.

I also tried to add some settings in <media> and <mediaopt>, e.g.

      <lan>
         <if>em0</if>
         <ipaddr>192.168.1.1</ipaddr>
         <spoofmac>2c:5f:a7:22:8b:01</spoofmac>
         <subnet>24</subnet>
         <media>autoselect</media>
         <mediaopt>full-duplex</mediaopt>
      </lan>

The Nokia IP290 interfaces em0 thru em5 still fail to communicate.

I found one single reference claiming pfsense running on a IP290 but not how it was achieved.

[omvanderwiele]

Hi Maga,

From my experience with lower end Nokia IPSO (110/120) based devices, I have never been able to get spoof Mac address to work correctly either, on any platform (not restricted to M0n0 / pfSense).

Usually Nokia Voyager, it assigns the MAC on boot for greater versatility, etc.

However, I have now encoded a valid MAC/PHY address on the eeprom for each network controller and works fine.  Many thanks to omvanderwiele for the great tutorial...

See http://forum.m0n0.ch/index.php?action=printpage;topic=1471.0 for details.  It takes about 2 hours for an IP110 from cracking the box open to completion, and allows me to run any FreeBSD routing variant I wish...  As a word of caution, I could only get the IP110 to boot DOS from a 2.5" laptop HD not a CF; maybe it was my old laptop misreading the CF and partitioning it badly?

Worth a try maybe; it would at least resolve the "BAD MAC" error you’re getting.

James.

Thank you James. I tried your suggestion and followed omvanderwiele's instructions but the network interfaces are still unavailable. The error reported in A.TXT and B.TXT is

Code:

Intel (R) PCI NIC EEPROM Utility  v4.3.19.0
Copyright (C) 1995 - 2003 Intel Corporation
Intel (R) Confidential and not for general distribution.


ERROR: No Intel based network adapters found in system.

Lacking an IDE to CF adapter, I used the procedure outlined in http://www.aetherwide.com/vignettes/20070530-1.html to create a DOS bootable CF card.

As both M0n0wall and pfSense are able to detect the Intel gigabit interfaces but are unable to use them, I suspect that there must be some special drivers or initialization commands which are used by the original IPSO software.

Last edit: April 27. 2012 : Working with Brushedmoss on a solution.

There is a "hacked" image of M0n0wall 1.8.0b510 which works on a Nokia IP-290 hardware platform now.
It contains a patched intel ethernet driver to prevent hardware checking and a spoofmac entry to get a proper mac address for the first interface.

As this involves a hacked driver file, we are not sure if this would still work on other intel platforms.
The developers will discuss the issue and decide if the workaround is integrated into the official beta.

Is anyone else interested in the working ip290 image? Please speak up.

Thanks for the offer.

I am waiting for an updated beta that resolves a remaining checksumming problem with the fxp driver. I am currently able to work around the problem by including an

<shellcmd>ifconfig fxp1 -rxcsum</shellcmd>

in the System section of config.xml

fxp1 is my WAN interface, and routing is disabled without the command.