[ previous ] [ next ] [ threads ]
 From:  "Stephen Erisman" <StephenE at Ameripay dot com>
 To:  <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  m0n0wall on a Celestrix Aries Server - kernel config change needed?
 Date:  Mon, 4 Oct 2004 16:42:53 -0500


First off, I have to say I am really impressed with m0n0wall.  I have
been running it as a router/firewall between my cable modem and home
computers for about 3-4 months now, and it has handled all my needs much
more stably than the Belkin routers I had used previous.  Great Job on
the distribution!


I recently purchased a Celestrix Aries Server with the intent of running
m0n0wall on it.  (The size and functionality seemed to suite my needs

(For more info, here is the same hardware currently for sale on eBay:

It is a 300mhz Geode (pc/104) based computer with 128mb ram, 5gb
notebook hard drive, dual ethernet and pcmcia (among other normal i/o

It has a RealTek 8139 as it's primary Ethernet controller (LAN), and a
RealTek 8019 as it's secondary Ethernet controller (WAN - for cable


The RealTek 8139 is easily supported by m0n0wall, and recognizes

The RealTek 8019 is supposed to be supported by m0n0wall/FreeBSD as well
(it is a NE2000 compliant controller), but I could not get it to

The RealTek 8019 is supported by the ed driver:

You can see the support for it in the source code
(/src/sys/dev/ed/ed_isa.c) for FreeBSD release 4.10:


I found some information about a DOS based utility (RSET8019.EXE) that
is used to switch the controller between plug-n-play mode, and
jumperless mode (with i/o port and irq selections)

I changed the controller to jumperless mode with i/o of 0x280 and irq of
10 which makes it 100% compatible with ISA NE2000 (ISA is the only
option for pc/104 embedded computers as PC/104 is an ISA bus)

Even after this change, the controller still was not recognized by


I traced down the issue to the following line in the MONOWALL_GENERIC
kernel configuration file:

device               ed0       at isa? disable port 0x280 irq 10 iomem

To enable this device, this would need to be changed to the following
(took out the 'disable' option):

device               ed0       at isa? port 0x280 irq 10 iomem 0xd8000


I made the above change to the kernel config file, rebuilt the kernel,
reflashed the image to the machine, and now both ethernet controllers
are recognized and seem to work.


My questions are the following:

1.	Does anyone know why the device has been disabled in the kernel
config file? 
2.	Has anyone else run across this with a different solution? 
3.	I would really appreciate it if this configuration option was
changed in the generic-pc.img.  Is this a possibility? 



            Stephen E.