RE: [leaf-user] Stumped trying to get Bering uClibc 2.2.0b4 inter faces to light up
-Original Message- From: John Desmond [mailto:[EMAIL PROTECTED] Sent: Thursday, July 08, 2004 1:28 AM To: Luis.F.Correia Cc: LEAF User List Subject: RE: [leaf-user] Stumped trying to get Bering uClibc 2.2.0b4 inter faces to light up OK, here's what I did wrong. The User Guide shows how to insert info into /etc/networks/interfaces for PPPoE. It shows all the Please be carefull to which User guide you are using because Bering and Bering-uClibc are almost equal bot not exactly the same. Start from this page and follow the general Bering instructions but beware of the Bering-uClibc specifics... Luis lines for auto, lo, ppp0 and eth1 all together. The interfaces file has them separated out into Steps and Options. Taking it all a little too literally, I stuck all those interface lines together near the top of the file, but also left in all the configuration lines later in the file. As a result, the interfaces had doubled lines in the configuration. The boot was actually trying to tell me that, too; but the warnings weren't dire enough to ring any bells. No errors made it into any of the log files. After removing the duplicates, IP addresses were assigned to the i/f's. Thanks for your help with this. By the way, the PPPoE interface info seems to have eth0 and eth1 info swapped, like it's using eth1 for the outside interface. Also, it uses the 'masklen' keyword instead of 'netmask'. Is that a problem? -John --- Luis.F.Correia [EMAIL PROTECTED] wrote: Hi! They seem to be OK I'm just curious that you don't have _any_ errors on the logs... What does 'ip -s addr' show you? BTW, which exact 486 type is yours? Luis Correia Bering uClibc Team Member PGP Fingerprint: BC44 D7DA 5A17 F92A CA21 9ABE DFF0 3540 2322 21F6 Key Server: http://pgp.mit.edu --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com 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
RE: [leaf-user] Stumped trying to get Bering uClibc 2.2.0b4 inter faces to light up
-Original Message- [snip] I see that you are trying to use the Donald Becker version of the Net drivers. Could you try and use the kernel one instead? AFAIK, it will not need any additional driver. -Luis I removed the 3c509 entry from /etc/modules. (Is that all I needed to do?) The NICs no longer seem to be detected. Output of 'dmesg' and 'ip link show' appended (eth0 and eth1 are missing). -John Sorry, I have misguided you. The cards do need a driver... Apparently the 3c509 driver that comes with the kernel was in fact written by Donald Becker... Please include it again in /etc/modules and post back the dmesg output. Luis Correia Bering uClibc Team Member PGP Fingerprint: BC44 D7DA 5A17 F92A CA21 9ABE DFF0 3540 2322 21F6 Key Server: http://pgp.mit.edu --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com 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
RE: [leaf-user] Stumped trying to get Bering uClibc 2.2.0b4 inter faces to light up
OK, here's what I did wrong. The User Guide shows how to insert info into /etc/networks/interfaces for PPPoE. It shows all the lines for auto, lo, ppp0 and eth1 all together. The interfaces file has them separated out into Steps and Options. Taking it all a little too literally, I stuck all those interface lines together near the top of the file, but also left in all the configuration lines later in the file. As a result, the interfaces had doubled lines in the configuration. The boot was actually trying to tell me that, too; but the warnings weren't dire enough to ring any bells. No errors made it into any of the log files. After removing the duplicates, IP addresses were assigned to the i/f's. Thanks for your help with this. By the way, the PPPoE interface info seems to have eth0 and eth1 info swapped, like it's using eth1 for the outside interface. Also, it uses the 'masklen' keyword instead of 'netmask'. Is that a problem? -John --- Luis.F.Correia [EMAIL PROTECTED] wrote: Hi! They seem to be OK I'm just curious that you don't have _any_ errors on the logs... What does 'ip -s addr' show you? BTW, which exact 486 type is yours? Luis Correia Bering uClibc Team Member PGP Fingerprint: BC44 D7DA 5A17 F92A CA21 9ABE DFF0 3540 2322 21F6 Key Server: http://pgp.mit.edu --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com 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
RE: [leaf-user] Stumped trying to get Bering uClibc 2.2.0b4 inter faces to light up
I see that you are trying to use the Donald Becker version of the Net drivers. Could you try and use the kernel one instead? AFAIK, it will not need any additional driver. Luis Correia Bering uClibc Team Member PGP Fingerprint: BC44 D7DA 5A17 F92A CA21 9ABE DFF0 3540 2322 21F6 Key Server: http://pgp.mit.edu -Original Message- From: John Desmond [mailto:[EMAIL PROTECTED] Sent: Monday, July 05, 2004 2:33 PM To: LEAF Subject: [leaf-user] Stumped trying to get Bering uClibc 2.2.0b4 interfaces to light up Friends- I've stared at this problem for several hours now and must admit I'm missing something very important but can't see it. I'm currently running Bering 1.0-rc3 on a 486 and have run EigerStein and LRP previously, so I've got several years of LEAF under my belt. I downloaded the stock uClibc 2.2.0b4 and made some configuration changes to bring up a PPPoE link with Verizon. I used my old configuration changes as guidance as I stepped through the Bering [ uClibc] Installation [ User] Guides. Everything boots up except eth0 and eth1 appear not to have TCP/IP bound to them and Shorewall spits and hisses about interfaces. The output of ping 127.0.0.1 is: - PING 127.0.0.1 (127.0.0.1): 56 data bytes ping: sendto: Network is unreachable - The output of ip link show is: - 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 noop qlen 1000 link/ether 00:10:4b:00:64:c4 brd ff:ff:ff:ff:ff:ff 4: eth1: BROADCAST,MULTICAST mtu 1500 qdisc noop qlen 1000 link/ether 00:60:08:08:78:81 brd ff:ff:ff:ff:ff:ff - Troubleshooting info follows. The strings in 3c509.o say: - kernel_version=2.4.26 description=3Com Etherlink III (3c509, 3c509B) ISA/PnP ethernet driver - so I seem to have the right compiled version of the ethernet card driver. syslinux.cfg is unchanged from stock. leaf.cfg looks like this: - LRP=root config etc local modules iptables dhcpcd shorwall ulogd dnsmasq dropbear weblet ppp pppoe PKGPATH=/dev/fd0u1680:msdos syst_size=6M log_size=2M - ls -l /lib/modules/3c509.o: - -rwxr-xr-x1 root root13632 Jul 3 10:21 3c509.o - 3c509.o is the first and only uncommented entry in /etc/modules until the PPPOE section, like in my current working /etc/modules. lsmod: - Module Size Used byNot tainted softdog 1508 1 ipt_state336 2 ipt_helper 464 0 (unused) ipt_conntrack820 0 ipt_REDIRECT 544 0 (unused) ipt_MASQUERADE 1056 0 (unused) ip_nat_irc 2152 0 (unused) ip_nat_ftp 2792 0 (unused) iptable_nat15716 2 [ipt_REDIRECT ipt_MASQUERADE ip_nat_irc ip_nat_ftp] ip_conntrack_irc2876 1 ip_conntrack_ftp3484 1 ip_conntrack 18312 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] pppoe 6732 0 (unused) pppox924 1 [pppoe] ppp_synctty 4632 0 (unused) ppp_generic16204 0 [pppoe pppox ppp_synctty] n_hdlc 5792 0 (unused) slhc4296 0 [ppp_generic] 3c509 8240 0 (unused) - dmesg shows the two 3c509's getting IRQs (which IIRC doesn't happen if 3c509.o isn't present): - Linux version 2.4.26 ([EMAIL PROTECTED]) (gcc version 2.95.3 20010315 (release)) #1 Sun Jun 6 11:44:34 CEST 2004 BIOS-provided physical RAM map: BIOS-88: - 0009f000 (usable) BIOS-88: 0010 - 0100 (usable) 16MB LOWMEM available. On node 0 totalpages: 4096 zone(0): 4096 pages. zone(1): 0 pages. zone(2): 0 pages. DMI not present. Kernel command line: BOOT_IMAGE=linux initrd=initrd.lrp init=/linuxrc rw root=/dev/ram0 LEAFCFG=/dev/fd0u1680:msdos Initializing CPU#0 Console: colour VGA+ 80x25 Calibrating delay loop... 33.28 BogoMIPS Memory: 14004k/16384k available (973k kernel code, 1992k reserved, 111k data, 64k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Dentry cache hash table entries: 2048 (order: 2, 16384 bytes) Inode cache hash table entries: 1024 (order: 1, 8192 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 4096 (order: 2, 16384 bytes) CPU: After generic, caps: 0003 CPU: Common caps: 0003 CPU: Intel 486 DX/2 stepping 05 Checking 'hlt' instruction... OK. POSIX
