Date: Sat, 26 Apr 1997 23:54:33 -0700 (PDT) From: batie@agora.rdrop.com (Alan Batie) To: hackers@freebsd.org Subject: pppd on 2.2 Message-ID: <m0wLNqz-0009AoC@agora.rdrop.com>
next in thread | raw e-mail | index | archive | help
I just installed a 2.2.1-RELEASE system for a friend, with the following
symptoms:
I have tun0 configured to dialout to his ISP (dedicated 28.8)
ppp0 is configured for clients to call into him, basically for local email.
The split is just cuz it looked easier to do dialouts with iijppp and dialins
with pppd.
When using the stock pppd:
Apr 21 22:00:01 e-cafe getty[288]: getty: starting ppplogin (/usr/sbin/pppd) on /dev/ttyd1
Apr 21 22:00:07 e-cafe getty[350]: getty: starting ppplogin (/usr/sbin/pppd) on /dev/ttyd1
Apr 21 22:00:13 e-cafe getty[351]: getty: starting ppplogin (/usr/sbin/pppd) on /dev/ttyd1
Apr 21 22:00:19 e-cafe getty[352]: getty: starting ppplogin (/usr/sbin/pppd) on /dev/ttyd1
Apr 21 22:00:25 e-cafe getty[353]: getty: starting ppplogin (/usr/sbin/pppd) on /dev/ttyd1
Apr 21 22:02:02 e-cafe getty[355]: getty: starting ppplogin (/usr/sbin/pppd) on /dev/ttyd1
So I pulled the one from my 2.1.5 system which is working just fine there
(with some hacks to add in utmp logging). With that, it appears to be
getting connected just fine:
$ ifconfig ppp0
ppp0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 552
inet 204.245.198.33 --> 204.245.198.62 netmask 0xfffffff0
$ netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
ed0 1500 <Link> 00.80.48.88.4c.92 134 0 174 0 0
ed0 1500 204.245.198.3 204.245.198.33 134 0 174 0 0
tun0 1500 <Link> 433 0 416 0 0
tun0 1500 204.245.198 204.245.198.33 433 0 416 0 0
ppp0 552 <Link> 93 1 50 0 0
ppp0 552 204.245.198.3 204.245.198.33 93 1 50 0 0
lo0 16384 <Link> 4 0 4 0 0
lo0 16384 127 127.0.0.1 4 0 4 0 0
$ netstat -rn
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 199.2.96.37 UGc 20 325 tun0
127 127.0.0.1 URc 0 0 lo0
127.0.0.1 127.0.0.1 UH 0 1 lo0
199.2.96.37 204.245.198.33 UH 19 0 tun0
204.245.198.32/28 link#1 UC 0 0
204.245.198.33 0:80:48:88:4c:92 UHLW 1 21 lo0
204.245.198.40 8:0:7:a6:f:60 UHLW 0 306 ed0 156
204.245.198.62 204.245.198.33 UH 0 2 ppp0
224.0.0.9 127.0.0.1 UH 1 1 lo0
However:
$ ping 204.245.198.62
PING 204.245.198.62 (204.245.198.62): 56 data bytes
ping: sendto: Network is down
ping: wrote 204.245.198.62 64 chars, ret=-1
ping: sendto: Network is down
ping: wrote 204.245.198.62 64 chars, ret=-1
^C
--- 204.245.198.62 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
I hacked some kernel printfs into if_ppp.c, and find that the ENETDOWN
message is coming from the NPMODE check:
/*
* Drop this packet, or return an error, if necessary.
*/
if (mode == NPMODE_ERROR) {
printf("ppp driver: NPMODE ERROR\n");
error = ENETDOWN;
goto bad;
}
I'm starting to reach my limits now; it looks like npmode is related to
one of the ppp commands, and I really don't know much about the bits...
Thanks for any help...
--
Alan Batie ______ It's not my fault! It's some guy
batie@agora.rdrop.com \ / named "General Protection"!
+1 503 452-0960 \ / --Ratbert
PGP FP: DE 3C 29 17 C0 49 \/ 7A 27 40 A5 3C 37 4A DA 52 B9
It is my policy to avoid purchase of any products from companies which
use unrequested email advertisements or telephone solicitation.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0wLNqz-0009AoC>