[ previous ] [ next ] [ threads ]
 
 From:  "Holger Bauer" <Holger dot Bauer at citec dash ag dot de>
 To:  "Manuel Kasper" <mk at neon1 dot net>
 Cc:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  AW: AW: [m0n0wall] Second total freeze of 1.2b3
 Date:  Mon, 21 Feb 2005 18:34:50 +0100
Here are some logs concerning the pppoe-problem, I only had the netgear dg632b here for testing 


Netgear DG632B in plain Modem-Mode, Sync on WAN:

Jan 1 00:06:23 	mpd: [pppoe] device: OPEN event in state DOWN
Jan 1 00:06:23 	mpd: [pppoe] pausing 2 seconds before open
Jan 1 00:06:23 	mpd: [pppoe] device is now in state DOWN
Jan 1 00:06:25 	mpd: [pppoe] device: OPEN event in state DOWN
Jan 1 00:06:25 	mpd: [pppoe] device is now in state OPENING
Jan 1 00:06:34 	mpd: [pppoe] PPPoE connection timeout after 9 seconds
Jan 1 00:06:34 	mpd: [pppoe] device: DOWN event in state OPENING
Jan 1 00:06:34 	mpd: [pppoe] device is now in state DOWN
Jan 1 00:06:34 	mpd: [pppoe] link: DOWN event
Jan 1 00:06:34 	mpd: [pppoe] LCP: Down event
Jan 1 00:06:34 	mpd: [pppoe] device: OPEN event in state DOWN
Jan 1 00:06:34 	mpd: [pppoe] pausing 4 seconds before open
Jan 1 00:06:34 	mpd: [pppoe] device is now in state DOWN
Jan 1 00:06:38 	mpd: [pppoe] device: OPEN event in state DOWN
Jan 1 00:06:38 	mpd: [pppoe] pausing 2 seconds before open
Jan 1 00:06:38 	mpd: [pppoe] device is now in state DOWN
Jan 1 00:06:40 	mpd: [pppoe] device: OPEN event in state DOWN
Jan 1 00:06:40 	mpd: [pppoe] device is now in state OPENING
Jan 1 00:06:49 	mpd: [pppoe] PPPoE connection timeout after 9 seconds
Jan 1 00:06:49 	mpd: [pppoe] device: DOWN event in state OPENING
Jan 1 00:06:49 	mpd: [pppoe] device is now in state DOWN
Jan 1 00:06:49 	mpd: [pppoe] link: DOWN event
Jan 1 00:06:49 	mpd: [pppoe] LCP: Down event
Jan 1 00:06:49 	mpd: [pppoe] device: OPEN event in state DOWN
Jan 1 00:06:49 	mpd: [pppoe] pausing 4 seconds before open
Jan 1 00:06:49 	mpd: [pppoe] device is now in state DOWN
Jan 1 00:06:53 	mpd: [pppoe] device: OPEN event in state DOWN
Jan 1 00:06:53 	mpd: [pppoe] pausing 2 seconds before open
Jan 1 00:06:53 	mpd: [pppoe] device is now in state DOWN
Jan 1 00:06:55 	mpd: [pppoe] device: OPEN event in state DOWN
Jan 1 00:06:55 	mpd: [pppoe] device is now in state OPENING
Jan 1 00:06:59 	mpd: [pppoe] rec'd signal usr1, opening
Jan 1 00:06:59 	mpd: [pppoe] IPCP: Open event
Jan 1 00:06:59 	mpd: [pppoe] bundle: OPEN event in state OPENED
Jan 1 00:06:59 	mpd: [pppoe] opening link "pppoe"...
Jan 1 00:06:59 	mpd: [pppoe] link: OPEN event
Jan 1 00:06:59 	mpd: [pppoe] LCP: Open event
Jan 1 00:07:04 	mpd: [pppoe] PPPoE connection timeout after 9 seconds
Jan 1 00:07:04 	mpd: [pppoe] device: DOWN event in state OPENING
Jan 1 00:07:04 	mpd: [pppoe] device is now in state DOWN
Jan 1 00:07:04 	mpd: [pppoe] link: DOWN event
Jan 1 00:07:04 	mpd: [pppoe] LCP: Down event
Jan 1 00:07:04 	mpd: [pppoe] device: OPEN event in state DOWN
Jan 1 00:07:04 	mpd: [pppoe] pausing 4 seconds before open
Jan 1 00:07:04 	mpd: [pppoe] device is now in state DOWN
Jan 1 00:07:08 	mpd: [pppoe] device: OPEN event in state DOWN
Jan 1 00:07:08 	mpd: [pppoe] pausing 1 seconds before open
Jan 1 00:07:08 	mpd: [pppoe] device is now in state DOWN
Jan 1 00:07:09 	mpd: [pppoe] device: OPEN event in state DOWN
Jan 1 00:07:09 	mpd: [pppoe] device is now in state OPENING

