Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question about CONFIG_WATCHDOG_FIREWALL conditional compilation #193

Open
guerinp38 opened this issue Mar 25, 2020 · 0 comments
Open

Question about CONFIG_WATCHDOG_FIREWALL conditional compilation #193

guerinp38 opened this issue Mar 25, 2020 · 0 comments

Comments

@guerinp38
Copy link

Hello,
Currently xl2tpd fails to connect with current releases in Debian 9 and 10 with "out of order control packet on tunnel xx".
So the fix is working well...
But is this really the best way to fix it ?
I took a look at the RFC 2661 (pages 32 and 33) and it's said :

(Tx) Connect Speed (ICCN, OCCN)
...
When the optional Rx Connect Speed AVP is present, the value in
this AVP represents the transmit connect speed, from the
perspective of the LAC (e.g. data flowing from the LAC to the
remote system). When the optional Rx Connect Speed AVP is NOT
present, the connection speed between the remote system and LAC is
assumed to be symmetric and is represented by the single value in
this AVP.

Rx Connect Speed (ICCN, OCCN)
...
Presence of this AVP implies that the connection speed may be
asymmetric with respect to the transmit connect speed given in the
(Tx) Connect Speed AVP.

In fact, when the txspped and rxspeed values are equal, is it necesssary to set the rx AVP value ?

Kind regards,
Patrice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant