Hello @David-TP 

Thank you for your Replay

regarding TKID260221657 it will not work as I expected :-( here the answer from the German Support

Der TP-Link M8550 unterstützt keine eingehenden VPN-Verbindungen über IPv6 auf der WAN-Seite. Der integrierte WireGuard-VPN-Server dieses Modells benötigt eine öffentliche IPv4-Adresse, um aus dem Internet erreichbar zu sein.

In Ihrem Fall stellt Ihr Mobilfunkanbieter Folgendes bereit:

• Eine private IPv4-Adresse (10.x.x.x – CG-NAT) → diese ist aus dem Internet nicht erreichbar

• Eine öffentliche IPv6-Adresse → jedoch unterstützt dieses Modell keinen VPN-Serverbetrieb über IPv

regarding the Issue that "I can't make a connection to my home network" it's also very simple. The  M8550 don't accept my config file from my Fritzbox because of my Home network IP 192.168.0.0/24 If I change it to something else e.g. 192.168.2.0/24 I can import the Config. This has been verified by @Maxx2112 see

https://community.tp-link.com/en/home/forum/topic/842696?replyId=1665954

Long-term I may change may Home network address and give it a other try, but for sure not the next 3 to 4 months.

regarding your question:

> By the way, do you wish the VPN clients on M8550 could only access certain local servers on the Fritzbox, not the whole LAN network or external internet connection?

I need to access the or external internet with a German IP and I don't want use a public VPN-Server.

Overall the M8550 is a very nice router, easy to take around and I can use it without battery installed. For me, 5G is nice to have, but I don't really need it.

But the whole VPN stuff ist not working as I expected, and therefor, just as a simple mobile hotspot, the M8550 ist far to expensive. I wouldn't by it again :-(

Sorry,

very best regards

CW56

  @Maxx2112 @TP-Link @David-TP 

Hi everyone,

I bought my M8550 to connect to my local network, especially my NAS, via WireGuard. However, it doesn't seem to work. I can set up the WireGuard connection with the beta firmware, and the M8550's web UI shows that it is connected. However, regardless of which device I use to test the connection, it doesn't work.

Does your conclusion in this thread mean that this is generally not possible with the M8550? That would be very surprising to me, because it works with my much cheaper TP-Link TL-WR3002X (it's just way too slow for my use case).

What VPN-capable mobile router would I need to make it work?

Thank you in advance for your response.

Kind regards,

Nate

Hi @Chess07 ,

in my experience the VPN connection via WireGurad is working. In the mean time I was able to switch to the beta Firmware, with this the configuration can be imported without any problems or adjustments. My former issue, that I only can access the network I am connected to via WireGurad but not the second network which has its own vpn connection is still there.

Did you change anything else on the setup besides the new router?

To answer your question "Does your conclusion in this thread mean that this is generally not possible with the M8550?" 

It is possible with the M8550 and should be working. There seems to be another issue (or maybe your M8550 is faulty).

In my case I am able to connect to my home network through WireGuard an can access my NAS (samba share) as well as any other network resource.  

But there are some problems with the M8550. For me it is still not possible to import a WireGuard configuration, if the home network as 192.168.0.0/24 as network IP. Then there wil be an error message if I try to import the config.

Please, can you provide some mor information to your setup?

Best regards

Maxx

  @TP-Link  @David-TP @Maxx2112 

Bonjour,

J'ai acheté ce routeur pour la fonction VPN Client Wirguard (utilisée avec le serveur VPN de ma Freebox).

Mais cela ne fonctionne pas. Lors du paramétrage de VPN avec le fichier de configuration, il est indiqué sur la ligne AllowedIP les 3 adresses suivantes : 0.0.0.0/0, 192.168.27.64/27, 192.168.1.0/24. Mais il est impossible de valider la configuration avec ces 3 adresses IP. Le format est incompatible... Il faut en indiquer une seule afin de pouvoir valider la configuration du tunnel, mais du coup, la connexion ne fonctionne pas. 

J'ai installé la versio BETA pour le modèle EU.

Avec cette version, j'ai pu paramétrer ma connection avec les 3 adresses IP sur la ligne AllowedIP : 0.0.0.0/0, 192.168.27.64/27, 192.168.1.0/24.

J'arrive à établir une connexion, mais elle ne fonctionne pas.

Après vérification du paramétrage de ma connexion, il s'avère qu'une seule adresse IP a été renseingée sur le champs Allowed IP, à savoir 0.0.0.0/0. La connexion ne pourra donc pas fonctionner.

J'ai acheté ce routeur pour cette fonctionnalité et je suis très décus de ne pas pouvoir l'utiliser.

J'ai ouvert le ticket #73299 auprès de l'assistance avec des captures d'écran et plus de précisions.

Il faudrait que TP-Link prenne en charge ce problème bloquant rapidement ! Ce n'est pas très serieux pour un produit de cette gamme. Il s'agit d'un vice caché au sens du code de la consommation !

Tout fonctionne très bien avec mon routeur Glinet !

Hi  @Jerome13,

I think the problem is the 0.0.0.0/0 IP adress. I had a similar issue in a privious firmware. I manually deleted the adress from the allowed address filed. Afterwards it worked. But I only trie /24 networks, I am not sure whether a /27 is working. For my setup I had to implement two seperate connections. One for my 192.168.178.0/24 network and one for my 192.168.2.0/24 network although they are connected via a seperate vpn tunnel. 

It seems that the allowed address field only works with one network address.

With the beta firmware it is possible to save the configuration more than on network address in the field but it is still working with only one.

I hope this information helps you.

Best regards

Maxx