Brad
Brad Klinghagen wrote:
> I've attached system messages, log files, configuration data, and error
> messages. Let me know if you need more.
I looked first at your lsmod output
Module Size Used by Not tainted
usbcore 51820 0
ext2 29728 0 (unused)
wd1100 2300 0 (unused)
ipt_ipp2p 5908 0 (unused)
ipt_state 272 0 (unused)
ipt_helper 400 0 (unused)
ipt_conntrack 692 0 (unused)
ipt_REDIRECT 480 0 (unused)
ipt_MASQUERADE 1024 0 (unused)
ip_nat_irc 1704 0 (unused)
ip_nat_ftp 2152 0 (unused)
iptable_nat 14388 2 [ipt_REDIRECT ipt_MASQUERADE ip_nat_irc
ip_nat_ftp]
ip_conntrack_irc 2484 1
ip_conntrack_ftp 3132 1
ip_conntrack 16548 2 [ipt_state ipt_helper ipt_conntrack
ipt_REDIRECT ipt_MASQUERADE ip_nat_irc ip_nat_ftp iptable_nat
ip_conntrack_irc ip_conntrack_ftp]
8139too 11944 0
mii 1820 0 [8139too]
crc32 2620 0 [8139too]
vfat 8492 2
isofs 15732 0 (unused)
ide-detect 132 0 (unused)
ide-cd 26748 0
ide-disk 11372 3
ide-core 88280 3 [ide-detect ide-cd ide-disk]
cdrom 25568 0 [ide-cd]
Unless you are running on a WRAP or anything similat to it, you don't
need the wd1100 driver but either a watchdog specific for this
board/chipset or softdog.
>
> As I looked over the files, it seems the 8139too.o module is allowing the
> NICs to work at some level; each NIC has the MAC address assigned, IRQ
> interrupts. When I execute 'ip addr' the system indicates each of the
> interfaces are up. When I try to ping eth1 on the firewall from the firewall
> I get the enclosed message in pingResults.
1: lo: <LOOPBACK> mtu 16436 qdisc noop
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:02:b6:35:d7:a9 brd ff:ff:ff:ff:ff:ff
4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:02:b6:35:d7:a8 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.1/24 brd 10.0.0.255 scope global eth1
5: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:02:b6:35:d7:a7 brd ff:ff:ff:ff:ff:ff
inet 10.0.2.1/24 brd 10.0.2.255 scope global eth2
This shows eth0 down probably because dhcp failed. The other ethernet
adapters appear to be up.
8139too Fast Ethernet driver 0.9.26
eth0: RealTek RTL8139 at 0xd0046000, 00:02:b6:35:d7:a9, IRQ 5
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
eth1: RealTek RTL8139 at 0xd0048000, 00:02:b6:35:d7:a8, IRQ 10
eth1: Identified 8139 chip type 'RTL-8100B/8139D'
eth2: RealTek RTL8139 at 0xd004a000, 00:02:b6:35:d7:a7, IRQ 11
eth2: Identified 8139 chip type 'RTL-8100B/8139D'
The driver appears to find the interfaces.
but, as mentioned before....
wd1100.c: unknown model value 1, trying anyway
wd1100.c: Can not find bridge device.
please get rid of the wd1100 stuff, it is _not_ a SC1100
>
> I also tried restarting one of my desktop computers, which gets it's IP
> address from the firewall via dnsmasq. The desktop never received an IP
> address from the firewall.
No surprise, you cannot even access your own interfaces as the
pingresults show.
In the config files I could not see any obvious problem
The only thing I could see is
Linux version 2.4.31 ([EMAIL PROTECTED]) (gcc version 3.3.3) #1 Thu Aug 18
21:03:20 CEST 2005
This is not the current bering-uClibc kernel. Is it possible that you
mixed kernels and modules?
cheers
Erich
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
