Still can't connect - long post

I've sent several posts recently lamenting that I can't make an
internect connection with Xandros 3 deluxe and a NetComm internal
modem. When I try the modem makes dial sounds, but after a few
seconds a connection failed message occurs.

I've been working slowly through GW Unruh's post on making a internect
connection, but as I mentioned in an earlier post entering route at
the console just gives me the headings but no numbers or anything
else. As described in that paper I've set up /var/ppplog to try to
record what happens, and have added that file and other files below.
I'm sorry that it's such a long post, but I thought I'd better include
everything from my last attempt to log on this afternoon.

I would be most grateful if Mr. Unruh and the others who have tried to
help me could look through the files and tell me what I'm doing wrong.

Regards, Alex


Contents of various files

/etc/resolv.conf
domain iinet.net.au
nameserver 203.0.178.191

/etc/host.conf
order hosts,bind
multi on

#/etc/nsswitch.conf
Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: compat
group: compat
shadow: compat
hosts: files dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis

Logfile from attempted connection
----- Connection Start -----
ATZ Q0 V1 E0V1
OK
ATL1
OK
ATDT 0198379000
CONNECT 34666 V42bis
User Access Verification
login:
ATH
ERROR

/var/ppp-connect-errors
dodtrigger: SIGUSR2 signal received.
dodtrigger: exiting with status: 0
sh: line 1: /user/sbin/chat: No such file or directory

