From owner-freebsd-current@FreeBSD.ORG Wed Sep 22 05:51:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 593EC16A4CE for ; Wed, 22 Sep 2004 05:51:06 +0000 (GMT) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id F08E243D41 for ; Wed, 22 Sep 2004 05:51:05 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (adsl-68-120-130-54.dsl.snfc21.pacbell.net [68.120.130.54])i8M5p6qM015980; Wed, 22 Sep 2004 01:51:06 -0400 Message-ID: <415112C6.80406@elischer.org> Date: Tue, 21 Sep 2004 22:51:02 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524 X-Accept-Language: en, hu MIME-Version: 1.0 To: ringworm@inbox.lv References: <200409202350.12931.ringworm@inbox.lv> <414FEBF8.8060308@elischer.org> <200409212233.58701.ringworm@inbox.lv> In-Reply-To: <200409212233.58701.ringworm@inbox.lv> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Cannot connect DSL with CURRENT ok with STABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2004 05:51:06 -0000 Michael C. Shultz wrote: >>Michael C. Shultz wrote: >> >>>Hello, >>> >>>I have a machine that dual boots in 4.10 STABLE or 6.0 CURENT. With >>>identical settings I cannot connect to Verizon DSL in CURRENT. Any >>>advice? Thankyou. Here are my sttings: >>> >>>ppp.conf: >>> >>>default: >>> set log Phase tun command >>> set ifaddr 10.0.0.1/0 10.0.0.2/0 >>> enable dns >>>verizon: >>> set device PPPoE:ed0 >>> set dial >>> set login >>> add default HISADDR >>> >>>rc.conf >>> >>>pppoed_enable="YES" # Run the PPP over Ethernet daemon. >>>pppoed_provider="verizon" # Provider and ppp(8) config file entry. >>>pppoed_flags="-P /var/run/pppoed.pid" # Flags to pppoed (if enabled). >>>pppoed_interface="ed0" # The interface that pppoed runs on. >>> >>>-Mike > > > On Tuesday 21 September 2004 01:53, Julian Elischer wrote: > >>output from tcpdump -i ed0 >>would be good for both successful and failing setups. >> > > OK, I posted them below. Note, I get the connection in STABLE > after running dhclient, in CURRENT dhclient hangs. While in current > when I compile then install dhclient from STABLE I connect no problem > so I think there is something wrong with dhclient in CURRENT. > > > good (from STABLE 4.10): > > root@~>tcpdump -i ed0 this shows NO pppoe packets > tcpdump: listening on ed0 > 21:57:14.105494 4.26.55.206.3201 > 4.26.230.108.loc-srv: S 27718824:27718824 > (0) win 64240 (DF) > 21:57:14.302237 201.133.233.89.3686 > 4.26.227.185.microsoft-ds: S > 3626197126:3626197126(0) win 64800 (DF) > 21:57:16.756732 4.26.85.219.1679 > 4.26.227.185.microsoft-ds: S > 1891626377:1891626377(0) win 16384 (DF) > 21:57:19.622700 4.7.41.253.3068 > 4.26.230.108.microsoft-ds: S > 3265755531:3265755531(0) win 16384 (DF) > 21:57:20.054668 201.133.233.89.3686 > 4.26.227.185.microsoft-ds: S > 3626197126:3626197126(0) win 64800 (DF) > 21:57:22.497887 4.7.41.253.3068 > 4.26.230.108.microsoft-ds: S > 3265755531:3265755531(0) win 16384 (DF) > 21:57:23.554664 4.26.87.108.4983 > 4.26.227.185.loc-srv: S > 3387494663:3387494663(0) win 16384 (DF) > 21:57:25.007299 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x1995be32 [| > bootp] [tos 0x10] > 21:57:25.504180 4.26.80.1.bootps > 4.26.86.117.bootpc: xid:0x1995be32 > Y:4.26.86.117 S:209.244.7.5 [|bootp] [tos 0x10] > 21:57:25.505318 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x1995be32 [| > bootp] [tos 0x10] > 21:57:25.587984 4.26.80.1.bootps > 4.26.86.117.bootpc: xid:0x1995be32 > Y:4.26.86.117 S:209.244.7.5 [|bootp] [tos 0x10] > 21:57:25.876082 arp who-has 4.26.86.117 tell 4.26.86.117 > 21:57:26.225701 arp who-has 4.26.80.1 tell 4.26.86.117 > 21:57:26.263556 arp reply 4.26.80.1 is-at 0:2:3b:1:16:2a > 21:57:26.263622 4.26.86.117.2437 > 207.69.188.187.domain: 6640+ PTR? > 117.86.26.4.in-addr.arpa. (42) > 21:57:26.307857 207.69.188.187.domain > 4.26.86.117.2437: 6640 NXDomain 0/1/0 > (115) (DF) > 21:57:26.405924 4.26.195.114.3103 > 4.26.86.117.loc-srv: S > 2693531866:2693531866(0) win 64240 (DF) > 21:57:27.208013 4.227.59.0.4081 > 4.26.86.117.microsoft-ds: S > 902967275:902967275(0) win 8760 (DF) > 21:57:28.978723 4.26.114.100.3552 > 4.26.230.108.microsoft-ds: S > 4159777173:4159777173(0) win 64240 (DF) > 21:57:30.127360 4.227.59.0.4081 > 4.26.86.117.microsoft-ds: S > 902967275:902967275(0) win 8760 (DF) > 21:57:30.787547 4.26.82.255.2823 > 4.26.227.185.loc-srv: S 356500099:356500099 > (0) win 16384 (DF) > > bad from (CURRENT 6.0) > this shows teh pppoe server just is not responding.. there are PADI packets and no PADO packets > root@~>tcpdump -i ed0 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on ed0, link-type EN10MB (Ethernet), capture size 96 bytes > 22:04:22.294573 IP 4.26.84.39.4597 > 4.26.86.117.loc-srv: S > 1562494193:1562494193(0) win 64240 > 22:04:23.360243 IP 4.26.147.187.4201 > 4.26.230.108.loc-srv: S > 1406724163:1406724163(0) win 16384 > 22:04:23.508565 PPPoE PADI [Host-Uniq 0x008900C1] > 22:04:23.543132 arp who-has 4.26.227.185 tell 4.26.224.1 > 22:04:25.507208 PPPoE PADI [Host-Uniq 0x008900C1] > 22:04:25.695178 arp who-has 4.26.227.185 tell 4.26.224.1 > 22:04:26.382926 IP 208.63.124.4.45664 > 4.26.230.108.microsoft-ds: S > 1894493832:1894493832(0) win 64240 > 22:04:26.699809 arp who-has 4.26.227.185 tell 4.26.224.1 > 22:04:27.697964 arp who-has 4.26.227.185 tell 4.26.224.1 > 22:04:29.568670 PPPoE PADI [Host-Uniq 0xC0380DC1] > 22:04:31.567295 PPPoE PADI [Host-Uniq 0xC0380DC1] > 22:04:33.762123 IP 65.61.101.16.4721 > 4.26.230.108.microsoft-ds: S > 1446633888:1446633888(0) win 8760 > 22:04:35.026550 IP 24.88.36.229.4597 > 4.26.230.108.microsoft-ds: S > 439167034:439167034(0) win 64240 > 22:04:35.643907 PPPoE PADI [Host-Uniq 0x403A0DC1] > 22:04:37.501279 IP 202.178.156.50.3568 > 4.26.86.117.microsoft-ds: S > 2126185622:2126185622(0) win 64240 > 22:04:37.637362 PPPoE PADI [Host-Uniq 0x403A0DC1] > 22:04:37.793436 IP 24.88.36.229.4597 > 4.26.230.108.microsoft-ds: S > 439167034:439167034(0) win 64240 > 22:04:40.134584 IP 4.26.245.133.miteksys-lm > 4.26.86.117.microsoft-ds: S > 4043206572:4043206572(0) win 64240 > 22:04:40.422860 IP 202.178.156.50.3568 > 4.26.86.117.microsoft-ds: S > 2126185622:2126185622(0) win 64240 > 22:04:41.699575 PPPoE PADI [Host-Uniq 0xC07BF8C0] > 22:04:43.697447 PPPoE PADI [Host-Uniq 0xC07BF8C0] > 22:04:46.467407 IP 202.178.156.50.3568 > 4.26.86.117.microsoft-ds: S > 2126185622:2126185622(0) win 64240 > 22:04:47.758880 PPPoE PADI [Host-Uniq 0xC08A00C1] > 22:04:49.757508 PPPoE PADI [Host-Uniq 0xC08A00C1] > 22:04:50.775977 IP 4.26.244.249.4115 > 4.26.230.108.loc-srv: S > 3339430298:3339430298(0) win 64240 > 22:04:51.428577 IP 4.26.242.71.4097 > 4.26.230.108.microsoft-ds: S > 1605743494:1605743494(0) win 64240 > 22:04:53.614146 IP 4.26.244.249.4115 > 4.26.230.108.loc-srv: S > 3339430298:3339430298(0) win 64240 > 22:04:53.818990 PPPoE PADI [Host-Uniq 0xC05943C1] > 22:04:54.340078 IP 4.26.242.71.4097 > 4.26.230.108.microsoft-ds: S > 1605743494:1605743494(0) win 64240 > 22:04:55.817588 PPPoE PADI [Host-Uniq 0xC05943C1] > 22:04:58.970800 IP 4.26.223.210.sophia-lm > 4.26.86.117.loc-srv: S > 3411251725:3411251725(0) win 64240 > 22:04:59.879010 PPPoE PADI [Host-Uniq 0x805343C1] > 22:05:01.877670 PPPoE PADI [Host-Uniq 0x805343C1] > 22:05:02.015564 IP 24.94.26.145.1981 > 4.26.86.117.microsoft-ds: S > 3060340817:3060340817(0) win 16384 > 22:05:03.845120 IP 81.37.215.133.2075 > 4.26.86.117.microsoft-ds: S > 3738125076:3738125076(0) win 16384 > 22:05:04.990806 IP 24.94.26.145.1981 > 4.26.86.117.microsoft-ds: S > 3060340817:3060340817(0) win 16384 > 22:05:05.232482 IP 4.26.143.242.4227 > 4.26.86.117.loc-srv: S > 4121653173:4121653173(0) win 64240 > 22:05:05.271587 IP 4.26.55.206.2437 > 4.26.230.108.loc-srv: S > 4033941466:4033941466(0) win 64240 > 22:05:05.590780 IP 4.26.127.89.4706 > 4.26.86.117.microsoft-ds: S > 763631196:763631196(0) win 16384 > 22:05:05.939134 PPPoE PADI [Host-Uniq 0x005D43C1] > 22:05:06.763665 IP 4.26.86.119.4085 > 4.26.86.117.microsoft-ds: S > 815576764:815576764(0) win 64240 > 22:05:06.765656 IP 4.26.86.119.4086 > 4.26.86.117.ms-sql-s: S > 815627672:815627672(0) win 64240 > 22:05:07.127080 IP 4.26.23.70.4910 > 4.26.230.108.loc-srv: S > 3943823469:3943823469(0) win 16384 > 22:05:07.628628 IP 201.133.117.183.3097 > 4.26.86.117.microsoft-ds: S > 1119685365:1119685365(0) win 64800 > 22:05:07.937755 PPPoE PADI [Host-Uniq 0x005D43C1] > 22:05:07.997047 IP 4.26.143.242.4227 > 4.26.86.117.loc-srv: S > 4121653173:4121653173(0) win 64240 > 22:05:08.339031 IP 4.26.127.89.4706 > 4.26.86.117.microsoft-ds: S > 763631196:763631196(0) win 16384 > ^C > 47 packets captured > 47 packets received by filter > 0 packets dropped by kernel