headers
Johannes Jakob | 1 Dec 10:24

Re: [PATCH] Re: [Openl2tp-users] OpenL2TP, multilink, ppp[PID] and bundle status monitoring


Hi Ben!

Hi Lists,

On Mon, 30 Nov 2009 10:47:27 +0000 (GMT), Ben McKeegan

<ben <at> netservers.co.uk> wrote:

> On Fri, 27 Nov 2009, Johannes Jakob wrote:

> 

>> With multilink disabled, radattr works fine and creates

>> /var/run/radattr.ppp0:

>>

>> RADATTR plugin wrote 8 line(s) to file /var/run/radattr.ppp0.

>>

>> but with enabled multilink it doesn't:

>>

>> rc_map2id: can't find tty /dev/ in map database

>> RADATTR plugin wrote 8 line(s) to file /var/run/radattr..
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ben McKeegan | 1 Dec 12:00
Picon
Favicon

Re: [PATCH] Re: [Openl2tp-users] OpenL2TP, multilink, ppp[PID] and bundle status monitoring

Johannes Jakob wrote:
> 
> Thank you very much for your patch! It is working absolutely great and as I
> hoped it would (pppd-2.4.5)!
> 
> As I think you might have had other similar problems we have, what are your
> experiences with openl2tp for dialin users in a large scale? Are there
> problems still unsolved?
> 

We've run into various multilink related kernel bugs (not openl2tp 
specific).  I've submitted patches upstream.  One fixes lost fragments 
and has been included upstream as of 2.6.31.   The other fixes quite a 
nasty kernel BUG (panic) and will be in 2.6.32.

> 
> Currently I'm having trouble monitoring mlppp bundles. Is there any
> reasonable and reliable way to check how many ppp links are in a bundle and
> if they are up and running?

We've written our own LNS management application that gathers all this 
data together.   It reads /var/run/pppd2.tdb to learn about active 
connections and the links that make them up, talks to openl2tpd via the 
RPC interface to learn how these relate to L2TP sessions and gather L2TP 
bandwidth stats for them, and uses libpcap to monitor the L2TP 
encapsulated LCP packets which it uses to provide a continual log of 
latency and packet loss.

> Because of it's nature, there aren't any pid files in /var/run/ except for
> the bundle, ip, ifconfig and netstat aren't of any help, too.  Is there any
(Continue reading)

Permalink | Reply | 0 comments |
headers
Diederik Hattingh | 4 Dec 09:35
Picon

Fwd: VPN to windows ISA server

On Mon, Nov 30, 2009 at 1:10 AM, James Carlson <carlsonj <at> workingcode.com> wrote:
> Diederik Hattingh wrote:
>> Nov 29 14:29:35 [pppd] sent [LCP ConfAck id=0x2 <asyncmap 0x0> <magic
>> 0x15190f75> <accomp>]
>
> It looks like you've trimmed away the beginning of the negotiation in
> the debug information you posted.  That's unfortunate, as this likely
> includes important details that will be needed to resolve the problem.
>
> In the future, don't do that.

Oops, sorry.

>
>> I read online that the NT Domain part must be left blank, but the
>> domain added as prefix, as described above, to the username.  Is this
>> still valid?
>
> It depends on how the NT server is configured.  There's no way to know
> without asking the administrator of that system.

Our system administrator  informed me, and from what I have read
online, it must always be "myworkdomain\username"  I specified the
domain separately, and also the username as mentioned before.

>
>> # Secrets for authentication using CHAP
>> # client        server  secret                  IP addresses
>> myworkdomain\\djh       myworkdomain    *****
>> myworkdomain    myworkdomain\\djh       *****
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jelle de Jong | 21 Dec 14:15
Picon

pppoe uplink goes down several times a day, what is wrong

Hello everybody,

I got a PPPoE uplink to a big Dutch internet service provider, and I
am having stability issues. My uplink is going down for very short
times but it happens several times a day.

I just had major network move and the physical copper line changed so
I think I can rule out bad coper connections now. I had the same
issues on the old location though.

The modem I use is a DrayTek Vigor 3100V (latest firmware) in PPPoE
bridge mode (1) it behaves complete transparent, so I let the Linux
server do as much as possible.

I am wondering what I am doing wrong, is there something I should
change on the software side? Should I change the modem configuration?
Stop using PPPoE?

Please see the attachment for the configuration and debug information.

1) http://imagebin.ca/img/aSt5Wc-c.png

Any help is appreciated,

Best regards,

Jelle


(Continue reading)






Permalink
| Reply
| 3 comments  
| 



  

  

  





headers


James Carlson
 | 
21 Dec 14:49





Re: pppoe uplink goes down several times a day, what is wrong


