Almost complete lockup of ppp with pre-2.0.30-2

Rene Hoejbjerg Larsen (renehl@post1.tele.dk)
9 Jun 1997 23:18:33 GMT

I just experienced an almost complete lockup of ppp networking with
pre-2.0.30-2. The link came up fine (except the first time when pppd
somehow failed to get the remote ip address), but the link was almost
dead. A few packages managed to get through, though, as some packets were
returned from ping, and ftp sessions were sometimes established. This
happened after four days of solid uptime. I tried reconnecting several
times, both with and without Van Jacobsen compression.

The reason I believe this to be a Linux problem (you could think it was an
ISP problem) is that netstat --inet -n gave some funny output:

Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.1:1274 127.0.0.1:1273 ESTABLISHED
tcp 0 0 127.0.0.1:1273 127.0.0.1:1274 ESTABLISHED
tcp 0 0 127.0.0.1:1276 127.0.0.1:1275 ESTABLISHED
tcp 0 0 127.0.0.1:1275 127.0.0.1:1276 ESTABLISHED
tcp 0 0 127.0.0.1:1330 127.0.0.1:1277 ESTABLISHED
tcp 0 0 127.0.0.1:1277 127.0.0.1:1330 ESTABLISHED
tcp 0 0 127.0.0.1:1332 127.0.0.1:1331 ESTABLISHED
tcp 0 0 127.0.0.1:1331 127.0.0.1:1332 ESTABLISHED
tcp 0 0 127.0.0.1:1334 127.0.0.1:1333 ESTABLISHED
tcp 0 0 127.0.0.1:1333 127.0.0.1:1334 ESTABLISHED
tcp 0 0 192.168.0.1:23 192.168.0.2:1027 ESTABLISHED
tcp 0 0 194.239.143.129:11355 128.2.196.124:80 ESTABLISHED
tcp 0 1 194.239.143.129:11712 193.162.153.172:80 FIN_WAIT1
tcp 0 0 194.239.143.188:12032 193.162.153.172:80 ESTABLISHED
tcp 696 1 194.239.143.188:12299 194.239.134.164:110 LAST_ACK
tcp 0 1 194.239.143.188:12331 193.162.153.172:80 FIN_WAIT1
tcp 0 1 194.239.143.188:12354 207.121.184.84:80 FIN_WAIT1
tcp 0 0 127.0.0.1:12379 127.0.0.1:119 ESTABLISHED
tcp 0 0 127.0.0.1:119 127.0.0.1:12379 ESTABLISHED
tcp 0 0 194.239.143.188:12402 193.162.153.172:80 ESTABLISHED
tcp 0 0 194.239.143.188:12404 137.92.14.2:80 ESTABLISHED
tcp 0 0 127.0.0.1:3128 127.0.0.1:12406 CLOSE_WAIT
tcp 0 0 127.0.0.1:3128 127.0.0.1:12432 CLOSE_WAIT
tcp 0 0 194.239.143.188:12439 193.162.153.172:80 ESTABLISHED
tcp 0 0 194.239.143.188:12463 193.162.153.172:80 ESTABLISHED
tcp 0 0 127.0.0.1:3128 127.0.0.1:12473 CLOSE_WAIT
tcp 0 0 194.239.143.188:12477 193.162.153.172:80 ESTABLISHED
tcp 0 1 194.239.143.188:12508 194.182.149.12:21 LAST_ACK
tcp 0 0 194.239.143.175:12528 128.2.196.124:80 ESTABLISHED
tcp 0 0 194.239.143.175:12609 130.225.51.30:21 FIN_WAIT2
tcp 0 0 194.239.143.175:12677 193.162.146.11:119 ESTABLISHED
tcp 0 0 194.239.143.175:12690 130.225.128.158:23 ESTABLISHED
tcp 0 0 127.0.0.1:12725 127.0.0.1:3128 FIN_WAIT2
tcp 0 0 127.0.0.1:3128 127.0.0.1:12725 CLOSE_WAIT
tcp 0 0 127.0.0.1:12731 127.0.0.1:3128 FIN_WAIT2
tcp 0 0 127.0.0.1:3128 127.0.0.1:12731 CLOSE_WAIT
tcp 0 0 194.239.143.175:12770 193.162.153.172:80 ESTABLISHED
tcp 0 0 194.239.143.175:12771 193.162.153.172:80 ESTABLISHED
tcp 1 0 127.0.0.1:12779 127.0.0.1:676 TIME_WAIT
tcp 0 0 194.239.143.175:12793 193.162.153.172:80 ESTABLISHED
tcp 0 0 194.239.143.175:12798 193.162.153.172:80 ESTABLISHED
tcp 0 0 194.239.143.175:12800 130.225.51.30:21 FIN_WAIT2
tcp 1 0 127.0.0.1:997 127.0.0.1:676 TIME_WAIT

