I'm using the floppy release of Dachstein V1.0.2 on a 486-66 with 32Meg of memory and two 3c509 NICs. I'm hooked up through a Motorola Surfboard 4100 cable modem to my ISP, Millenium Digital Media (cablespeed.com). eth0 is connected with dhclient to the cable modem and eth1 is for the internal network and is serving DCHP.
Prior to putting together my network, I thought that I had the configuration and filteriing rules finalized when I had e-mail problems and after troublshooting with the ISP, it was realized that the ISP was switching from static IPs to providing dynamic IPs. So it was back to the drawing board. In an effort to speed things up and not having to switch the cables around, rebooting the cable modem, etc., I have been booting the windows machine (with only one 3c900 NIC) with the Dachstein floppy. In looking at the syslog, there appears to be a problem with the dhclient handshaking.
Here is the syslog (this machine has only eth0)
Oct 30 19:06:36 firewall syslogd 1.3-3#31.slink1: restart.
Oct 30 19:06:36 firewall kernel: klogd 1.3-3#31.slink1, log source = /proc/kmsg started.
Oct 30 19:06:36 firewall kernel: Cannot find map file.
Oct 30 19:06:36 firewall kernel: Loaded 7 symbols from 12 modules.
Oct 30 19:06:36 firewall kernel: Linux version 2.2.19-3-LEAF (root@debian) (gcc version 2.7.2.3) #1 Sat Dec 1 12:15:05 CST 2001
Oct 30 19:06:36 firewall kernel: BIOS-provided physical RAM map:
Oct 30 19:06:36 firewall kernel: BIOS-e820: 0009f000 @ 00000000 (usable)
Oct 30 19:06:36 firewall kernel: BIOS-e820: 07ef0000 @ 00100000 (usable)
Oct 30 19:06:36 firewall kernel: Detected 656471 kHz processor.
Oct 30 19:06:36 firewall kernel: Console: colour VGA+ 80x25
Oct 30 19:06:36 firewall kernel: Calibrating delay loop... 1310.72 BogoMIPS
Oct 30 19:06:36 firewall kernel: Memory: 127564k/131008k available (732k kernel code, 416k reserved, 1552k data, 44k init)
Oct 30 19:06:36 firewall kernel: Dentry hash table entries: 16384 (order 5, 128k)
Oct 30 19:06:36 firewall kernel: Buffer cache hash table entries: 131072 (order 7, 512k)
Oct 30 19:06:36 firewall kernel: Page cache hash table entries: 32768 (order 5, 128k)
Oct 30 19:06:36 firewall kernel: CPU: L1 I Cache: 64K L1 D Cache: 64K
Oct 30 19:06:36 firewall kernel: CPU: L2 Cache: 512K
Oct 30 19:06:36 firewall kernel: CPU: AMD-K7(tm) Processor stepping 02
Oct 30 19:06:36 firewall kernel: Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Oct 30 19:06:36 firewall kernel: Checking 'hlt' instruction... OK.
Oct 30 19:06:36 firewall kernel: POSIX conformance testing by UNIFIX
Oct 30 19:06:36 firewall kernel: PCI: PCI BIOS revision 2.10 entry at 0xfdb71
Oct 30 19:06:36 firewall kernel: PCI: Using configuration type 1
Oct 30 19:06:36 firewall kernel: PCI: Probing PCI hardware
Oct 30 19:06:36 firewall kernel: PCI: Enabling I/O for device 00:00
Oct 30 19:06:36 firewall kernel: Linux NET4.0 for Linux 2.2
Oct 30 19:06:36 firewall kernel: Based upon Swansea University Computer Society NET3.039
Oct 30 19:06:36 firewall kernel: NET4: Unix domain sockets 1.0 for Linux NET4.0.
Oct 30 19:06:36 firewall kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Oct 30 19:06:36 firewall kernel: IP Protocols: ICMP, UDP, TCP
Oct 30 19:06:36 firewall kernel: TCP: Hash tables configured (ehash 131072 bhash 65536)
Oct 30 19:06:36 firewall kernel: Initializing RT netlink socket
Oct 30 19:06:36 firewall kernel: Starting kswapd v 1.5
Oct 30 19:06:36 firewall kernel: Software Watchdog Timer: 0.05, timer margin: 60 sec
Oct 30 19:06:36 firewall kernel: Real Time Clock Driver v1.09
Oct 30 19:06:36 firewall kernel: RAM disk driver initialized: 16 RAM disks of 6144K size
Oct 30 19:06:36 firewall kernel: Floppy drive(s): fd0 is 1.44M
Oct 30 19:06:36 firewall kernel: FDC 0 is a post-1991 82077
Oct 30 19:06:36 firewall kernel: RAMDISK: Compressed image found at block 0
Oct 30 19:06:36 firewall kernel: RAMDISK: Uncompressing root archive: done.
Oct 30 19:06:36 firewall kernel: RAMDISK: Auto Filesystem - minix: 2048i 6144bk 68fdz(68) 1024zs 2147483647ms
Oct 30 19:06:36 firewall kernel: VFS: Mounted root (minix filesystem).
Oct 30 19:06:36 firewall kernel: RAMDISK: Extracting root archive: done.
Oct 30 19:06:36 firewall kernel: VFS: Disk change detected on device fd(2,44)
Oct 30 19:06:36 firewall kernel: Freeing unused kernel memory: 44k freed
Oct 30 19:06:36 firewall kernel: 3c59x.c:v0.99Rb 8/8/2000 Donald Becker, [EMAIL PROTECTED]
Oct 30 19:06:36 firewall kernel: http://www.scyld.com/network/vortex.html
Oct 30 19:06:36 firewall kernel: eth0: 3Com 3c900 Cyclone 10Mbps TPO at 0xda00, 00:50:da:c7:26:87, IRQ 11
Oct 30 19:06:36 firewall kernel: 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
Oct 30 19:06:36 firewall kernel: MII transceiver found at address 24, status 182d.
Oct 30 19:06:36 firewall kernel: Enabling bus-master transmits and whole-frame receives.
Oct 30 19:06:36 firewall /usr/sbin/cron[1032]: (CRON) INFO (pidfile fd = 3)
Oct 30 19:06:36 firewall /usr/sbin/cron[1033]: (CRON) STARTUP (fork ok)
Oct 30 19:06:36 firewall dhcpd: Internet Software Consortium DHCP Server 2.0pl5
Oct 30 19:06:36 firewall dhcpd: Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
Oct 30 19:06:36 firewall dhcpd: All rights reserved.
Oct 30 19:06:36 firewall dhcpd:
Oct 30 19:06:36 firewall dhcpd: Please contribute if you find this software useful.
Oct 30 19:06:36 firewall dhcpd: For info, please visit http://www.isc.org/dhcp-contrib.html
Oct 30 19:06:36 firewall dhcpd:
Oct 30 19:06:36 firewall dhcpd: No subnet declaration for eth1 (0.0.0.0).
Oct 30 19:06:36 firewall dhcpd: Please write a subnet declaration in your dhcpd.conf file for the
Oct 30 19:06:36 firewall dhcpd: network segment to which interface eth1 is attached.
Oct 30 19:06:36 firewall dhcpd: exiting.
Oct 30 19:06:36 firewall dhclient: ip length 328 disagrees with bytes received 332.
Oct 30 19:06:36 firewall dhclient: accepting packet with data after udp payload.
Oct 30 19:06:36 firewall dhclient: ip length 328 disagrees with bytes received 332.
Oct 30 19:06:36 firewall dhclient: accepting packet with data after udp payload.
Oct 30 19:06:42 firewall dhclient: ip length 340 disagrees with bytes received 344.
Oct 30 19:06:42 firewall dhclient: accepting packet with data after udp payload.
Oct 30 19:06:48 firewall dhclient: ip length 328 disagrees with bytes received 332.
Oct 30 19:06:48 firewall dhclient: accepting packet with data after udp payload.
Oct 30 19:06:48 firewall dhclient: ip length 328 disagrees with bytes received 332.
Oct 30 19:06:48 firewall dhclient: accepting packet with data after udp payload.
Oct 30 19:06:50 firewall dhclient: ip length 340 disagrees with bytes received 344.
Oct 30 19:06:50 firewall dhclient: accepting packet with data after udp payload.
Oct 30 19:06:51 firewall kernel: Packet log: input DENY eth0 PROTO=2 192.168.100.1:65535 224.0.0.1:65535 L=28 S=0xC0 I=0 F=0x0000 T=1 (#10)
Oct 30 19:06:52 firewall dhclient: ip length 328 disagrees with bytes received 332.
Oct 30 19:06:52 firewall dhclient: accepting packet with data after udp payload.
Oct 30 19:06:52 firewall dhclient: ip length 328 disagrees with bytes received 332.
Oct 30 19:06:52 firewall dhclient: accepting packet with data after udp payload.
Oct 30 19:06:58 firewall dhclient: ip length 340 disagrees with bytes received 344.
Oct 30 19:06:58 firewall dhclient: accepting packet with data after udp payload.
[snip]
Performing 'ip addr show' results in the following
1: lo: <LOOPBACK,UP> mtu 3924 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 global lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:50:da:c7:26:87 brd ff:ff:ff:ff:ff:ff
inet 66.235.19.223/22 brd 66.235.19.255 scope global eth0
and 'ip route show' shows
66.235.16.0/22 dev eth0 proto kernel scope link src 66.235.19.223
default via 66.235.16.1 dev eth0
In looking at past archives of various messages, it was pointed out that it could be a driver problem. So I hooked up the box with the 3c509 NICs and got the same indications. So to be sure it was not the driver for the 3c905 (3c59x.o), I booted a machine on the network at work, which has a 3c905 NIC and did not see the dhclient errors in syslog. Other messages thought that it could be a multicast vs unicast issue.From the above I would assume that dhclient got the correct information.
I looked at dhclient.conf, which is very minimal, wondering if it needs to be expanded with more options. If it does have something to do with the ISP DHCP server, what questions do I need to ask in order to setup dhclient on the firewall properly?
I can ping the servers on the internet and have sent mail from the firewall.
Thank you for any insight and words of wisdom.
John Wittenberg
_________________________________________________________________
Choose an Internet access plan right for you -- try MSN! http://resourcecenter.msn.com/access/plans/default.asp
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
------------------------------------------------------------------------
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
