Date: Fri, 27 Jul 2001 12:24:24 +0100 From: Rasputin <rara.rasputin@virgin.net> To: stable@freebsd.org Cc: brian@freebsd.org Subject: Re: PPP still playing up? Message-ID: <20010727122423.A48668@shaft.techsupport.co.uk>
next in thread | raw e-mail | index | archive | help
>* Rasputin <rara.rasputin@virgin.net> [010725 10:31]: > >> Re: the issue with PPP falling over, I found (as others did) >> that replacing the line: >> >> set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 >> with >> set ifaddr 0.0.0.0/0 0.0.0.0/0 0.0.0.0 0.0.0.0 > ^^^^^^^^^ > ??? >> >> works >Ugh, ignore me. Brain dump. >I misread Neals' fix - will try setting only the server end to >0.0.0.0/0 when I get back to the box and take it from there.... Ok, for the record, I can now get online by making a few workarounds. If I set: set ifaddr 10.0.0.1/0 0.0.0.0/0 0.0.0.0 0.0.0.0 (I need an IP for the local side to use tun0) ppp -ddial isp but not ppp -auto isp (which refuses to accept the config without the remote side's IP being specified) I believe we need to change these settings due to IPCP and LCP being extra picky about the negotiation with the PPP server. Possibly related to chages in lcp.c and friends? ----------------------------------------------------- http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/ppp/lcp.c?only_with_tag=RELENG_4 Revision 1.81.2.6, Monday Jul 9 01:37:16 2001 UTC (2 weeks, 4 days ago) by brian Branch: RELENG_4 Changes since 1.81.2.5: +63 -18 lines MFC: Support stateful MPPE Insist on correct MRU negotiation during LCP Insist on correct IPADDR negotiation during IPCP ----------------------------------------------------- Since the '/0' on the end of the IPs is supposed to mean: "None of the bits in the preceding IP are significant" this looks like a bug to me - ppp should accept that the other end may end up being any IP and live with it, instead of repeatedly trying to negotiate. (in the past, the remote IP has remained 10.0.0.2 after connecting, with no side effects) I realise that from a standards point of view we are probably 'doing the right thing'; however, it sounds like I'm not the only one with an iffy ISP, and something as fundamentally important as a network connection should be more flexible in its negotiations IMHO. (It's difficult to roll back via cvsup when you can't get online :) ) That's my take on it, any comments? <<Logfiles showing the wierdness from the client side are available at: http://shaft.techsupport.co.uk/~rasputin/logs as before.>> -- Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010727122423.A48668>