LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 10-20-2004, 09:12 PM   #1
BillJennings
Member
 
Registered: Oct 2004
Location: Big River, California, USA
Distribution: Debian
Posts: 48

Rep: Reputation: 15
Windows XP dialup to Linux dies after 20 seconds


I have set up several Linux boxes as dialup servers. They seem to connect just fine, and I can ping the linux box from the windows box... for about 15 to 20 seconds. Then the pings start timing out and the windows box starts counting receive errors. Also, it dies immediately if I try to ping the windows box from the linux box.

Here is /etc/ppp/options:

10.0.1.2:
ms-dns 10.0.1.2
asyncmap 0
auth
crtscts
lock
hide-password
modem
debug 7
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx

Here is /etc/mgetty/login.config

/AutoPPP/ - a_ppp /usr/sbin/pppd auth -chap +pap login debug
* - - /bin/login @

Here is "ifconfig ppp0" after it stops working:

ppp0 Link encap:Point-to-Point Protocol
inet addr:10.0.1.2 P-t-P:10.0.1.8 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:30 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:2471 (2.4 KiB) TX bytes:1237 (1.2 KiB)

Here is "tcpdump -n -i ppp0":

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ppp0, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
19:04:05.801640 IP 10.0.1.8 > 224.0.0.22: igmp v3 report, 1 group record(s)
19:04:06.151559 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 512
19:04:06.151571 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 512
19:04:07.151366 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 768
19:04:07.151382 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 768
19:04:08.051193 IP 10.0.1.8.3136 > 239.255.255.250.1900: UDP, length: 133
19:04:08.161169 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 1024
19:04:08.161176 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 1024
19:04:09.160979 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 1280
19:04:09.160987 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 1280
19:04:10.000820 IP 10.0.1.8.68 > 255.255.255.255.67: BOOTP/DHCP, Request, length: 300
19:04:10.150787 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 1536
19:04:10.150794 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 1536
19:04:11.060616 IP 10.0.1.8.3136 > 239.255.255.250.1900: UDP, length: 133
19:04:11.150596 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 1792
19:04:11.150603 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 1792
19:04:12.150408 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 2048
19:04:12.150420 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 2048
19:04:13.160214 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 2304
19:04:13.160221 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 2304
19:04:14.160024 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 2560
19:04:14.160034 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 2560
19:04:15.159833 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 2816
19:04:15.159845 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 2816
19:04:16.169641 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 3072
19:04:16.169650 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 3072
19:04:17.159454 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 3328
19:04:17.159462 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 3328
19:04:18.159263 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 3584
19:04:18.159269 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 3584
19:04:19.159074 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 3840
19:04:19.159084 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 3840
19:04:20.168884 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 4096
19:04:20.168892 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 4096
19:04:21.168695 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 4352
19:04:21.168706 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 4352

19:04:26.347719 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 4608
19:04:26.347729 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 4608
19:04:27.347530 IP 10.0.1.8 > 10.0.1.2: icmp 40: echo request seq 4864
19:04:27.347539 IP 10.0.1.2 > 10.0.1.8: icmp 40: echo reply seq 4864

notice the gap... one ping times out, then one gets through, then nothing gets through.

I've googled for this for several days and haven't found a thing.

Any help at all would be greatly appreciated.

TIA

Bill Jennings
 
Old 10-21-2004, 02:02 AM   #2
TigerOC
Senior Member
 
Registered: Jan 2003
Location: Devon, UK
Distribution: Debian Etc/kernel 2.6.18-4K7
Posts: 2,380

Rep: Reputation: 49
Perhaps this article will help. You may have missed something like setting up users or groups.
 
Old 10-21-2004, 03:30 AM   #3
BillJennings
Member
 
Registered: Oct 2004
Location: Big River, California, USA
Distribution: Debian
Posts: 48

Original Poster
Rep: Reputation: 15
Thanks, but the article only covers getting the link started, which I am able to do. My problem is keeping it going for longer than 20 or 30 seconds. The windows box gets logged in and starts pinging the linux box. It gets responses for the first 12 or 15 pings, then it misses one or two, gets one or two, then it never gets any more until I disconnect and reconnect. Then it starts all over again.

Something is happening after 12 or 15 seconds that buggers up the ppp link. All subsequent packets sent by the linux box to the windows box are counted as errors by the windows box, and no further packets are recieved from the windows box by the linux box.

Everything is hunky dory for about 15 seconds though.

This is starting to piss me off...

Sincerely.

Bill Jennings
 
Old 10-21-2004, 03:42 PM   #4
BillJennings
Member
 
Registered: Oct 2004
Location: Big River, California, USA
Distribution: Debian
Posts: 48

Original Poster
Rep: Reputation: 15
I think I fixed it. I disabled asyncmap negotiation in /etc/ppp/options:

-am

Perhaps the interface on the linux box was left in "cooked" mode and the link worked until the windows box sent a ^S to the linux box, which took about 15 to 20 seconds to happen.

Well, thanks!

Sincerely
Bill Jennings
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
convert total no of seconds in the format hour minutes and seconds suchi_s Programming 15 03-15-2011 11:34 AM
Windows won't boot after playing around with Mandrake CD1 for only 30 Seconds! mooga Mandriva 5 06-06-2005 11:12 AM
nForce3 network dies after 30 seconds in mandrake 10 antken Linux - Networking 1 10-09-2004 07:53 PM
linux dialup faster and more stable than windows dialup -why? whitshade Linux - Networking 4 06-19-2004 03:52 PM
Sharing a Dialup Internet Connection between Redhat Linux 9 and Windows XP nitpil Linux - Networking 9 03-21-2004 11:43 AM


All times are GMT -5. The time now is 11:51 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration