On Sunday 14 July 2002 19:17, David Pitts wrote: > Thanks for your response Lynn. This is the info you requested. All > assistance gratefully accepted! > Syslog
> 07:40:55 firewall kernel: tulip.c:v0.92m 9/22/2000 Written by Donald > Becker <[EMAIL PROTECTED]> Jul 15 07:40:55 firewall kernel: > http://www.scyld.com/network/tulip.html Jul 15 07:40:55 firewall > kernel: eth0: Digital DC21041 Tulip rev 17 at 0xc183b800, > 00:00:F8:03:C1:E3, IRQ 10. Jul 15 07:40:55 firewall kernel: eth0: > 21041 Media table, default media 0800 (Autosense). Jul 15 07:40:55 > firewall kernel: eth0: 21041 media #0, 10baseT. Jul 15 07:40:55 > firewall kernel: eth0: 21041 media #1, 10base2. Jul 15 07:40:55 > firewall kernel: eth0: 21041 media #2, AUI. Jul 15 07:40:55 firewall > kernel: eth0: 21041 media #4, 10baseT-FDX. Jul 15 07:40:55 firewall Good. > kernel: eth1: Digital DC21041 Tulip rev 17 at 0xc183dc00, > 00:00:F8:00:A9:67, IRQ 11. Jul 15 07:40:55 firewall kernel: eth1: > 21041 Media table, default media 0800 (Autosense). Jul 15 07:40:55 > firewall kernel: eth1: 21041 media #0, 10baseT. Jul 15 07:40:55 > firewall kernel: eth1: 21041 media #1, 10base2. Jul 15 07:40:55 > firewall kernel: eth1: 21041 media #2, AUI. Jul 15 07:40:55 firewall > kernel: eth1: 21041 media #4, 10baseT-FDX. Jul 15 07:40:55 firewall > kernel: eth0: 21143 10baseT link beat good. Jul 15 07:40:55 firewall > kernel: eth1: 21143 10baseT link beat good. Jul 15 07:40:55 firewall Good. > 07:40:55 firewall udhcpd: udhcp server (v0.9.6) started Jul 15 This is correct for the LAN dhcp server. Your LAN clients should be able to get an ip address. > 07:40:55 firewall bpalogin: Parameter debuglevel set to 2 Jul 15 > 07:40:55 firewall bpalogin: Parameter debuglevel set to 2 Jul 15 > 07:40:55 firewall bpalogin: Parameter localport set to 5050 Jul 15 > 07:40:55 firewall bpalogin: Parameter localport set to 5050 Jul 15 > 07:40:55 firewall bpalogin: Parameter minheartbeatinterval set to 60 > Jul 15 07:40:55 firewall bpalogin[851]: BPALogin v2.0 - lightweight > portable BIDS2 login client Jul 15 07:40:55 firewall bpalogin[851]: > Auth host = 61.9.240.13:5050 Jul 15 07:40:55 firewall bpalogin[851]: > Listening on port 5050 Jul 15 07:40:55 firewall bpalogin[851]: Cant > connect to auth server - Network is unreachable Jul 15 07:40:55 > firewall bpalogin[851]: Sleeping for 60 seconds Jul 15 07:41:56 > firewall bpalogin[851]: Auth host = 61.9.240.13:5050 Jul 15 07:41:56 > firewall bpalogin[851]: Listening on port 5050 Jul 15 07:41:56 > firewall bpalogin[851]: Cant connect to auth server - Network is > unreachable Jul 15 07:41:56 firewall bpalogin[851]: Sleeping for 60 The dhcp client doesn't appear to have been started. If you do not receive an ip address via DHCP, the BPA login application cannot reach it's server. Strange that there is no messages from the dhcp client program, I wonder if the RCDLinks init number in the BPA program is the same as the dhcp client script. I know that dhclient and udhcp client use the same init number. If two init scripts use the same init number, only one will work. > IP Route > > 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.254 > > IP Address > > 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:00:f8:03:c1:e3 brd ff:ff:ff:ff:ff:ff > 3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 > link/ether 00:00:f8:00:a9:67 brd ff:ff:ff:ff:ff:ff > inet 192.168.1.254/24 brd 192.168.1.255 scope global eth1 > This confirms that the dhcp client script hasn't been run or a lease hasn't been received on eth0. You say that your LAN client machines are unable to get a lease from the firewall's dhcp server? I would suspect first that eth0 is connected to the LAN and eth1 is connected to the ISP.... have you tried switching the cables yet??? Next I would suspect that there is a cabling/hub problem. Are you using cross-over cables/normal cables in the proper places??? Post copy of these files to check for an init numbering conflict: /etc/init.d/udhcpc /etc/init.d/bpalogin -- ~Lynn Avants aka Guitarlynn guitarlynn at users.sourceforge.net http://leaf.sourceforge.net If linux isn't the answer, you've probably got the wrong question! ------------------------------------------------------- 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
