Thanks for the reply. I have been forced to put the system into use so I have had to use the SCO ppp. I will not get another chance at debug for a couple of weeks and then I can have a more extensive testing effort. I wish I had found the list earlier. I was looking at vger.rudger.edu which ad deceased. Stephen Collier Panavision Australia > -----Original Message----- > From: Alexandre Dulaunoy [mailto:alex@conostix.com] > Sent: Wednesday, 5 December 2001 21:34 > To: Stephen Collier > Cc: 'linux-net@vger.kernel.org' > Subject: Re: linux ppp server SLOW with cisco 801 > > > The best way maybe could be to debug on the both side : > (by doing a ping or telnet session) > > tcpdump -i ppp0 -vv > > on cisco side : > (don't forget term mon) > > debug ppp error > debug ppp negotiation > show debug > > could you send us this debug information ? also the "sh ver" > of the cisco. > > alx > > > > On Tue, 4 Dec 2001, Stephen Collier wrote: > > > I have the following setup > > > > > > XXXXXXXXXppp0 XXXXXXXXXXXXX > > X linux X----------------------------------X cisco 801 X > > XXXXXXXXX192.168.40.1 192.168.40.2XXXXXXXXXXXXX > > 192.168.1.164 192.168.5.1 > > > > The cisco dials into the linux box and the connection is > very slow (for a > > dialup). If I ping cisco to linux it gives a 30% packet > loss but linux to > > cisco gives no packet loss. Telnet linux to cisco is OK but > telnet cisco to > > linux is very slow. I suspect routing but I can't see any > problems. The same > > setup works perfectly on SCO 5.0.4 but I don't want to use > it on that > > server. > > > > routing is setup with ip-up.local on the linux box > > > > Linux is redhat 7.1 with kernel-2.4.2-2 ppp-2.4.0-2 mgetty-1.1.25-5 > > > > netstat -rn on linux > > Kernel IP routing table > > Destination Gateway Genmask Flags MSS > Window irtt > > Iface > > 192.168.40.2 0.0.0.0 255.255.255.255 UH 40 > 0 0 > > ppp0 > > 192.168.5.0 192.168.40.2 255.255.255.0 UG 40 > 0 0 > > ppp0 > > 192.168.1.0 0.0.0.0 255.255.255.0 U 40 > 0 0 > > eth0 > > 127.0.0.0 0.0.0.0 255.0.0.0 U 40 > 0 0 lo > > 0.0.0.0 192.168.1.1 0.0.0.0 UG 40 > 0 0 > > eth0 > > > > show ip route on the cisco > > Codes: C - connected, S - static, I - IGRP, R - RIP, M - > mobile, B - BGP > > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF > inter area > > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA > external type 2 > > E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP > > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * > - candidate > > default > > U - per-user static route, o - ODR, P - periodic > downloaded static > > route > > T - traffic engineered route > > > > Gateway of last resort is 192.168.40.1 to network 0.0.0.0 > > > > 192.168.40.0/24 is variably subnetted, 2 subnets, 2 masks > > C 192.168.40.0/29 is directly connected, Dialer1 > > C 192.168.40.1/32 is directly connected, Dialer1 > > C 192.168.5.0/24 is directly connected, Ethernet0 > > S* 0.0.0.0/0 [1/0] via 192.168.40.1 > > > > Any suggestions as to where to start would be appreciated. > I can provide > > tcpdumps etc. > > > > Stephen Collier > > Panavision Australia > > > > - > > : send the line "unsubscribe > linux-net" in > > the body of a message to majordomo@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > -- > Alexandre Dulaunoy adulau@conostix.com > http://www.conostix.com/ > - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
