I would like to set up a map lite as a wireguard client and tunnel all the traffic from the ethernet interface via the vpn.
The idea is that I want to use the map lite to:
connect to the wireless network in location A [done] _- connect to a wireguard server I have set up in location B which is reachable via the internet on a public ddns name [done]
set up the eth1 port in such a way that the whatever device I plug in there thinks that it’s basically in location B [no idea how to do]
Assume that this is all the configuration currently on the device (wlan connection and wireguard tunnel), all firewall rules are deleted, no manual routing, no nating, etc
What confuses me a little bit is how routing should even work since i need a default gateway pointing out the default gateway of location A, to be able to reach the ddns name and set up the tunnel but then technically any device connected on eth1 should have a default gateway pointing to the wireguard tunnel_
You are putting many restrictions on the requirements in terms of setup.
Better if you state what the users coming on the hex wifi can and cannot do.
In other words, more information and clarity is required.
a1. all maplite users from wifi ending up at WG server device must go out the remote site for internet
OR
a2. all maplite users from wifi ending up at WG server device must go out the remote site to access subnets at the remote site?
c. ether1 of the maplite will be connected via ether1 to a Main router
d. the maplite itself gets a PRIVATE IP? from the main router or a statically assigned Private IP?
e. the wifi users get a Private IP via DHCP from the main router.
f. is the subnet the same for both wifi user and maplite
g. is there a management or base vlan for the admin to control smart devices…
h. is the reachable WG server a MT device or a different device or a third party server
----> diagrams help
----> config helps /export file=anynameyouwish