Re: 2 NIC chrooted Fat Client NAT Problems

On Mon, 25 Feb 2019, 11:29 J O'Connor, <[email protected]> wrote:

> Hello!
>
> Thanks for all the work and great information out there already -- I've
> worked through a ton of the resources out there along the way of trying to
> fix this, but none of it seems to work.
>
> I went back to square one and have installed everything clean from the
> wiki tutorial, but still running into the same problems: I can't get my
> clients to connect to anything beyond the WAN facing NIC on the Server.
>
> All of this is running in Ubuntu 18.04 on Virtual Machines (the server
> will stay Virtual, clients will be deployed into a school lab with amd64
> terminals). The network adaptors are attached in Bridge mode, on the same
> ethernet, and using virtio-net on the Server, and in Bridge mode as an
> Intel1000 on the Client.
>
> I really appreciate any help!
>
> Here's the contents of my /etc/netplan .yaml (not sure if the routes help,
> but on an earlier machine configuration, they were part of getting it to
> work before things went the other direction):
>
> network:
>      version: 2
>      renderer: networkd
>      ethernets:
>          enp0s3:
>               addresses:
>                - 192.168.2.50/24
>                gateway4: 192.168.2.1
>                nameservers:
>                    addresses: [127.0.0.53, 192.168.2.1, 192.168.1.1,
> 1.1.1.1]
>                 routes:
>                     - to: 192.168.2.0/24
>                       from: 192.168.67.0/24
>                       via: 192.168.2.50
>
>         enp0s8:
>              addresses:
>              - 192.168.67.1/24
>              nameservers:
>                   addresses: [127.0.0.53, 192.168.2.1, 192.168.1.1,
> 1.1.1.1]
>              routes:
>               - to: 192.168.67.0/24
>                 from: 192.168.2.1
>                 via: 192.168.2.50
>
> I also have dnsmasq set with --no-proxy-dhcp, and net.ipv4.ip_forward=1 in
> /etc/sysctl.conf.
>
> Any other settings anyone wants to see, I can share -- or if there are
> some good checks I should be running to try and follow traffic beyond just
> 'ping', I'd really appreciate learning how to track what's going on here
> better.
>

As Alkis mentioned, the NAT part of your configuration may be broken. You
can check it with something like this:
`iptables-save | grep masquerade` or just `iptables-save`


> Thanks again for all the help that's already out there!
>
>
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>

_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net