Peer refused to agree to our IP address and connection is terminated #1076

wmasilva · 2023-03-09T16:19:10Z

Hi,

I'm having the same issue as #920, sometimes i got "Peer refused to agree to our IP address".

I'm using the version 1.20.1, on debian bullseye.
the file /etc/ppp/options is the original one.

Here is the log when it happens:


DEBUG:  Got Address: 172.16.245.16
DEBUG:  if_config: not ready yet...
DEBUG:  gateway ---> pppd (16 bytes)
gtw:    80 21 01 66 00 0e 01 0a 2e 19 f2 5b ac 10 f5 10

DEBUG:  pppd ---> gateway (16 bytes)
pppd:   80 21 04 66 00 0e 01 0a 2e 19 f2 5b ac 10 f5 10

DEBUG:  pppd ---> gateway (16 bytes)
pppd:   80 21 01 03 00 0e 01 0a ac 10 f5 10 a9 fe 02 01

DEBUG:  gateway ---> pppd (6 bytes)
gtw:    80 21 01 67 00 04

INFO:   Negotiation complete.
DEBUG:  pppd ---> gateway (6 bytes)
pppd:   80 21 02 67 00 04

DEBUG:  gateway ---> pppd (16 bytes)
gtw:    80 21 03 03 00 0e 01 0a ac 10 f5 10 2e 19 f2 5b

DEBUG:  pppd ---> gateway (16 bytes)
pppd:   80 21 01 04 00 0e 01 0a ac 10 f5 10 a9 fe 02 01

DEBUG:  Got Address: 172.16.245.16
DEBUG:  gateway ---> pppd (16 bytes)
gtw:    80 21 03 04 00 0e 01 0a ac 10 f5 10 2e 19 f2 5b

DEBUG:  if_config: not ready yet...
DEBUG:  pppd ---> gateway (16 bytes)
pppd:   80 21 01 05 00 0e 01 0a ac 10 f5 10 a9 fe 02 01

DEBUG:  gateway ---> pppd (16 bytes)
gtw:    80 21 03 05 00 0e 01 0a ac 10 f5 10 2e 19 f2 5b

DEBUG:  pppd ---> gateway (16 bytes)
pppd:   80 21 01 06 00 0e 01 0a ac 10 f5 10 a9 fe 02 01

DEBUG:  gateway ---> pppd (16 bytes)
gtw:    80 21 03 06 00 0e 01 0a ac 10 f5 10 2e 19 f2 5b

DEBUG:  pppd ---> gateway (16 bytes)
pppd:   80 21 01 07 00 0e 01 0a ac 10 f5 10 a9 fe 02 01

DEBUG:  gateway ---> pppd (16 bytes)
gtw:    80 21 03 07 00 0e 01 0a ac 10 f5 10 2e 19 f2 5b

DEBUG:  pppd ---> gateway (16 bytes)
pppd:   80 21 01 08 00 0e 01 0a ac 10 f5 10 a9 fe 02 01

DEBUG:  Got Address: 172.16.245.16
DEBUG:  if_config: not ready yet...
DEBUG:  gateway ---> pppd (16 bytes)
gtw:    80 21 04 08 00 0e 01 0a ac 10 f5 10 a9 fe 02 01

DEBUG:  pppd ---> gateway (6 bytes)
pppd:   80 21 01 09 00 04

DEBUG:  gateway ---> pppd (6 bytes)
gtw:    80 21 02 09 00 04

Peer refused to agree to our IP address
Connect time 0.1 minutes.
Sent 1199 bytes, received 1179 bytes.
DEBUG:  pppd ---> gateway (28 bytes)
pppd:   80 21 05 0a 00 1a 52 65 66 75 73 65 64 20 6f 75 72 20 49 50 20 61 64 64 72 65 73 73

DEBUG:  gateway ---> pppd (6 bytes)
gtw:    80 21 06 0a 00 04

DEBUG:  Got Address: 172.16.245.16
DEBUG:  if_config: not ready yet...
DEBUG:  Got Address: 172.16.245.16
DEBUG:  if_config: not ready yet...
DEBUG:  Got Address: 172.16.245.16
DEBUG:  if_config: not ready yet...
DEBUG:  Got Address: 172.16.245.16
DEBUG:  Got Address: 172.16.245.16
..
DEBUG:  Got Address: 172.16.245.16
DEBUG:  if_config: not ready yet...
DEBUG:  Got Address: 172.16.245.16
DEBUG:  if_config: not ready yet...
DEBUG:  Got Address: 172.16.245.16
DEBUG:  if_config: not ready yet...
DEBUG:  Got Address: 172.16.245.16
ERROR:  Timed out waiting for the ppp interface to be UP.
INFO:   Cancelling threads...
DEBUG:  Error canceling if_config_thread: No such process
INFO:   Cleanup, joining threads...
DEBUG:  disconnecting
DEBUG:  Waiting for pppd to exit...
DEBUG:  waitpid: pppd exit status code 16
ERROR:  pppd: The link was terminated by the modem hanging up.
INFO:   Terminated pppd.
INFO:   Closed connection to gateway.

I try to enable ppp log but only got:

rcvd [IPCP ConfNak id=0x7 <addrs 172.16.245.16 46.25.242.91>]
sent [IPCP ConfReq id=0x8 <addrs 172.16.245.16 169.254.2.1>]
rcvd [IPCP ConfRej id=0x8 <addrs 172.16.245.16 169.254.2.1>]
sent [IPCP ConfReq id=0x9]
rcvd [IPCP ConfAck id=0x9]
Peer refused to agree to our IP address
Connect time 0.2 minutes.
Sent 1199 bytes, received 1179 bytes.
sent [IPCP TermReq id=0xa "Refused our IP address"]
rcvd [IPCP TermAck id=0xa]

The text was updated successfully, but these errors were encountered:

DimitriPapadopoulos · 2023-03-09T18:38:49Z

I don't know how to tackle this. As noted in #920, the error originates in pppd and I would have hoped that #1021 would fix this by adding ipcp-accept-local. I'm not sure what each of the pppd options do, you could try to a few other pppd options such as ipcp-accept-remote, perhaps in /etc/ppp/options – for test purposes.

The real fix would be to merge branch tun and get rid of pppd. Unfortunately, it's not ready yet: routing needs fixing – help welcome!

DimitriPapadopoulos · 2023-03-09T18:43:36Z

Note that in the <addrs 172.16.245.16 169.254.2.1> request sent by pppd, the remote address 169.254.2.1 is set by openfortivpn, while the local address 172.16.245.16 is suggested by the peer and taken up by pppd as far as I can understand.

wmasilva · 2023-03-10T08:59:42Z

I try the ipcp-accept-remote and the tunnel now always connect, but there is no traffic in the vpn, i cannot reach the subnets on the other side, routes are well created...

what i notice is that after the tunnel is up, in debug only exists traffic in one way: ppp -> gateway, the gateway is not responding not sure if is normal..

INFO:   Tunnel is up and running.
DEBUG:  pppd ---> gateway (66 bytes)
DEBUG:  pppd ---> gateway (148 bytes)
DEBUG:  pppd ---> gateway (230 bytes)
DEBUG:  pppd ---> gateway (312 bytes)
DEBUG:  pppd ---> gateway (394 bytes)
DEBUG:  pppd ---> gateway (476 bytes)
DEBUG:  pppd ---> gateway (558 bytes)
DEBUG:  pppd ---> gateway (640 bytes)
DEBUG:  pppd ---> gateway (722 bytes)
DEBUG:  pppd ---> gateway (804 bytes)
DEBUG:  pppd ---> gateway (886 bytes)
DEBUG:  pppd ---> gateway (968 bytes)
DEBUG:  pppd ---> gateway (1344 bytes)
DEBUG:  pppd ---> gateway (66 bytes)

How can i help you to speedup the tun implementation?

wmasilva · 2023-03-10T10:25:16Z

I just try openconnect, it uses tun, and is OK, the connection is establish always.
It uses vpnc scripts to handle routing, could you do the same here?

DimitriPapadopoulos · 2023-03-10T11:23:14Z

I just need help with fixing routing.

I agree about exploring vpnc-scripts, see #678. But then vpnc-scripts is not well-maitained either: systemd-resolved support has been broken for years and I cannot get merge requests to get accepted.

wmasilva · 2023-03-10T12:37:13Z

sure, i just start playing with vpnc-scripts , i miss the options to set no-route or no-dns (on my setup i want to create them manually), the positive side is that we can easily modify the script.

I can help you test the tun branch, i have debian environment is it ok for you?

DimitriPapadopoulos · 2023-03-10T12:52:59Z

Sure. I'm on Ubuntu 22.04 myself.

Perhaps we can simulate no-route or no-dns by resetting environment variables passed as arguments to vpnc-scripts?

Tatsh · 2023-04-24T06:24:15Z

I ran into this issue after updating ppp to 2.5.0. Gentoo main tree does not yet have an updated openfortivpn. Even so, I have been using the old patch for an ifup issue (setting DNS for systemd-resolved) and do not know how to migrate to vpnc-scripts.

DimitriPapadopoulos · 2023-04-24T07:53:08Z

Migrating to vpnc-scripts implies someone contributing the actual code to openfortivpn.

Using tun instead of pppd implies building the tun branch from sources.

…nection fails with 'Peer refused to agree to his IP address' message. see adrienverge/openfortivpn/issues/1076 Signed-off-by: Petru Ciobanu <[email protected]>

net-dialup/ppp-2.5.0 is incompatible. A new connection fails with 'Peer refused to agree to his IP address' message. see adrienverge/openfortivpn/issues/1076 Signed-off-by: Petru Ciobanu <[email protected]> Closes: #30818 Signed-off-by: Joonas Niilola <[email protected]>

mrbaseman · 2023-07-06T19:31:04Z

I'm trying to catch up here. If I can help with the routing in the context ov vpnc-scripts, just let me know

timthelion · 2023-07-20T10:49:40Z

This appears for me in 1.20.5 but not in 1.20.4:

timothy@nixos ~/> nix-shell -p 'openfortivpn.overrideAttrs(old: {src = builtins.fetchTarball https://github.com/adrienverge/openfortivpn/archive/refs/tags/v1.20.4.tar.gz;})'
bash: /home/timothy/.cargo/env: No such file or directory

[nix-shell:~/]$ sudo openfortivpn --config vpn.config
INFO:   Connected to gateway.
INFO:   Authenticated.
INFO:   Remote gateway has allocated a VPN.
Using interface ppp0
Connect: ppp0 <--> /dev/pts/2
INFO:   Got addresses: [10.112.107.4], ns [0.0.0.0, 0.0.0.0]
INFO:   Negotiation complete.
local  IP address 10.112.107.4
remote IP address 185.103.147.171
INFO:   Interface ppp0 is UP.
INFO:   Setting new routes...
INFO:   Adding VPN nameservers...
INFO:   Tunnel is up and running.
^CINFO:   Cancelling threads...
INFO:   Cleanup, joining threads...
INFO:   Setting ppp0 interface down.
INFO:   Restoring routes...
INFO:   Removing VPN nameservers...
Hangup (SIGHUP)
Modem hangup
Connect time 0.2 minutes.
Sent 0 bytes, received 0 bytes.
Connection terminated.
INFO:   pppd: The link was terminated by the modem hanging up.
INFO:   Terminated pppd.
INFO:   Closed connection to gateway.
INFO:   Logged out.

[nix-shell:~/]$ exit
exit
timothy@nixos ~/> nix-shell -p 'openfortivpn.overrideAttrs(old: {src = builtins.fetchTarball https://github.com/adrienverge/openfortivpn/archive/refs/tags/v1.20.5.tar.gz;})'
bash: /home/timothy/.cargo/env: No such file or directory

[nix-shell:~/]$ sudo openfortivpn --config vpn.config
INFO:   Connected to gateway.
INFO:   Authenticated.
INFO:   Remote gateway has allocated a VPN.
Using interface ppp0
Connect: ppp0 <--> /dev/pts/2
INFO:   Got addresses: [10.112.107.4], ns [0.0.0.0, 0.0.0.0]
INFO:   Negotiation complete.
INFO:   Negotiation complete.
Peer refused to agree to his IP address
Connect time 0.1 minutes.
Sent 1101 bytes, received 1081 bytes.
^CINFO:   Cancelling threads...
INFO:   Cleanup, joining threads...
Hangup (SIGHUP)
Modem hangup
Connection terminated.
INFO:   pppd: The link was terminated by the modem hanging up.
INFO:   Terminated pppd.
INFO:   Closed connection to gateway.
INFO:   Logged out.

