LEAF/LRP Team;
Thanks for a great piece of work!
I have successfully implemented LEAF using Dachstein Linux version
2.2.19-3-LEAF. It took me about two days, I'm pretty new at Linux and did a
lot of reading of the FAQ, etc., before I actually dove in and built the
disk. I was able to get this configuration working due to your hard work
and the contributions of the many who have gone before me; undeniable proof
that open software and open forum support is the best.
Here's my configuration and some "bumps" I hit, just in case anybody else
tries to do this as well:
1 Cable Modem
(Through a well known and
deservedly well-maligned
provider - I tried to get
DSL, but I'm on the fringe
until they get off copper.)
|
|
|
V
LRP running on
Gateway Pentium 166
(Bought the machine back in
1997, and it just can't run
Windows 2000... I have redhat 7.2
installed on it as well, will keep it
that way and add multi-boot for LRP
in the future, to get off the
diskette limitation.)
64MB memory (yes, i tired to keep Windows running...)
NIC#1: eth0, ADMtek Comet rev 17
NIC#2: eth1, SMC1211TX EZCard 10/100 (RealTek RTL8139)
Drivers: tulip.c:v0.92m, 8139too FastEthernet driver 0.9.14-2.2
BUMP#1: original config of modules.lrp did not work for my hardware setup,
I found tulip and 8139too at
http://lrp.steinkuehler.net/files/kernels/Dachstein-normal/modules/net/,
SPECIAL
THANKS TO Charles Steinkuehler for his VERY USEFUL website!
Even these didn't work. Then while searching the knowledge base
(http://lrp.ramhb.co.nz/kb.htm)
until found a coment about the order of the modules... I
uncommented the pci-scan module ahead
of these other two, then, presto, both cards came up, but the PCI
order switched, so I swapped
the cables and bango! eth0 obtained a DHCP address.
Still had to reboot the Windows 2000 machine becasue i had some
left-over settings from when I was
using Connection Sharing.
A note here; I had modified the original LRP install to include
IFCONFIG/ROUTE, IPTRAF and HTTP_GET.
IFCONFIG was helpful to me in knowing when I got a good address on
eth0. Http_get was really helpful
for knowing that I was really getting through to the Internet. A
simple 'http_get http://www.yahoo.com'
got me feeling pretty good as I watched the lights blink on the
NIC!
Iptraf is just sort of cool to watch, especially when you're
listening to internet radio...
|
|
|
V
NetGear FS105 4-Port 10/100 Switch
(Has an uplink port as well for growth.)
|
|
|
V
My new Windows 2000 box (yes, 256MB memory and a fast pentium processor
make this work well enough, until
the MS folks pork it out some more...)
A DHCP client to the LRP machine.
I really like the Web interface to the firewall, I wish it could show the
active DHCP leases(?)
Couple of other things:
1.) EMAIL - once the system was up and running I couldn't get my email to
work, but knew it was the mail server name. So after I poked around the
provider's member services site and found the FQDN, presto, that worked as
well.
2.) Many of the emails in the knowledge base (http://lrp.ramhb.co.nz/kb.htm)
are somewhat old and if you're not careful, you could chase some wild geese.
I almost started adding the FQDN to my dhcpd.conf file as 'option
domain-name' until I realized that the Outlook account matenance dialog box
needed it in the 'Servers' tab in the 'Incoming mail (POP3):' and
'Outgoing mail (SMTP):' text boxes as 'mail.xxxxx.com'. Also, people tend
to complain about the configurations too much, rather than stick to the
technical layout and what their problem is/how to solve it; so you have to
wade through the comments.
That's it, sorry for the long-winded message. But i do really apprciate the
effort you folks have gone through to deliver a nice peice of software.
dave
"If parents pass enthusiasm along to their children, they will have left
them an estate of incalculable value."
Thomas Edison
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