Jelle de Jong wrote:
> I am wondering what I am doing wrong, is there something I should
> change on the software side? Should I change the modem configuration?
> Stop using PPPoE?

Your debug log shows the following:

Dec 21 06:37:54 sammy pppd[2954]: primary   DNS address 213.75.63.36
Dec 21 06:37:54 sammy pppd[2954]: secondary DNS address 213.75.63.70
Dec 21 08:32:56 sammy pppd[2954]: No response to 4 echo-requests
Dec 21 08:32:56 sammy pppd[2954]: Serial link appears to be disconnected.
Dec 21 08:32:56 sammy pppd[2954]: Connect time 115.1 minutes.

That indicates that your link was up and working for almost two hours,
and then was torn down because the ISP's server suddenly stopped
responding to LCP Echo-Request messages from your system.

If it happens this way every time, then I would suspect that your ISP
may have set a time limit on connections.  Some ISPs are known for doing
such things, especially those that have a dial-up background.  They view
their service as being "on-demand" and thus an always-connected client
is one that's abusing the terms of service.  (That having everyone
connected all the time costs no more than having them connect on demand
doesn't seem to factor into those calculations.  There's no technical
accounting for business rules ...)

If it seems to be "random" rather than a fixed interval, then that's
probably not the problem.  It's possible that the ISP's server is
crashing occasionally or that it's experiencing some sort of
communications problem or that the path between you and that server (the

(Continue reading)






Permalink
| Reply
| 2 comments  
| 



  

  

  





headers


Jelle de Jong
 | 
21 Dec 15:25






Picon





Re: pppoe uplink goes down several times a day, what is wrong


Hi James,

Thank you for taking the time to look at my problems.

James Carlson wrote, on 21-12-09 14:49:
> Jelle de Jong wrote:
>> I am wondering what I am doing wrong, is there something I should
>> change on the software side? Should I change the modem configuration?
>> Stop using PPPoE?
> 
> Your debug log shows the following:
> 
> Dec 21 06:37:54 sammy pppd[2954]: primary   DNS address 213.75.63.36
> Dec 21 06:37:54 sammy pppd[2954]: secondary DNS address 213.75.63.70
> Dec 21 08:32:56 sammy pppd[2954]: No response to 4 echo-requests
> Dec 21 08:32:56 sammy pppd[2954]: Serial link appears to be disconnected.
> Dec 21 08:32:56 sammy pppd[2954]: Connect time 115.1 minutes.
> 
> That indicates that your link was up and working for almost two hours,
> and then was torn down because the ISP's server suddenly stopped
> responding to LCP Echo-Request messages from your system.
> 
> If it happens this way every time, then I would suspect that your ISP
> may have set a time limit on connections.  Some ISPs are known for doing
> such things, especially those that have a dial-up background.  They view
> their service as being "on-demand" and thus an always-connected client
> is one that's abusing the terms of service.  (That having everyone
> connected all the time costs no more than having them connect on demand
> doesn't seem to factor into those calculations.  There's no technical
> accounting for business rules ...)

(Continue reading)






Permalink
| Reply
| 1 comment  
| 



  

  

  





headers


James Carlson
 | 
21 Dec 15:51





Re: pppoe uplink goes down several times a day, what is wrong


Jelle de Jong wrote:
>> If it happens this way every time, then I would suspect that your ISP
>> may have set a time limit on connections.  Some ISPs are known for doing
>> such things, especially those that have a dial-up background.  They view
>> their service as being "on-demand" and thus an always-connected client
>> is one that's abusing the terms of service.  (That having everyone
>> connected all the time costs no more than having them connect on demand
>> doesn't seem to factor into those calculations.  There's no technical
>> accounting for business rules ...)
> 
> The disconnection interval seems random, as you can see the logs
> showed two disconnects this day.
> 
> # grep -i pppd /var/log/syslog | grep -i time
> Dec 21 06:37:24 sammy pppd[2954]: Connect time 2681.4 minutes.
> Dec 21 08:32:56 sammy pppd[2954]: Connect time 115.1 minutes.
> 
> The connection is a G.SHDSL 2048:2048 1:1 business connection very
> expensive by the biggest ISP in our country (not saying the ISP is
> good) I don't think they have a connection time limit?

OK; that certainly narrows things down.

>> If it seems to be "random" rather than a fixed interval, then that's
>> probably not the problem.  It's possible that the ISP's server is
>> crashing occasionally or that it's experiencing some sort of
>> communications problem or that the path between you and that server (the
>> ATM network) is itself unreliable.  The key information that's needed to
>> identify such a problem would be on the ISP's systems (or may need some
>> investigation and analysis).

(Continue reading)






Permalink
| Reply
| 0 comments  
| 



  

  

  

  


  





    



Gmane