I have an old system currently running as an LNS and taking connections reasonably well.
I am now trying to get a newer faster system up and running to replace the older one and I am having no end of problems. From what I can see it looks like there is a problem with the connection control state machine.
My first question is.
1) has anybody actually used the l2tpd as the LNS component of a service provider type application?
2) Are there any known problems with the dropping and regaining sync with a tunnel?
Alvin.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I do know that people have posted...in the mailing list (l2tpd-devel) I believe...that they have been using l2tpd as an LNS...though I'm not sure what sort of application space they were working in though...whether it was a service provider type of application or something else.
I would not be surprised if there were a problem with the connection control state machine...well...l2tpd doesn't really use a state machine type of setup in the code so its kind of kludgey to begin with.
I'm not sure what you're referring to with "dropping and regaining sync with a tunnel".
Is it dropping a control connection packet and then never getting caught back up with sequence numbers or something? I can certainly believe that...and think there may even be comments in the code indicating that I thought there might be a problem with it but didn't have a test case for it. :)
Can you reproduce errors that your seeing with it and cut-n-paste them, either here or on the mailing list. I'm certainly willing (and wanting) to help out and find whatever is broken in this code, but don't have all that many permutations of setups that I can test here locally so I have to depend on the willingness of others (such as yourself) to be remote eyes and ears (such as it is) for setups that I can't reproduce locally.
Jeff
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We have a link up and running between an LAC and our LNS. The tunnel is dropped for some reason.
The server does not seem to resync.
I have a bunch of ethereal snapshots and debug logs but I am not nearly farmilar enough with the software to do any real debugging.
I would really appreciate any help.
I will be leaving for holidays at the end of this week and hope to have this up and running cleanly by then.
My email address is alvin@iplink.net It will be much easier than talking through the list.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have an old system currently running as an LNS and taking connections reasonably well.
I am now trying to get a newer faster system up and running to replace the older one and I am having no end of problems. From what I can see it looks like there is a problem with the connection control state machine.
My first question is.
1) has anybody actually used the l2tpd as the LNS component of a service provider type application?
2) Are there any known problems with the dropping and regaining sync with a tunnel?
Alvin.
I do know that people have posted...in the mailing list (l2tpd-devel) I believe...that they have been using l2tpd as an LNS...though I'm not sure what sort of application space they were working in though...whether it was a service provider type of application or something else.
I would not be surprised if there were a problem with the connection control state machine...well...l2tpd doesn't really use a state machine type of setup in the code so its kind of kludgey to begin with.
I'm not sure what you're referring to with "dropping and regaining sync with a tunnel".
Is it dropping a control connection packet and then never getting caught back up with sequence numbers or something? I can certainly believe that...and think there may even be comments in the code indicating that I thought there might be a problem with it but didn't have a test case for it. :)
Can you reproduce errors that your seeing with it and cut-n-paste them, either here or on the mailing list. I'm certainly willing (and wanting) to help out and find whatever is broken in this code, but don't have all that many permutations of setups that I can test here locally so I have to depend on the willingness of others (such as yourself) to be remote eyes and ears (such as it is) for setups that I can't reproduce locally.
Jeff
Ho boy where to start.
Here is the sequence of events
We have a link up and running between an LAC and our LNS. The tunnel is dropped for some reason.
The server does not seem to resync.
I have a bunch of ethereal snapshots and debug logs but I am not nearly farmilar enough with the software to do any real debugging.
I would really appreciate any help.
I will be leaving for holidays at the end of this week and hope to have this up and running cleanly by then.
My email address is alvin@iplink.net It will be much easier than talking through the list.