I have a freedombox behing two routers doing NAT with different /24 IPv4 ranges. The freedombox is alone in 192.168.a.xxx (that router sets up an openVPN connection in order to have a public IPv4 address while I have no public IPv4 address with my connection) and the WAN interface of its router is in 192.168.b.xxx.
When I have wireguard setup as server on the freedombox and I connect to it via my laptop running Trisquel GNU/Linux, the laptop is allocated the address 10.84.0.2 and I get responses when I ping 10.84.0.1, 192.168.a.1 or 192.168.b.1.
If I try accessing 10.84.0.1, I have:
$ curl 10.84.0.1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href="http://10.84.0.1/freedombox">here</a>.</p>
<hr>
<address>Apache/2.4.68 (Debian) Server at 10.84.0.1 Port 80</address>
</body></html>
$ curl http://10.84.0.1/freedombox
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="https://10.84.0.1/freedombox">here</a>.</p>
<hr>
<address>Apache/2.4.68 (Debian) Server at 10.84.0.1 Port 80</address>
</body></html>
$ curl https://10.84.0.1/freedombox
^C
$
When I try with https, it remains stuck forever so I have to interrupt.
$ curl http://192.168.b.1
<!DOCTYPE html><html lang=""><head><meta charset="utf-8"><meta name="robots" content="noindex, nofollow"><meta http-equiv="Cache-Control" content="no-cache,no-store,must-revalidate"><meta http-equiv="pragma" content="no-cache"><meta http-equiv="expires" content="0"><meta http-equiv="X-UA-Compatible" content="IE=edge"><meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1,minimum-scale=1,user-scalable=no"><title>Admin Panel</title><link href="/js/app.5d830700.js" rel="preload" as="script"></head><body><noscript><strong>We're sorry but gl-ui doesn't work properly without JavaScript enabled. Please enable it to continue.</strong></noscript><div id="app"></div><script src="/js/app.5d830700.js"></script></body></html>
If I try the same with https, it remains stuck as well.
I can even get ping responses from other machines in 192.168.b.xxx. One machine there is homeassistant that normally responds on http with port 8123 but here it does not respond. Then, if I try to ping any IP address from internet there is no response at all.
I could successfully connect via ssh on 192.168.a.1 (running libreCMC) and 192.168.a.2 (running openWRT) but I cannot access their web interface.
I have ethernet interface of the freedombox (rasberry pi 4) configured as external, the WG interface as internal (seems it cannot be changed).
At least, I’d like to be able to access web interfaces of hosts on 192.168.b.xxx when I have wireguard connected.