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

Peer refused to agree to his IP address #194

Closed
jgui1014 opened this issue Sep 11, 2023 · 3 comments · Fixed by #195
Closed

Peer refused to agree to his IP address #194

jgui1014 opened this issue Sep 11, 2023 · 3 comments · Fixed by #195

Comments

@jgui1014
Copy link

Hi.

I've been using openfortigui for some time now, but after updating my Arch box, all connection attempts fail with: Peer refused to agree to his IP address.

Before update:

Aug 21 16:06:50 Hangup (SIGHUP)
Modem hangup
Connect time 6.5 minutes.
Sent 711160 bytes, received 4568390 bytes.
Connection terminated.
Aug 30 21:00:37 INFO: Start tunnel.
Aug 30 21:00:44 INFO: Connected to gateway.
INFO: Authenticated.
Aug 30 21:00:45 INFO: Remote gateway has allocated a VPN.
Aug 30 21:00:45 Using interface ppp0
Connect: ppp0 <--> /dev/pts/5
Aug 30 21:00:45 INFO: Got addresses: [10.212.134.200], ns [0.0.0.0, 0.0.0.0]
INFO: Negotiation complete.
Aug 30 21:00:48 INFO: Got addresses: [10.212.134.200], ns [0.0.0.0, 0.0.0.0]
INFO: Negotiation complete.
Aug 30 21:00:51 INFO: Got addresses: [10.212.134.200], ns [0.0.0.0, 0.0.0.0]
INFO: Negotiation complete.
Aug 30 21:00:52 INFO: Negotiation complete.
Cannot determine ethernet address for proxy ARP
local IP address 10.212.134.200
remote IP address 169.254.2.1
INFO: Interface ppp0 is UP.
INFO: Setting new routes...
INFO: Adding VPN nameservers...
INFO: Tunnel is up and running.
Aug 30 21:02:43 INFO: Setting ppp0 interface down.
INFO: Restoring routes...
INFO: Removing VPN nameservers...
Aug 30 21:02:45 Hangup (SIGHUP)
Modem hangup
Connect time 1.9 minutes.
Sent 540297 bytes, received 4152445 bytes.
Connection terminated.

Today:

Sep 11 13:22:26 INFO: Start tunnel.
Sep 11 13:22:34 INFO: Connected to gateway.
INFO: Authenticated.
Sep 11 13:22:34 INFO: Remote gateway has allocated a VPN.
Sep 11 13:22:34 Warning: couldn't open ppp database /run/pppd/pppd2.tdb
Using interface ppp0
Connect: ppp0 <--> /dev/pts/4
Sep 11 13:22:35 INFO: Got addresses: [10.212.134.200], ns [0.0.0.0, 0.0.0.0]
INFO: Negotiation complete.
Sep 11 13:22:38 INFO: Got addresses: [10.212.134.200], ns [0.0.0.0, 0.0.0.0]
INFO: Negotiation complete.
Sep 11 13:22:41 INFO: Got addresses: [10.212.134.200], ns [0.0.0.0, 0.0.0.0]
INFO: Negotiation complete.
Sep 11 13:22:43 INFO: Negotiation complete.
Peer refused to agree to his IP address
Connect time 0.2 minutes.
Sent 1125 bytes, received 1090 bytes.

Thanks!

@lgaggini
Copy link

Hi,

very likely it's related to the ppp upgrade to the version 2.5.0. You can check this issue on openfortivpn: adrienverge/openfortivpn#1076 on which openfortigui is built on.

@gamelaster
Copy link

Hi, yes, it's because of that option. It would be great if we can configure this in OpenFortiGUI

@petrkr
Copy link
Contributor

petrkr commented Nov 9, 2023

Just got same problem today.. New openfortivpn have cmd line param for it "--pppd-accept-remote"

Would be nice to add this option to "pppd" section too

  --pppd-accept-remote          Invoke pppd with option 'ipcp-accept-remote'.                                It might help avoid errors with PPP 2.5.0.

petrkr added a commit to petrkr/openfortigui that referenced this issue Nov 9, 2023
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

Successfully merging a pull request may close this issue.

4 participants