I'm having a problem I think is related to ethernet card configuration. My LEAF distribution is Bering_1.0-rc3 configured per chapter 4 of the users guide for PPPoE.
Output of "uname -a" is: Linux firewall 2.4.18 #4 Sun Jun 9 09:46:15 CEST 2002 i586 unknown My 2 ethernet cards are both D-Link DFE-530TX+, which are PCI cards. Relevant lines in /etc/modules are: # /etc/modules: kernel modules to load at boot time. # # This file should contain the names of kernel modules that are # to be loaded at boot time, one per line. Comments begin with # a `#', and everything on the line after them are ignored. # # All modules should reside in /lib/modules, and you are required # to list what you need *in the correct order*. Modprobe is not # used and there is no dependacy checking. # How they are loaded: insmod /lib/module/"$module".o $args ###################################################################### # More modules available from: # http://leaf.sourceforge.net/devel/jnilo/bering/latest/modules/ ###################################################################### # My ethernet cards # needed by PCI modules pci-scan # D-Link card rtl8139 # Linksys card #tulip # Modules needed for PPP/PPPOE connection slhc n_hdlc ppp_generic ppp_synctty pppox pppoe # Masquerading 'helper' modules # Other modules available in bering/modules/net/ipv4/netfilter ip_conntrack_ftp ip_conntrack_irc ip_nat_ftp ip_nat_irc Shortly after boot, the following message is displayed: eth0: Transmit timeout, status 0c 0005 media 00. The ppp interface is not established. Output of "ip addr show" is: 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo 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,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:50:ba:cc:67:58 brd ff:ff:ff:ff:ff:ff 4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:50:ba:42:c7:b0 brd ff:ff:ff:ff:ff:ff inet 192.168.1.254/24 brd 192.168.1.255 scope global eth1 Output of "ip route show" is: 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.254 Output of "lsmod" is: Module Pages Used by ip_nat_irc 2384 0 (unused) ip_nat_ftp 2960 0 (unused) ip_conntrack_irc 3056 1 ip_conntrack_ftp 3824 1 pppoe 6636 1 pppox 912 1 [pppoe] ppp_synctty 4376 0 (unused) ppp_generic 14920 1 [pppoe pppox ppp_synctty] n_hdlc 5760 0 (unused) slhc 4264 0 [ppp_generic] rtl8139 11720 2 pci-scan 3048 1 [rtl8139] Pings between the firewall machine and another machine on the LAN are successful in both directions. Ping from the firewall machine to the Internet fails - returns nothing. The D-Link ethernet cards are PnP. The BIOS defaulted both cards to the same IRQ. I changed 1 of the cards to a different IRQ, but the behavior described above did not change. Installing only 1 ethernet card at a time allowed the PPP interface to be established. Output of "ip addr show" is: 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo 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,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:50:ba:cc:67:58 brd ff:ff:ff:ff:ff:ff 4: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1492 qdisc pfifo_fast qlen 3 link/ppp inet 199.174.15.61 peer 199.174.15.1/32 scope global ppp0 Output of "ip route show" is: 199.174.15.1 dev ppp0 proto kernel scope link src 199.174.15.61 default via 199.174.15.1 dev ppp0 Output of "lsmod" is: Module Pages Used by ip_nat_irc 2384 0 (unused) ip_nat_ftp 2960 0 (unused) ip_conntrack_irc 3056 1 ip_conntrack_ftp 3824 1 pppoe 6636 1 pppox 912 1 [pppoe] ppp_synctty 4376 0 (unused) ppp_generic 14920 3 [pppoe pppox ppp_synctty] n_hdlc 5760 0 (unused) slhc 4264 0 [ppp_generic] rtl8139 11720 1 pci-scan 3048 1 [rtl8139] I tried one of the D-Link boards with a Linksys board. In that configuration I could force which board was eth0 and eth1 by the order in which modules were listed in /etc/modules. I could get either the LAN or the WAN to work (meaning successful pings), but not both at the same time. Any assistance is appreciated. DPD ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
