Author Topic: LEAF/Bering router using Shorewall, anyone?  (Read 1519 times)

Space Between

  • Guest
LEAF/Bering router using Shorewall, anyone?
« on: August 25, 2003, 05:50:52 PM »
First here's my situation trying to get a linux based router on a 133mhz, 32mb ram, and 90mb hdd.
These spec's are more than enough for a 10/100 router...soooo....

Anybody have any experience in this monster called LEAF.

Iver read the doc's, like 4 times, i got it actually installed, but my DHCP is just
not working. Im using the Shorewall firewall it comes with, i *think* that is
setup right...atleast according to the provided help.  Although i cant be for
sure.

If anybody has a hint or 2 please let me know.

Or does anybody have a linux router they have setup that is small, like a floppy size?
That's what im looking for, not neccesarily LEAF.  I would like to use LEAF but it
does require some sort of previous knowledge of itself that i just dont have. I can
follow the standard linux modifications, but some of others are pretty indepth i guess
you could say.

Guest

  • Guest
LEAF/Bering router using Shorewall, anyone?
« Reply #1 on: September 08, 2003, 12:19:46 PM »
[quote name=\'Space Between\' date=\'Aug 25 2003, 04:50 PM\']First here's my situation trying to get a linux based router on a 133mhz, 32mb ram, and 90mb hdd.
These spec's are more than enough for a 10/100 router...soooo....

Anybody have any experience in this monster called LEAF.

Iver read the doc's, like 4 times, i got it actually installed, but my DHCP is just
not working. Im using the Shorewall firewall it comes with, i *think* that is
setup right...atleast according to the provided help.  Although i cant be for
sure.

If anybody has a hint or 2 please let me know.

Or does anybody have a linux router they have setup that is small, like a floppy size?
That's what im looking for, not neccesarily LEAF.  I would like to use LEAF but it
does require some sort of previous knowledge of itself that i just dont have. I can
follow the standard linux modifications, but some of others are pretty indepth i guess
you could say.[/quote]
 hi, i've been using leaf/bering for more than a year, it's very good!! you can' mail me your questions at [email protected]
hopefully i can help you http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/tongue.gif\' class=\'bbc_emoticon\' alt=\':P\' />

Regards /Fredrik

Space Between

  • Guest
LEAF/Bering router using Shorewall, anyone?
« Reply #2 on: September 12, 2003, 03:13:23 AM »
Well i emailed you, dunnot if you got it yet or not. Anyways i'll post my issue here too.

First, the hardware all works. Im running Coyote Linux with the same hardware i have tried LEAF with.

Coyote linux detects both my nics. Im using realteck 8139 modules and their dependencies are mii.o and 8139too.o C module's (or i guess they are C). At first Coyote only detected my LAN 192.168....  and not my isp via pump.  Now i dont think pump is working correctly...but it could be.  After switching around the nics in the pci slots i finally got Coyote to see both nic's, from there it's down hill.

Now in LEAF i cannot get it to see my inet eth at all.  Ive switched around the nic's over a dozen times, no luck. Only thing i can think of is that since im using 2 of the same nic, maybe i need to load the .o's 2 times??? although i think if they load they load and that should be it. They are exactly the same nic, they work in Coyote now though ;-?.

Anyways, ive read the doc' on Bering and shorewall like 10 times or more. Ive even compiled my own kernel in the manner the dev doc for it says. No love, none.

Basically, i understand how to do all i want software wise with LEAF/Bering/Shorewall but i cant even get the damn nic to be seen.

In Coyote linux, the installer use's a GUI. I had to select at a certain screen what drivers i will be using for which cards.  The screen has a top and bottom field representing your eth0 and eth1, both fields are identical. I just selected the same driver for each card and moved on...sure enough Coyote worked after toggling the nic's around.

Im going to try another nic, however i havent found a module for it just yet. I wish i could just use these realtek cards though...i know they work since they work with Coyotoe.    The other nic i got is pricey, like 25usd :-).  Considering the pc i got running this router was 10usd(floppy included), and the 2 nic's combined where 9usd total...this other nic i want to use will cost more than my current setup.

I dunno, im stumped. Now nothing works in LEAF, i cant even ping the other pc's with the workind LAN nic. I know it see's that, because if i remove a NIC it doesnt assign any ip at all...everything is 0.0.0.0/0

Right now on boot it says something similar to this...

Masquerading...
TO: 0.0.0.0/0  FROM: 192.168.1....

So it's trying to masq. but there is no isp assigned to eth0 at all...again, maybe i need a 2nd duplicate driver?.

What do you got your Gateways set too for your LAN?

Space Between

  • Guest
LEAF/Bering router using Shorewall, anyone?
« Reply #3 on: September 12, 2003, 03:40:51 AM »
Ok just clearing up, Coyote only use's 1 driver for my card. So all that is needed it mii.o and 8139too.o for this to work. Dunno why i thought i might need 2 of the same exact driver...naive of me.

LEAF still not working :-/

Leaf Erikson

  • Guest
LEAF/Bering router using Shorewall, anyone?
« Reply #4 on: November 20, 2003, 01:28:14 PM »
I am a LEAF convert from Coyote.  I finally got around to getting my LEAF box with 1 ISA NIC and 3 PCI RealTek 8139 PCI NICs configured.  I actually have all four interfaces up and running.  The tricky part was to figure out how to get the PCI cards seen; I finally found buried deep in the LEAF docs what was needed:

You have to load the pci-scan.o module before the 8319xx.o module.

The nasty thing about configuring LEAF is that modprobe is NOT used, so YOU get to manage all of the module dependencies manually.  Coyote on the other hand DOES use modprobe, so it will auto-detect and load NIC drivers.  However, once LEAF is up and running, I find it MUCH more flexible and capable than Coyote.  But ya gotta know what you're doing a whole lot more.

BTW, for my 8139 cards ($4 apiece !), I only had to download pci-scan.o and rtl8139.o from the LEAF website;  I didn't need 8139too.o or 8139cp.o, and I apparently don't even need mii.o.  I'm not sure what all of the various combinations of 8139-related modules are, but all I had to use was the two I downloaded.

Now in all fairness, I should state that I just barely got this working -- I can ping machines on all four networks, but I haven't tried anything else yet.  If I run into trouble, I'll complain about it here.

Let me know if this helps...