michel-zimmer · 2023-07-24T15:23:17Z

The workaround of adding ipcp-accept-remote to /etc/ppp/options works for me under NixOS with openfortivpn version 1.20.5.

DimitriPapadopoulos · 2023-08-07T07:14:33Z

It looks like we need to add ipcp-accept-remote back, perhaps in a new version 1.21 and then fix:

Linux with older versions of pppd
macOS

I will need help at least with the latter.

AdrianChungie · 2023-08-09T16:41:49Z

This appears for me in 1.20.5 but not in 1.20.4:

timothy@nixos ~/> nix-shell -p 'openfortivpn.overrideAttrs(old: {src = builtins.fetchTarball https://github.com/adrienverge/openfortivpn/archive/refs/tags/v1.20.4.tar.gz;})'
bash: /home/timothy/.cargo/env: No such file or directory

[nix-shell:~/]$ sudo openfortivpn --config vpn.config
INFO:   Connected to gateway.
INFO:   Authenticated.
INFO:   Remote gateway has allocated a VPN.
Using interface ppp0
Connect: ppp0 <--> /dev/pts/2
INFO:   Got addresses: [10.112.107.4], ns [0.0.0.0, 0.0.0.0]
INFO:   Negotiation complete.
local  IP address 10.112.107.4
remote IP address 185.103.147.171
INFO:   Interface ppp0 is UP.
INFO:   Setting new routes...
INFO:   Adding VPN nameservers...
INFO:   Tunnel is up and running.
^CINFO:   Cancelling threads...
INFO:   Cleanup, joining threads...
INFO:   Setting ppp0 interface down.
INFO:   Restoring routes...
INFO:   Removing VPN nameservers...
Hangup (SIGHUP)
Modem hangup
Connect time 0.2 minutes.
Sent 0 bytes, received 0 bytes.
Connection terminated.
INFO:   pppd: The link was terminated by the modem hanging up.
INFO:   Terminated pppd.
INFO:   Closed connection to gateway.
INFO:   Logged out.

[nix-shell:~/]$ exit
exit
timothy@nixos ~/> nix-shell -p 'openfortivpn.overrideAttrs(old: {src = builtins.fetchTarball https://github.com/adrienverge/openfortivpn/archive/refs/tags/v1.20.5.tar.gz;})'
bash: /home/timothy/.cargo/env: No such file or directory

[nix-shell:~/]$ sudo openfortivpn --config vpn.config
INFO:   Connected to gateway.
INFO:   Authenticated.
INFO:   Remote gateway has allocated a VPN.
Using interface ppp0
Connect: ppp0 <--> /dev/pts/2
INFO:   Got addresses: [10.112.107.4], ns [0.0.0.0, 0.0.0.0]
INFO:   Negotiation complete.
INFO:   Negotiation complete.
Peer refused to agree to his IP address
Connect time 0.1 minutes.
Sent 1101 bytes, received 1081 bytes.
^CINFO:   Cancelling threads...
INFO:   Cleanup, joining threads...
Hangup (SIGHUP)
Modem hangup
Connection terminated.
INFO:   pppd: The link was terminated by the modem hanging up.
INFO:   Terminated pppd.
INFO:   Closed connection to gateway.
INFO:   Logged out.

I tried this in the nix-shell with version 1.20.4 and it works fine. If I try using 1.20.5 I get the same problem of "Peer refused to agree to his IP address" and it won't work.

I'm a bit new to nixos, so I just need to figure out how to use an older package in the configuration.nix until this issue is fixed.

timthelion · 2023-08-09T16:45:21Z

