[Solved] 3 WG clients only 1 works well - closed

Installing and Using OpenWrt
21

A relevant idea that I am already pursuing.

22

Add the option route_allowed_ips '1' line to each of the peers on the openwrt config.

Restart and test again.

23

Didn't work.
No status change, no green indicator in the wg-app and very slow traffic...via LTE/5G.
Mobile network is excellent.
Currently I check the DNS task, which @egc mentioned above.

24

This setup works within the “known” WLAN perfectly (green indicator and full speed traffic)...but outside...

25

This suggests that there may be something going on with your external connectivity and not OpenWrt.

So, to confirm... if you are connected to the network via wifi, you can successfully handshake and access the internet. But if you try to use the cellular network (wifi off), you are unable to connect?

If this is correct, let's review a few things...

first, let's see the output of

ifstatus wan | grep address
wg show

(you shouldn't need to redact anything from the first command; please redact the keys from the wg command)

Then, let's see the port forwarding setup on your main router (a screen grab will work here since it's not OpenWrt).

Finally, let's select one if your peer devices (a phone, preferably) and look at the config there.

26

Ok, I have just quickly installed a “third-party WLAN” on the MT6000 and have exactly the same effect as with the mobile network. So it's not just a mobile network problem

root@GL-MT6000:~# ifstatus wan | grep address
		"addresses",
	"ipv4-address": [
			"address": "192.168.150.14",
	"ipv6-address": [
		"ipv4-address": [
		"ipv6-address": [
root@GL-MT6000:~# wg show
interface: WGSERVER
  public key: vFWRsqm/vgq27o06fLxaSNpzP1rW0sdupmy7BxJYtAU=
  private key: (hidden)
  listening port: 47362

peer: +uDFDf5N+lMRjHBjm7v5z39k0u2VpGE/arIZHByXPkQ=
  preshared key: (hidden)
  endpoint: 192.168.152.51:43120
  allowed ips: 10.0.49.2/32
  latest handshake: 3 hours, 34 minutes, 52 seconds ago
  transfer: 2.89 KiB received, 8.16 KiB sent

peer: JnfGxnqOsNOUdWxAcz+SpLhrRq0Y59NACRWv1+wnoV8=
  preshared key: (hidden)
  allowed ips: 10.0.49.4/32

peer: Pn2PpbY/HX56aGXzCFa3F3XcahTl99UHIQmTowrazy0=
  preshared key: (hidden)
  allowed ips: 10.0.49.3/32
root@GL-MT6000:~#
27

Can you be more specific here...

  1. What do you mean by a "third party WLAN"?
  2. What is your specific method of testing?
28

You're right, the wording is a bit unfortunate...

I have a "trusted" WLan network (WG works here, I mentioned above) and have now set up an "untrusted" WLan network with an additional router (here 192.168.150.1[main router]) and WG doesn't work in this network either - so it's not just a mobile problem.
It should be a test due to mobile network problem.

29

I still don't understand the details about how you're testing with this new network.

Can you provide a diagram that might make it more clear? Please be sure to label all the devices, including their IP addresses.

Also, what is your test method?

30

The problem seams to be to reach the router MT6000.

diagram
diagram1403×992 83.3 KB

31

The problem is not related to OpenWrt -- it is clearly the main router that is involved here.

Can we see a screenshot of this config item in the main router?

Let's also see the output of the following from your OpenWrt router:

ifstatus wan | grep address

Finally, we need to verify that you have a proper public IP on your main router's WAN. I don't know exactly where you'll find that information, but it should be in a status page or similar. Please post the first two octets (in bold: aaa.bbb.ccc.ddd) once you find it.

32

Thanks for your assessment - but I disagree - why:

When I received the MT6000 I set up the MT6000 with the standard GL-iNET software (openwrt21.xxx) in the same way (AGH+WG server) and this setup worked behind the main router [Fritzbox(192.168.150.1)]. However, I did not want the software dependency of GL-iNET and therefore I switched to openwrt(25.05.5) and so far the migration has almost worked...just not with the WG server.

The Fritzbox(main router) has removed ssh by default, so I will now try to find out the data via the support script.

33

Peter....I found the root cause!

In the main router I have forgotten to forward the correct IP(MT6000) address...

Thank you for your persistence in making me realize the mistake myself.

Thank you very much, Peter!

34

The problem normally sits 90 cm in front of the screen... :roll_eyes:

1 Like
35

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.