-
Notifications
You must be signed in to change notification settings - Fork 321
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
Fix "Peer refused to agree to our IP address" #1021
Fix "Peer refused to agree to our IP address" #1021
Conversation
I do not understand ipcp-accept-local would be required or have any effect here: With this option, pppd will accept the peer's idea of our local IP address, even if the local IP address was specified in an option. Indeed, we do not specify the local IP address: ":169.254.2.1", // <local_IP_address>:<remote_IP_address> Instead, we explicitly ask the peer to provide the local IP address, using option noipdefault: With this option, the peer will have to supply the local IP address during IPCP negotiation (unless it specified explicitly on the command line or in an options file). It seems to be working in practice. So let's test it.
I guess it might help when a local IP address is defined in |
I am observing this with openfortivpn 1.20.3 in NixOS and pppd 2.5.0. Is that a combination that should work? |
Doesn't it work? |
No, unfortunately it doesn't |
Well, what's the problem, and does this new patch fix the problem? |
Oh, my bad, for some reason I assumed that 1.10.3 contained all patches already! Will try |
Indeed, on master it works for me as well! |
I have fixed it #1076 (comment) |
I do not understand why
ipcp-accept-local
would be required or have any effect here:Indeed, we do not specify the local IP address:
Instead, we explicitly ask the peer to provide the local IP address, using option
noipdefault
:It seems to be working in practice. So let's test it.
Fixes #920.