Setting the parameter only made a modem that was connecting before to show the same behavior.
I should have made a list of all the modems I found out not to work, but the netgear would be 
a good start to find a solution for the problem as others behave in the same way. The only 
difference I see with some modems is, that you sometimes see the name of the server you want 
to connect to and after that the connection times out. The same modem works on the same 
WAN-connection when used by another router or the windows xp pppoe-driver for example.
Very strange....


workaround, hopefully I find some time tomorrow.

Thanks for the help and fur the great product!

Regards
Holger Bauer




Von: Manuel Kasper [mailto:mk at neon1 dot net]
Gesendet: Montag, 21. Februar 2005 16:17
An: Holger Bauer
Cc: m0n0wall at lists dot m0n0 dot ch
Betreff: Re: AW: [m0n0wall] Second total freeze of 1.2b3


On 21.02.2005 13:30 +0100, Holger Bauer wrote:

> All my WRAPS with 1.2b3 work stable so far, only thing is, that

> 
> m0n0 with fixed IP ---- m0n0 with dynamic IP
> 
> everything is configured right and the tunnel comes up the first


> "Save" on the IPSEC-settingpage of the dynamic m0n0 without
> changing anything. I reported this behavior before, but nobody
> cared about it. :-( Going back to 1.11 works rockstable.

The only major changes (as far as IPsec is concerned) are the kernel
fix to prefer newer SAs over older ones, and the fact that
proposal_check in racoon.conf is now set to "claim" instead of
"obey". Try turning off the kernel hack using

sysctl -w net.key.preferred_oldsa=1

in /exec.php after it has booted (this change is lost on reboot, when
you apply/save new IPsec settings or when your WAN IP address
changes).

> Another thing I found out is that there are problems with newer
> dsl-modems and m0n0s pppoe. I can provide logs, if you need them,
> but it seems that the link up request times out although the
> servername of the distant server can be seen. This happens with
> more than one specific vendor (for example the new netgear modem
> DG632B, products from t-com, ....) I am very unhappy about that, as
> the problem seems to appear with nearly every new modem I get to
> test. I tested different providers and also have different
> connections to test on. The same modems work with other products on
> the same wanconnection. This happens also with 1.11.

Huh? This is the first time that I hear of this issue. The latest
modems that I've used with m0n0wall are ZyXEL 623MEs. But yes, please
do send me the logs. There aren't many parameters to PPPoE; FreeBSD's
ng_pppoe has a sysctl variable to control interoperation with "broken
PPPoE implementations":

sysctl -w net.graph.nonstandard_pppoe=1

and after that click "Save" on the WAN setup page again. I doubt that
it's the solution as you probably wouldn't be seeing the remote
server name if that was the problem, but maybe it's still worth a try.

If anyone has an ADSL modem with this issue and would be willing to
lend it to me for testing, please contact me (Annex B ADSL line
available here).

- Manuel


____________
Virus checked by G DATA AntiVirusKit
Version: AVK 15.0.2868 from 04.02.2005
Virus news: www.antiviruslab.com

____________
Virus checked by G DATA AntiVirusKit