/var/ppplog
Jun 4 00:00:20 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 00:00:23 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 00:00:28 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 00:00:31 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 00:00:31 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 00:00:31 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 00:09:23 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 00:09:30 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 00:09:34 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 00:09:34 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 00:09:34 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 00:22:59 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 00:23:03 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 00:23:10 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 00:23:10 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 00:23:10 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 00:30:46 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 00:30:51 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 00:30:57 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 00:30:57 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 00:30:57 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 00:45:21 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 00:45:26 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 00:45:32 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 00:45:32 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 00:45:32 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 00:56:41 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 00:56:48 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 00:56:52 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 00:56:52 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 00:56:52 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 01:07:28 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 01:07:32 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 01:07:39 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 01:07:39 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 01:07:39 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 01:16:21 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 01:16:24 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 01:16:27 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 01:16:32 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 01:16:32 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 01:16:32 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 01:22:57 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 01:23:03 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 01:23:08 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 01:23:08 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 01:23:08 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 01:31:04 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 01:31:11 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 01:31:15 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 01:31:15 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 01:31:15 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 01:41:59 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 01:42:04 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 01:42:09 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 1
Jun 4 01:42:10 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 01:42:10 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 01:42:10 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 01:49:47 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 01:49:54 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 01:49:58 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 01:49:58 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 01:49:58 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 01:56:33 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 01:56:38 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 01:56:44 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 01:56:44 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 01:56:44 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 02:02:58 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 8
Jun 4 02:03:06 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 02:03:09 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 02:03:09 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 02:03:09 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 02:14:55 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 02:15:01 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 02:15:06 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 02:15:06 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 02:15:06 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 02:25:38 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 8
Jun 4 02:25:46 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 02:25:49 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 02:25:49 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 02:25:49 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 02:35:18 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 02:35:21 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 02:35:25 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 02:35:29 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 02:35:29 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 02:35:29 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 02:47:04 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 02:47:11 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 02:47:15 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 02:47:15 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 02:47:15 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 02:57:51 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 02:57:56 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 02:58:02 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 02:58:02 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 02:58:02 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 03:10:01 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 03:10:08 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 03:10:12 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 03:10:12 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 03:10:12 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 03:23:14 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 8
Jun 4 03:23:22 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 03:23:25 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 03:23:25 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 03:23:25 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 03:30:36 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 03:30:43 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 03:30:47 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 03:30:47 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 03:30:47 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 03:44:43 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 03:44:48 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 03:44:54 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 03:44:54 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 03:44:54 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 03:59:24 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 03:59:30 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 03:59:35 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 03:59:35 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 03:59:35 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 04:13:15 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 04:13:18 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 04:13:25 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 1
Jun 4 04:13:26 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 04:13:26 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 04:13:26 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 04:28:04 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 04:28:10 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 04:28:15 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 04:28:15 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 04:28:15 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 04:38:52 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 04:38:57 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 04:39:03 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 04:39:03 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 04:39:03 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 04:45:22 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 04:45:29 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 04:45:33 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 04:45:33 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 04:45:33 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 04:53:40 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 8
Jun 4 04:53:48 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 04:53:51 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 04:53:51 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 04:53:51 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 05:04:32 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 8
Jun 4 05:04:40 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 05:04:43 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 05:04:43 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 05:04:43 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 05:16:18 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 05:16:24 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 05:16:29 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 05:16:29 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 05:16:29 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 05:29:08 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 05:29:15 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 05:29:19 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 05:29:19 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 05:29:19 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 05:37:35 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 05:37:39 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 05:37:46 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 05:37:46 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 05:37:46 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 05:49:39 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 05:49:44 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 05:49:50 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 05:49:50 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 05:49:50 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 06:01:17 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 06:01:21 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 06:01:28 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 06:01:28 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 06:01:28 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 06:10:52 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 06:10:57 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 06:11:03 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 06:11:03 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 06:11:03 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 06:17:59 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 8
Jun 4 06:18:07 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 06:18:10 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 06:18:10 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 06:18:10 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 06:24:22 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 8
Jun 4 06:24:30 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 06:24:33 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 06:24:33 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 06:24:33 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 06:36:18 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 06:36:21 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 06:36:28 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 1
Jun 4 06:36:29 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 06:36:29 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 06:36:29 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 06:48:27 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 06:48:34 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 06:48:38 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 06:48:38 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 06:48:38 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 06:57:38 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 06:57:45 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 06:57:49 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 06:57:49 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 06:57:49 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 07:10:54 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 8
Jun 4 07:11:02 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 07:11:05 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 07:11:05 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 07:11:05 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 07:18:20 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 07:18:26 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 07:18:31 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 07:18:31 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 07:18:31 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 07:25:32 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 07:25:38 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 07:25:43 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 07:25:43 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 07:25:43 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 07:38:16 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 07:38:19 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 07:38:23 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 07:38:27 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 07:38:27 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 07:38:27 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 07:50:20 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 8
Jun 4 07:50:28 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 07:50:31 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 07:50:31 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 07:50:31 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 08:03:43 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 08:03:48 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 08:03:54 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 08:03:54 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 08:03:54 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 08:14:49 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 08:14:54 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 08:15:00 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 08:15:00 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 08:15:00 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 08:28:57 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 08:29:04 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 08:29:08 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 08:29:08 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 08:29:08 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 08:34:47 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 08:34:52 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 08:34:57 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 1
Jun 4 08:34:58 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 08:34:58 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 08:34:58 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 08:44:00 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 08:44:05 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 08:44:11 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 08:44:11 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 08:44:11 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 08:55:53 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 08:55:56 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 08:56:01 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 08:56:04 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 08:56:04 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 08:56:04 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 09:08:05 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 09:08:09 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 09:08:15 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 1
Jun 4 09:08:16 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 09:08:16 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 09:08:16 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 09:08:41 XANP4585M5 init: Switching to runlevel: 6
Jun 4 09:08:50 XANP4585M5 rpc.statd[3842]: Caught signal 15,
un-registering and exiting.
Jun 4 10:09:25 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 10:09:31 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 10:09:32 XANP4585M5 rpc.statd[3845]: Version 1.0.6 Starting
Jun 4 10:09:32 XANP4585M5 rpc.statd[3845]: statd running as root.
chown /var/lib/nfs/sm to choose different user
Jun 4 10:09:36 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 10:09:36 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 10:09:36 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 10:14:55 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 10:15:00 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 10:15:06 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 10:15:06 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 10:15:06 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 10:23:54 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 10:24:01 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 10:24:05 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 10:24:05 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 10:24:05 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 10:31:30 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 10:31:36 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 10:31:41 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 10:31:41 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 10:31:41 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 10:36:43 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 10:36:48 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 10:36:54 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 10:36:54 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 10:36:54 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 10:48:06 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 10:48:12 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 10:48:17 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 10:48:17 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 10:48:17 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 11:02:51 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 11:02:57 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 11:03:02 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 11:03:02 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 11:03:02 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 11:10:00 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 11:10:03 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Jun 4 11:10:10 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 1
Jun 4 11:10:11 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 11:10:11 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 11:10:11 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 11:23:26 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 11:23:29 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 11:23:33 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Jun 4 11:23:37 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 11:23:37 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 11:23:37 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 11:36:11 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 11:36:16 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 11:36:22 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 11:36:22 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 11:36:22 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 11:41:22 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 11:41:25 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 11:41:31 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 2
Jun 4 11:41:33 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 11:41:33 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 11:41:33 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 11:47:12 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 6
Jun 4 11:47:18 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Jun 4 11:47:23 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 11:47:23 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 11:47:23 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 12:00:53 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 12:00:56 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 8
Jun 4 12:01:04 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 12:01:04 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 12:01:04 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 12:07:02 XANP4585M5 pppd[15254]: The remote system is required
to authenticate itself
Jun 4 12:07:02 XANP4585M5 pppd[15254]: but I couldn't find any
suitable secret (password) for it to use to do so.
Jun 4 12:07:17 XANP4585M5 pppd[15282]: The remote system is required
to authenticate itself
Jun 4 12:07:17 XANP4585M5 pppd[15282]: but I couldn't find any
suitable secret (password) for it to use to do so.
Jun 4 12:08:46 XANP4585M5 pppd[15418]: The remote system is required
to authenticate itself
Jun 4 12:08:46 XANP4585M5 pppd[15418]: but I couldn't find any
suitable secret (password) for it to use to do so.
Jun 4 12:14:19 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 8
Jun 4 12:14:27 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 12:14:30 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 12:14:30 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 12:14:30 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 12:21:20 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
Jun 4 12:21:23 XANP4585M5 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 8
Jun 4 12:21:31 XANP4585M5 dhclient: No DHCPOFFERS received.
Jun 4 12:21:31 XANP4585M5 dhclient: No working leases in persistent
database - sleeping.
Jun 4 12:21:31 XANP4585M5 dhclient: receive_packet failed on eth0:
Network is down
Jun 4 12:27:46 XANP4585M5 pppd[17307]: pppd 2.4.2 started by root,
uid 0
Jun 4 12:27:46 XANP4585M5 pppd[17307]: Using interface ppp0
Jun 4 12:27:46 XANP4585M5 pppd[17307]: Connect: ppp0 <-->
/dev/tts/Winmodem0
Jun 4 12:27:46 XANP4585M5 pppd[17307]: Remote message: Authentication
failed
Jun 4 12:27:46 XANP4585M5 pppd[17307]: PAP authentication failed
Jun 4 12:27:46 XANP4585M5 pppd[17307]: Connection terminated.
Jun 4 12:27:46 XANP4585M5 pppd[17307]: Exit.

Alex Bell wrote:

> I've sent several posts recently lamenting that I can't make an
> internect connection with Xandros 3 deluxe and a NetComm internal
> modem. When I try the modem makes dial sounds, but after a few
> seconds a connection failed message occurs.
>
> I've been working slowly through GW Unruh's post on making a internect
> connection, but as I mentioned in an earlier post entering route at
> the console just gives me the headings but no numbers or anything
> else. As described in that paper I've set up /var/ppplog to try to
> record what happens, and have added that file and other files below.
> I'm sorry that it's such a long post, but I thought I'd better include
> everything from my last attempt to log on this afternoon.
>
> I would be most grateful if Mr. Unruh and the others who have tried to
> help me could look through the files and tell me what I'm doing wrong.
>
> Regards, Alex
>
>
> Contents of various files
>
> /etc/resolv.conf
> domain iinet.net.au
> nameserver 203.0.178.191
>
> /etc/host.conf
> order hosts,bind
> multi on
>
> #/etc/nsswitch.conf
> Example configuration of GNU Name Service Switch functionality.
> # If you have the `glibc-doc' and `info' packages installed, try:
> # `info libc "Name Service Switch"' for information about this file.
> passwd: compat
> group: compat
> shadow: compat
> hosts: files dns
> networks: files
> protocols: db files
> services: db files
> ethers: db files
> rpc: db files
> netgroup: nis
>
> Logfile from attempted connection
> ----- Connection Start -----
> ATZ Q0 V1 E0V1
> OK
> ATL1
> OK
> ATDT 0198379000
> CONNECT 34666 V42bis
> User Access Verification
> login:
> ATH
> ERROR
>
> /var/ppp-connect-errors
> dodtrigger: SIGUSR2 signal received.
> dodtrigger: exiting with status: 0
> sh: line 1: /user/sbin/chat: No such file or directory
>

Well it appears one of your PPP scripts is incorrectly pointing
to /user/sbin/chat rather than /usr/sbin/chat

[snippage]
> Jun 4 12:27:46 XANP4585M5 pppd[17307]: pppd 2.4.2 started by root,
> uid 0
> Jun 4 12:27:46 XANP4585M5 pppd[17307]: Using interface ppp0
> Jun 4 12:27:46 XANP4585M5 pppd[17307]: Connect: ppp0 <-->
> /dev/tts/Winmodem0
> Jun 4 12:27:46 XANP4585M5 pppd[17307]: Remote message: Authentication
> failed
> Jun 4 12:27:46 XANP4585M5 pppd[17307]: PAP authentication failed
> Jun 4 12:27:46 XANP4585M5 pppd[17307]: Connection terminated.
> Jun 4 12:27:46 XANP4585M5 pppd[17307]: Exit.

From what this appears to be is that your modem is connecting, but the
authentication part is failing, probably to the above error in the PPP
script.
Now I'm not using Xandros but looking at /usr/share/doc/packages/ppp/SETUP
the file should be /etc/ppp/peers.

Bruce S.
--
Replace the by by blueyonder.

Alex Bell <(E-Mail Removed)> wrote:
> I've sent several posts recently lamenting that I can't make an
> internect connection with Xandros 3 deluxe and a NetComm internal
> modem. When I try the modem makes dial sounds, but after a few
> seconds a connection failed message occurs.
....

> Jun 4 12:01:04 XANP4585M5 dhclient: No DHCPOFFERS received.
> Jun 4 12:01:04 XANP4585M5 dhclient: No working leases in persistent
> database - sleeping.
> Jun 4 12:01:04 XANP4585M5 dhclient: receive_packet failed on eth0:
> Network is down

What are all these DHCP Discovery requests supposed to do? They clutter
the log for no good reason that I can see.

> Jun 4 12:07:02 XANP4585M5 pppd[15254]: The remote system is required
> to authenticate itself
> Jun 4 12:07:02 XANP4585M5 pppd[15254]: but I couldn't find any
> suitable secret (password) for it to use to do so.

This is the reason for the failure. You require the peer to authenticate
itself to you. Rare indeed is the ISP that will do so. Maybe due to a
mistakenly configured require-chap or require-pap option? Read man pppd
(more carefully?).

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* 97.3% of all statistics are made up. */

On Sat, 04 Jun 2005 15:54:24 GMT, Bruce Stewart
<(E-Mail Removed)> wrote:

>Alex Bell wrote:
>
>> I've sent several posts recently lamenting that I can't make an
>> internect connection with Xandros 3 deluxe and a NetComm internal
>> modem. When I try the modem makes dial sounds, but after a few
>> seconds a connection failed message occurs.
>>
>> I've been working slowly through GW Unruh's post on making a internect
>> connection, but as I mentioned in an earlier post entering route at
>> the console just gives me the headings but no numbers or anything
>> else. As described in that paper I've set up /var/ppplog to try to
>> record what happens, and have added that file and other files below.
>> I'm sorry that it's such a long post, but I thought I'd better include
>> everything from my last attempt to log on this afternoon.
>>
>> I would be most grateful if Mr. Unruh and the others who have tried to
>> help me could look through the files and tell me what I'm doing wrong.
>>
>> Regards, Alex
>>
>>
>> Contents of various files
>>
>> /etc/resolv.conf
>> domain iinet.net.au
>> nameserver 203.0.178.191
>>
>> /etc/host.conf
>> order hosts,bind
>> multi on
>>
>> #/etc/nsswitch.conf
>> Example configuration of GNU Name Service Switch functionality.
>> # If you have the `glibc-doc' and `info' packages installed, try:
>> # `info libc "Name Service Switch"' for information about this file.
>> passwd: compat
>> group: compat
>> shadow: compat
>> hosts: files dns
>> networks: files
>> protocols: db files
>> services: db files
>> ethers: db files
>> rpc: db files
>> netgroup: nis
>>
>> Logfile from attempted connection
>> ----- Connection Start -----
>> ATZ Q0 V1 E0V1
>> OK
>> ATL1
>> OK
>> ATDT 0198379000
>> CONNECT 34666 V42bis
>> User Access Verification
>> login:
>> ATH
>> ERROR
>>
>> /var/ppp-connect-errors
>> dodtrigger: SIGUSR2 signal received.
>> dodtrigger: exiting with status: 0
>> sh: line 1: /user/sbin/chat: No such file or directory
>>
>
>Well it appears one of your PPP scripts is incorrectly pointing
>to /user/sbin/chat rather than /usr/sbin/chat
>
>[snippage]
>> Jun 4 12:27:46 XANP4585M5 pppd[17307]: pppd 2.4.2 started by root,
>> uid 0
>> Jun 4 12:27:46 XANP4585M5 pppd[17307]: Using interface ppp0
>> Jun 4 12:27:46 XANP4585M5 pppd[17307]: Connect: ppp0 <-->
>> /dev/tts/Winmodem0
>> Jun 4 12:27:46 XANP4585M5 pppd[17307]: Remote message: Authentication
>> failed
>> Jun 4 12:27:46 XANP4585M5 pppd[17307]: PAP authentication failed
>> Jun 4 12:27:46 XANP4585M5 pppd[17307]: Connection terminated.
>> Jun 4 12:27:46 XANP4585M5 pppd[17307]: Exit.
>
>From what this appears to be is that your modem is connecting, but the
>authentication part is failing, probably to the above error in the PPP
>script.
>Now I'm not using Xandros but looking at /usr/share/doc/packages/ppp/SETUP
>the file should be /etc/ppp/peers.
>
>Bruce S.

Thanks, Bruce. That's a big help. I don't suppose you could point
this helpless newbie to the script so I can change it?

Regards, Alex

On Sat, 4 Jun 2005 12:27:47 -0500, Clifford Kite
<(E-Mail Removed)> wrote:

>Alex Bell <(E-Mail Removed)> wrote:
>> I've sent several posts recently lamenting that I can't make an
>> internect connection with Xandros 3 deluxe and a NetComm internal
>> modem. When I try the modem makes dial sounds, but after a few
>> seconds a connection failed message occurs.
>...
>
>> Jun 4 12:01:04 XANP4585M5 dhclient: No DHCPOFFERS received.
>> Jun 4 12:01:04 XANP4585M5 dhclient: No working leases in persistent
>> database - sleeping.
>> Jun 4 12:01:04 XANP4585M5 dhclient: receive_packet failed on eth0:
>> Network is down
>
>What are all these DHCP Discovery requests supposed to do? They clutter
>the log for no good reason that I can see.
>
>> Jun 4 12:07:02 XANP4585M5 pppd[15254]: The remote system is required
>> to authenticate itself
>> Jun 4 12:07:02 XANP4585M5 pppd[15254]: but I couldn't find any
>> suitable secret (password) for it to use to do so.
>
>This is the reason for the failure. You require the peer to authenticate
>itself to you. Rare indeed is the ISP that will do so. Maybe due to a
>mistakenly configured require-chap or require-pap option? Read man pppd
>(more carefully?).
Thanks, Clifford. I've just this evening discovered how to read man
pppd.

Regards, Alex

On Sat, 04 Jun 2005 17:33:10 -0500, (E-Mail Removed)
(Moe Trin) wrote:

>In article <(E-Mail Removed)>, Alex Bell wrote:
>
>>As described in that paper I've set up /var/ppplog to try to
>>record what happens, and have added that file and other files below.
>>I'm sorry that it's such a long post, but I thought I'd better include
>>everything from my last attempt to log on this afternoon.
>
>I think you managed to typo the instruction in /etc/syslog.conf, but after
>putting the post through a few grep -v commands, I see:
>
>/etc/resolv.conf
>
>OK
>
>>/etc/host.conf
>
>OK
>
>>#/etc/nsswitch.conf
>
>OK
>
>>Logfile from attempted connection
>>----- Connection Start -----
>>ATZ Q0 V1 E0V1
>>OK
>
>Do you know what the ATZ is resetting to? That resets to some value you
>saved to NVRAM, which may or may not be valid. THAT is why I said to use
>the AT&F0 command.
>
>>CONNECT 34666 V42bis
>>User Access Verification
>>login:
>
>Connect script is wrong - but not shown. It should be as shown on my
>post yesterday morning. To refresh your mind, that is
>
>ABORT BUSY ABORT 'NO CARRIER' "" AT&F0 OK ATDT2662902 CONNECT \d\c
>
>>/var/ppp-connect-errors
>
>This has everything under the sun - most of which has no bearing on ppp.
>This is because you mistyped something in /etc/syslog.conf (review what
>was in Unruh's paper) and you are missing the 'debug' option in your
>script or in /etc/ppp/options. Compare this mess with the bottom of
>my post to you yesterday morning in the thread "How to determine which
>port modem is on? etc."
>
>>sh: line 1: /user/sbin/chat: No such file or directory
>
>TYPO /usr/sbin/chat
>
>>/var/ppplog
>
>>Jun 4 12:07:02 XANP4585M5 pppd[15254]: The remote system is required
>>to authenticate itself
>>Jun 4 12:07:02 XANP4585M5 pppd[15254]: but I couldn't find any
>>suitable secret (password) for it to use to do so.
>
>EITHER - you have the 'auth' or 'require-pap' or 'require-chap' option
>somewhere in your script, OR you have an existing default route in your
>networking setup.
>
>>Jun 4 12:27:46 XANP4585M5 pppd[17307]: Connect: ppp0 <-->
>>/dev/tts/Winmodem0
>>Jun 4 12:27:46 XANP4585M5 pppd[17307]: Remote message: Authentication
>>failed
>>Jun 4 12:27:46 XANP4585M5 pppd[17307]: PAP authentication failed
>>Jun 4 12:27:46 XANP4585M5 pppd[17307]: Connection terminated.
>
>OK, this time things worked (apparently you got rid of the previous
>problems) but you authenticated incorrectly. This could be because you
>are missing the 'user abell1' option (either in the dialing script, or
>in /etc/ppp/options), or you have the user or password incorrect in the
>/etc/ppp/*ap-secrets files.
>
> Old guy

Thanks, Moe. I'll work through this once I get back into Xandros.
Please don't give up on me.

Regards, Alex