@AdrianChungie try something like:

  environment.systemPackages = with pkgs; [
      (openfortivpn.overrideAttrs(
            old: {
              src = builtins.fetchTarball https://github.com/adrienverge/openfortivpn/archive/refs/tags/v1.20.4.tar.gz;
      }))
     vim # Do not forget to add an editor to edit configuration.nix! The Nano editor is also installed by default.
     wget
     slack
     firefox
     restic
     rsync
     emacs
.. .

AsharLohmar · 2023-09-08T10:19:03Z

It all seems to be a misunderstanding between ppp and openfortivpn, more on the ppp side
I have 2 containers with Alpine 3.17.2 and 3.18.3, first has ppp-2.4.9-r6 the second has ppp-2.5.0-r2, in both cases the /etc/ppp/options contains only lock
I have 2 version for the client 1.20.1 and 1.20.5

client 1.20.1 with ppp-2.4.9-r6 ok
client 1.20.5 with ppp-2.4.9-r6 ok

client 1.20.1 with ppp-2.5.0-r2 Peer refused to agree to his IP address
client 1.20.5 with ppp-2.5.0-r2 Peer refused to agree to his IP address

After adding ipcp-accept-remote to /etc/ppp/options both client versions kept failing with

Hangup (SIGHUP)
Modem hangup
Connection terminated.
ERROR:  pppd: The link was terminated by the modem hanging up.
INFO:   Terminated pppd.

But this one is related to the Alpine ppp package, details here
I just needed to mkdir -p /run/ppp/lock after this
client 1.20.1 with ppp-2.5.0-r2 ok
client 1.20.5 with ppp-2.5.0-r2 ok

Bottom line ipcp-accept-remote helped in my case too

githubixx · 2023-09-11T06:00:33Z

I also got Peer refused to agree to our IP address on Arch Linux with openfortivpn v1.20.5 and pppd v0.2.5. Adding ipcp-accept-remote to /etc/ppp/options also helped in my case. ipcp-accept-local option was not needed.

smart2128 · 2023-09-11T08:28:09Z

I'm also on Arch Linux with recently updated openfortivpn 1.20.5, pppd 2.5.0 and networkmanager-fortisslvpn 1.4.0.
Adding ipcp-accept-remote to /etc/ppp/options allows to establish VPN tunnels, but remote networks are still unreachable.

psic4t · 2023-09-11T08:40:41Z

I'm also on Arch Linux with recently updated openfortivpn 1.20.5, pppd 2.5.0 and networkmanager-fortisslvpn 1.4.0. Adding ipcp-accept-remote to /etc/ppp/options allows to establish VPN tunnels, but remote networks are still unreachable.

I've got the same problem since today.

flba35 · 2023-09-11T09:47:26Z

Same here, on Archlinux.
Had to downgrade ppp:
downgrade 'ppp=2.4.9-3' 'networkmanager-pptp=1.2.12-1'

smart2128 · 2023-09-11T09:51:38Z

Yes, the problem seems to be on ppp 2.5.0.
Downgrading to ppp 2.4.9, openfortivpn works again.
For archlinux users, while networkmanager-pptp is still packaged, networkmanager-fortisslvpn has been moved to AUR and depends on ppp 2.5.0.

Still34 · 2023-09-18T03:05:56Z

Can confirm rolling back to ppp==2.4.9 works around this issue

karlovskiy · 2023-09-19T17:03:24Z

I've got the same problem today. Rolling back to ppp 2.4.9 resolves this issue

akha666 · 2023-09-20T13:35:53Z

I have fixed this issue by enabling or adding

ipcp-accept-local
ipcp-accetp-remote

in the /etc/ppp/options

smart2128 · 2023-09-20T13:58:49Z

For those using networkmanager-fortisslvpn on Archlinux, you can find a solution reading this comment in AUR.
No needs to edit /etc/ppp/options.

dakota-marshall · 2023-09-22T13:11:09Z

I have fixed this issue by enabling or adding
ipcp-accept-local
ipcp-accept-remote
in the /etc/ppp/options

Can confirm that this resolved the issue for me as well. After uncommenting these config lines, VPN connected without issue.

msm-code · 2023-10-24T11:12:52Z

PSA for people using nixos like me, you need:

environment.etc."ppp/options".text = "ipcp-accept-remote";

DimitriPapadopoulos · 2023-10-24T14:10:02Z

I think we need to make ipcp-accept-remote the default, and add a compile-time option to disable it on older systems that don't ship PPP 2.5.0 yet.

leppaott · 2023-11-13T08:41:04Z

Hmm VPN stopped working Fedora 39. Interesting. Well seems Fedora's still on 1.19.

frendon · 2023-11-13T10:06:09Z

Hmm VPN stopped working Fedora 39. Interesting. Well seems Fedora's still on 1.19.

Hi @leppaott , same case. I fixit with add the next line to options, the same indicate in the issue, and work arround in this issuue.
My options in fedora is , test with client 1.19.

cat /etc/ppp/options
lock
ipcp-accept-remote <-- NEW LINE

The cause is fedora 39 update pppd to ~~2.0.5~~ 2.5.0

https://packages.fedoraproject.org/pkgs/ppp/ppp/fedora-39.html --> ppp-2.5.0-3.fc39 in Fedora 39
https://packages.fedoraproject.org/pkgs/ppp/ppp/fedora-38.html --> ppp-2.4.9-9.fc38 in Fedora 38

ameijboom · 2023-11-13T12:48:07Z

Hi @leppaott , same case. I fixit with add the next line to options, the same indicate in the issue, and work arround in this issuue. My options in fedora is , test with client 1.19.

cat /etc/ppp/options lock ipcp-accept-remote <-- NEW LINE

The cause is fedora 39 update pppd to ~~2.0.5~~ 2.5.0

https://packages.fedoraproject.org/pkgs/ppp/ppp/fedora-39.html --> ppp-2.5.0-3.fc39 in Fedora 39 https://packages.fedoraproject.org/pkgs/ppp/ppp/fedora-38.html --> ppp-2.4.9-9.fc38 in Fedora 38

Fixed it for me! Had to edit the file, add the new line & simply retried connecting. Thanks!

DimitriPapadopoulos · 2023-11-13T17:47:18Z

@ameijboom Are you using Fedora 39 too?

ameijboom · 2023-11-15T06:39:21Z

@ameijboom Are you using Fedora 39 too?

I was, however after some more testing, I realised I can’t access any resources on the network. So while I can connect, it’s basically useless right now.

DimitriPapadopoulos · 2023-11-15T08:46:10Z

@ameijboom Thank you for the feedback. So while adding ipcp-accept-remote fixes a first issue related to pppd > 2.5.0, many if not all users on Fedora 39 experience a second issue, which we can follow up in #1141.

DimitriPapadopoulos · 2023-11-15T08:48:57Z

@frendon Is ipcp-accept-remote enough to get openfortivpn to work on Fedora 39 in your case? Other users complain that while the ipcp-accept-remote is necessary, it is not sufficient to fix later routing issues or DNS issues. These new issues are tracked in #1141.

frendon · 2023-12-16T13:00:00Z

@frendon Is ipcp-accept-remote enough to get openfortivpn to work on Fedora 39 in your case? Other users complain that while the ipcp-accept-remote is necessary, it is not sufficient to fix later routing issues or DNS issues. These new issues are tracked in #1141.

Yes, with this modification, all my vpns that connect with openfortivpn it's working. Perhaps its my configuration, I've two scritps:

Connect with the vpn.
Script that, launch vpn

sudo openfortivpn -c configVPN

Content of configVPM

host = xxx.example.com
port = 444
username = YYYYYYY
password = XXXXXXXXXXXXXXXXXXXXXX
user-cert = ./cer.pem
user-key = ./key.pem
trusted-cert = ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
set-dns = 0
set-routes = 1
half-internet-routes = 0
pppd-use-peerdns = 0
insecure-ssl = 0
cipher-list = HIGH:!aNULL:!kRSA:!PSK:!SRP:!MD5:!RC4
persistent = 0
seclevel-1 = 0

Manual settings dns.

sudo systemd-resolve --interface=ppp0 --set-dns=XXXXXXX --set-dns=YYYYYY --set-domain=example.com

DimitriPapadopoulos · 2023-12-16T17:45:40Z

@frendon Ah, most probably you don't experience DNS issues because you run your own script. Thank you for coming back to use with this important information. We will track DNS issues in #1141.

sawhsib · 2024-06-09T07:31:59Z

Thank You
After removing comment on
ipcp-accept-local
ipcp-accept-remote

from /etc/ppp/options
My openfortigui works

DimitriPapadopoulos added bug duplicate labels Mar 9, 2023

Scantlight mentioned this issue May 1, 2023

Openfortivpn bump version to 1.20.2 gentoo/gentoo#30818

Closed

aminvakil mentioned this issue Jun 18, 2023

openfortivpn version 1.20.4 #1115

Closed

lgaggini mentioned this issue Sep 13, 2023

Peer refused to agree to his IP address theinvisible/openfortigui#194

Closed

akha666 mentioned this issue Sep 20, 2023

Fix "Peer refused to agree to our IP address" #1021

Merged

DimitriPapadopoulos mentioned this issue Oct 24, 2023

Add "ipcp-accept-remote" pppd option #1148

Merged

DimitriPapadopoulos closed this as completed in #1148 Nov 3, 2023

This comment was marked as off-topic.

Sign in to view

Repository owner deleted a comment from Neustradamus Dec 5, 2023

rodrigoaguilera mentioned this issue May 8, 2024

Let know we don't support HTTP compression #1213

Merged

Peer refused to agree to our IP address and connection is terminated #1076

Peer refused to agree to our IP address and connection is terminated #1076

Comments

wmasilva commented Mar 9, 2023

DimitriPapadopoulos commented Mar 9, 2023 • edited Loading

DimitriPapadopoulos commented Mar 9, 2023

wmasilva commented Mar 10, 2023

wmasilva commented Mar 10, 2023

DimitriPapadopoulos commented Mar 10, 2023

wmasilva commented Mar 10, 2023

DimitriPapadopoulos commented Mar 10, 2023

Tatsh commented Apr 24, 2023

DimitriPapadopoulos commented Apr 24, 2023 • edited Loading

mrbaseman commented Jul 6, 2023

timthelion commented Jul 20, 2023

michel-zimmer commented Jul 24, 2023

DimitriPapadopoulos commented Aug 7, 2023 • edited Loading

AdrianChungie commented Aug 9, 2023

timthelion commented Aug 9, 2023

AsharLohmar commented Sep 8, 2023

githubixx commented Sep 11, 2023

smart2128 commented Sep 11, 2023

psic4t commented Sep 11, 2023

flba35 commented Sep 11, 2023 • edited Loading

smart2128 commented Sep 11, 2023 • edited Loading

Still34 commented Sep 18, 2023

karlovskiy commented Sep 19, 2023

akha666 commented Sep 20, 2023

smart2128 commented Sep 20, 2023

dakota-marshall commented Sep 22, 2023 • edited by DimitriPapadopoulos Loading

msm-code commented Oct 24, 2023

DimitriPapadopoulos commented Oct 24, 2023

leppaott commented Nov 13, 2023 • edited Loading

frendon commented Nov 13, 2023 • edited by DimitriPapadopoulos Loading

ameijboom commented Nov 13, 2023 • edited by DimitriPapadopoulos Loading

DimitriPapadopoulos commented Nov 13, 2023

This comment was marked as off-topic.

This comment was marked as off-topic.

ameijboom commented Nov 15, 2023

DimitriPapadopoulos commented Nov 15, 2023

DimitriPapadopoulos commented Nov 15, 2023 • edited Loading

frendon commented Dec 16, 2023

Content of configVPM

DimitriPapadopoulos commented Dec 16, 2023 • edited Loading

sawhsib commented Jun 9, 2024 • edited Loading

DimitriPapadopoulos commented Mar 9, 2023 •

edited

Loading

DimitriPapadopoulos commented Apr 24, 2023 •

edited

Loading

DimitriPapadopoulos commented Aug 7, 2023 •

edited

Loading

flba35 commented Sep 11, 2023 •

edited

Loading

smart2128 commented Sep 11, 2023 •

edited

Loading

dakota-marshall commented Sep 22, 2023 •

edited by DimitriPapadopoulos

Loading

leppaott commented Nov 13, 2023 •

edited

Loading

frendon commented Nov 13, 2023 •

edited by DimitriPapadopoulos

Loading

ameijboom commented Nov 13, 2023 •

edited by DimitriPapadopoulos

Loading

DimitriPapadopoulos commented Nov 15, 2023 •

edited

Loading

DimitriPapadopoulos commented Dec 16, 2023 •

edited

Loading

sawhsib commented Jun 9, 2024 •

edited

Loading