I.e. a lot of connections in FIN_WAITX states. Besides, the connection
works fine now after a reboot (sigh).

The networking parts of .config are as follows:

#
# Networking options
#
CONFIG_FIREWALL=y
CONFIG_NET_ALIAS=y
CONFIG_INET=y
CONFIG_IP_FORWARD=y
CONFIG_IP_MULTICAST=y
CONFIG_SYN_COOKIES=y
CONFIG_RST_COOKIES=y
CONFIG_IP_FIREWALL=y
# CONFIG_IP_FIREWALL_VERBOSE is not set
CONFIG_IP_MASQUERADE=y

#
# Protocol-specific masquerading support will be built as modules.
#
CONFIG_IP_MASQUERADE_IPAUTOFW=y
CONFIG_IP_MASQUERADE_IPPORTFW=y
CONFIG_IP_MASQUERADE_ICMP=y
CONFIG_IP_TRANSPARENT_PROXY=y
CONFIG_IP_ALWAYS_DEFRAG=y
CONFIG_IP_ACCT=y
# CONFIG_IP_ROUTER is not set
# CONFIG_NET_IPIP is not set
# CONFIG_IP_MROUTE is not set
CONFIG_IP_ALIAS=y

#
# (it is safe to leave these untouched)
#
# CONFIG_INET_PCTCP is not set
# CONFIG_INET_RARP is not set
# CONFIG_NO_PATH_MTU_DISCOVERY is not set
CONFIG_IP_NOSR=y
CONFIG_SKB_LARGE=y

#
#
#
CONFIG_IPX=m
# CONFIG_IPX_INTERN is not set
# CONFIG_ATALK is not set
# CONFIG_AX25 is not set
# CONFIG_BRIDGE is not set
# CONFIG_NETLINK is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
# CONFIG_EQUALIZER is not set
# CONFIG_DLCI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=y

#
# CCP compressors for PPP are only built as modules.
#
# CONFIG_SLIP is not set
# CONFIG_NET_RADIO is not set
CONFIG_NET_ETHERNET=y
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
CONFIG_NET_ISA=y
# CONFIG_AT1700 is not set
# CONFIG_E2100 is not set
# CONFIG_DEPCA is not set
# CONFIG_EWRK3 is not set
# CONFIG_EEXPRESS is not set
# CONFIG_EEXPRESS_PRO is not set
# CONFIG_FMV18X is not set
# CONFIG_HPLAN_PLUS is not set
# CONFIG_HPLAN is not set
# CONFIG_HP100 is not set
# CONFIG_ETH16I is not set
CONFIG_NE2000=y
# CONFIG_NI52 is not set
# CONFIG_NI65 is not set
# CONFIG_SEEQ8005 is not set
# CONFIG_SK_G16 is not set
# CONFIG_NET_EISA is not set
# CONFIG_NET_POCKET is not set
# CONFIG_TR is not set
# CONFIG_FDDI is not set
# CONFIG_ARCNET is not set

I realize this is not much to go on, but my logs show NOTHING unusual. I
don't know if this is reproducable or not (I only installed the pre-patch
a week ago or so), but I thought you would like to know about this. Too
bad I didn't think about doing a tcpdump when this happened :-(

-- 
         /'"`\  zzzZ    | My PGP Public Key is available at:
        ( - - )         | <http://home1.inet.tele.dk/renehl/>
----oooO--(_)--Oooo------------------------------------------- 
   Math and alcohol don't mix: Do not drink and derive!