Re: Problem with user-pppoe after upgrade, fixed
Hi, Let me make sure I've got things straight. You've upgraded to -stable and removed any ``set mtu'' or ``set mru'' lines that you've got in your ppp.conf. If this is the case, then I'm not sure what's happening. The only way I can reproduce what you're seeing in your log is if I add ``set mtu 1500'' to the configuration - which is incorrect (you can't force the link to have a 1500 byte mtu as it's physically invalid). > Ok. I ran some tests on the server, from here, and I of course fried my > connection. :) It's all back up now and I have the logs of the failure, > so... > > http://anarcat.dyndns.org/ftp/pub/FreeBSD/local/info/ppp.log > > Also censored, properly, this time. > > Neal (the -questions guy :) sent me this privately: > > <<-- > Looking at CVS for ppp, I noticed that the last change seemed to be > "MFC: Support stateful MPPE Insist on correct MRU negotiation during LCP > ...". I wonder if this would have anything to do with my problems? > -->> > > What do you think? > > a. -- Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]> http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Problem with user-pppoe after upgrade, fixed
Brian Somers wrote: > Hi, > > I said your ppp.conf was censored because you didn't attach it - you > just attached an error message that said it couldn't read it :*P LOL! ok.. I see. Darn mozilla. :) Ok, here goes a url, that should be fine: http://anarcat.dyndns.org/ftp/pub/FreeBSD/local_info/ppp.conf Also check the parent dir for dmesg. > The right fix is to simply remove these lines. Then a workaround is to change them to 1492. :) But ok, I'll kill the line. > What do your logs say when you enable LCP logging and the negotiation > fails ? I'm sorry, I forgot to check yesterday night. But we have another nice test case here that cross-posted -stable and -questions. :) I'll try to do it via remote and a nice script, but this is mad, I could really fsck up my connection here. Hmm... Let's be mad. ;) A. -- Antoine Beaupré Jambala TCM team Ericsson Canada inc. mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Problem with user-pppoe after upgrade, fixed
Hi, I said your ppp.conf was censored because you didn't attach it - you just attached an error message that said it couldn't read it :*P The right fix is to simply remove these lines. What do your logs say when you enable LCP logging and the negotiation fails ? > Brian Somers wrote: > > > Hi, > > > > I think your ppp.conf was a bit too censored. > > > Well the only thing I "censored" was my password/username lines and a > "set log" line I removed the same day. > > Apart from that, this is the ppp.conf that I use right now, and it works. > > > > If you're setting the MTU or MRU to 1500, this will now fail. > > > As seen in the logs? > > > The maximum these can be set to for PPPoE is 1492. > > > That's the physical ethernet limitation, right? > > > That's now enforced by the PPPoE ppp device as it knows the limitations > > > on the physical Ethernet. > > > Shouldn't ppp warn the user or panic instead of looping as it did for me? > > > > Just commenting out your setting of the MTU/MRU should solve your > > problems. > > > Actually, putting the set mtu/mru lines solved the problems. Should I > remove them altogether to remove future problems? :) > > Thank you very much. > > A. > > > -- > Antoine Beaupré > Jambala TCM team > Ericsson Canada inc. > mailto:[EMAIL PROTECTED] -- Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]> http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
