I’d have to check my iptables syntax again but I’m not sure you want the FORWARD between the networks unless C has a manual route to get traffic for the 192.168.15.0/24 network back via B. You just want to NAT A behind B’s IP on 192.168.38.0/24. I think the forwards are sending the traffic without doing NAT on A.
this post was submitted on 04 Oct 2024
18 points (100.0% liked)
Linux
48013 readers
865 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
yes, but you really don't want to nat if you dont have to - gets too messy too quickly when direct IP connectivity is right there.
@shadowintheday2@lemmy.world parent comment is correct. check routes on device C. make there is either a default route or a specific route back to A via B.
how could I set up NAT like this ? thanks
Can you post ip r output.
Is your android being used as the modem/tether for device A? (If so adding route 192.168.38.0/24 via _gateway and _gateway dev x0 proto static scope link should allow it to reach C) If using network manager just use the GUI to add the one line in routes. 192.168.38.0 24 yourgateway - it will do the metric on its own.
What are the gateway addresses?
You'd need to add a route from c to a as well, I believe, but I haven't used windows in forever.
(The above is what I've had to do to get a machine behind an android to ping my other devices.)
ip r
default via 192.168.15.1 dev enp3s0 proto dhcp src 192.168.15.32 metric 100
192.168.15.0/24 dev enp3s0 proto kernel scope link src 192.168.15.32 metric 100
192.168.38.0/24 via 192.168.15.21 dev enp3s0
so it seems that without any config, the traffic passes from wlan1 to wlan0's network flawlessly; but traffic from wlan0 network stops at the Android device, even with iptables -P FORWARD ACCEPT, so I'm clueless on what to do next