[prev in list] [next in list] [prev in thread] [next in thread]
List: ltsp-discuss
Subject: Re: [Ltsp-discuss] 2 NIC chrooted Fat Client NAT Problems
From: Dashamir Hoxha <dashohoxha () gmail ! com>
Date: 2019-02-25 11:17:23
Message-ID: CAMucfLxXDWKMB8M9jXfjafJz2K3FCGiDTXNj1Vo6ts_tv8uL2g () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Mon, 25 Feb 2019, 11:29 J O'Connor, <jfo192877@gmail.com> 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
>
[Attachment #5 (text/html)]
<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Mon, 25 Feb 2019, 11:29 J O'Connor, <<a \
href="mailto:jfo192877@gmail.com">jfo192877@gmail.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div \
dir="ltr">Hello!<div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>I really appreciate any \
help!</div><div><br></div><div>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):</div><div><br></div><div>network:</div><div> version: 2</div><div> \
renderer: networkd</div><div> ethernets:</div><div> \
enp0s3:</div><div> addresses:</div><div> - \
<a href="http://192.168.2.50/24" target="_blank" \
rel="noreferrer">192.168.2.50/24</a></div><div> gateway4: \
192.168.2.1</div><div> nameservers:</div><div> \
addresses: [127.0.0.53, 192.168.2.1, 192.168.1.1, 1.1.1.1]</div><div> \
routes:</div><div> - to: <a href="http://192.168.2.0/24" \
target="_blank" rel="noreferrer">192.168.2.0/24</a></div><div> \
from: <a href="http://192.168.67.0/24" target="_blank" \
rel="noreferrer">192.168.67.0/24</a></div><div> via: \
192.168.2.50</div><div><br></div><div> enp0s8:</div><div> \
addresses:</div><div> - <a href="http://192.168.67.1/24" \
target="_blank" rel="noreferrer">192.168.67.1/24</a></div><div> \
nameservers:</div><div> addresses: [127.0.0.53, \
192.168.2.1, 192.168.1.1, 1.1.1.1]</div><div> routes:</div><div> \
- to: <a href="http://192.168.67.0/24" target="_blank" \
rel="noreferrer">192.168.67.0/24</a></div><div> from: \
192.168.2.1</div><div> via: \
192.168.2.50</div><div><br></div><div>I also have dnsmasq set with --no-proxy-dhcp, \
and net.ipv4.ip_forward=1 in /etc/sysctl.conf.</div><div><br></div><div>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. \
</div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">As \
Alkis mentioned, the NAT part of your configuration may be broken. You can check it \
with something like this:</div><div dir="auto">`iptables-save | grep masquerade` or \
just `iptables-save`</div><div dir="auto"><br></div><div dir="auto"><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div \
dir="ltr"><div><br></div><div>Thanks again for all the help that's already out \
there!</div><div><br></div><div><br></div></div> \
_____________________________________________________________________<br> \
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:<br> <a \
href="https://lists.sourceforge.net/lists/listinfo/ltsp-discuss" rel="noreferrer \
noreferrer" target="_blank">https://lists.sourceforge.net/lists/listinfo/ltsp-discuss</a><br>
For additional LTSP help, try #ltsp channel on <a href="http://irc.freenode.net" \
rel="noreferrer noreferrer" target="_blank">irc.freenode.net</a><br> \
</blockquote></div></div></div>
_____________________________________________________________________
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
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic