Stack Exchange
log in

ylluminate

 Discussion between ylluminate and hey…

Imported from a comment discussion on askubuntu.com/questions/...
ylluminate
May 22, 2020 15:48
Made sure to have wpasupplicant installed and then did a sanity check with rfkill list and iwconfig (apt install wireless-tools; iwlist wlan0 scan|grep ESSID), saw that things were looking alright and then limited the netplan conf and did a netplan --debug generate; netplan apply; systemctl daemon-reload). curl https://wtfismyip.com/text/ip showed what I wanted to see at that point as did ip addr so it looks solid.
ylluminate
May 22, 2020 15:48
So good news, wifis worked great. At first I had a problem with it not prioritizing the strongest AP for some reason when I put in a list of multiple access points, but when I just put one in it did connect.
ylluminate
May 22, 2020 14:56
FYI, I found a handy working script that emails IP address changes out: github.com/begleysm/ipwatch
ylluminate
May 22, 2020 14:55
Right, I thought it might be 3 but I was just curious about it and didn't look it up again yet. Yes, I'm going to add the wlan0 today if possible - I'm just out of time on this and so if I run into any hiccups I might have to deploy as-is until more time comes up later.
ylluminate
May 22, 2020 03:57
so far it seems to be resilient and able to deal with isp outages and reboots
ylluminate
May 22, 2020 03:57
the only thing that bothers me slightly is that i feel as though the iptables rules may not be robust enough or are doing something not quite right. so many other tutorials and mentions i see for this kind of forwarding seem to be tremendously more complicated... so i'm hoping this is correct and not creating some kind of a problem - somehow...
ylluminate
May 22, 2020 03:56
hey @heynnema and @slangasek thanks so much for your help in this area. i was able to get it working great it appears, here are my steps, please let me know if this makes sense: gist.github.com/ylluminate/1a7a791202beb0d1b4fb81253ada75ac
ylluminate
May 21, 2020 22:46
so @heynnema i'll give that last link a close look when i have a chance this evening. i have to ask myself: what is the best / cleanest option to do this on ubuntu? hopefully this is it vs some of the others i've been exploring as it seems as though it can get rather messy and ufw had some poor results. (cc @slangasek)
ylluminate
May 21, 2020 22:18
basically i want the 192.168.10.1 interface recipient (eg, 192.168.10.2) to be a DMZ for all traffic from eth1, eth2, and eth3
ylluminate
May 21, 2020 22:17
@slangasek then yes, that is the question. i was trying to understand in that i was under the impression that NAT'ing was part of netplan... my goal is for this device to act essentially as an internet "multiplexer" that takes 2 or 3 isps and then hands them all back and forth across eth0 which is the LAN interface...
ylluminate
May 21, 2020 04:24
@slangasek with that update can you advise as to where to go now with this setup to get the routing set properly?
ylluminate
May 20, 2020 22:44
oopsy, thanks, i'm in the middle of a meeting so i keep hopping back and forth
ylluminate
May 20, 2020 22:36
@slangasek ^
ylluminate
May 20, 2020 22:35
so now i'm looking at the following: gist.github.com/ylluminate/1a3c21f127bfe3d4c93fa79effc097c6
ylluminate
May 20, 2020 22:32
i did that: netplan --debug generate; netplan apply; reboot
ylluminate
May 20, 2020 22:32
no kidding. <sigh> i should have thought about that but due to the "cloud" in the name and not grok'ing netplan fully yet, i never dreamed of looking in there - assuming ubuntu / canonical wanted it for something else. -.-
ylluminate
May 20, 2020 22:30
so i've blown that away now
ylluminate
May 20, 2020 22:30
default server install: gist.github.com/ylluminate/990c81a1004739319424962080bbf879
ylluminate
May 20, 2020 22:28
i did not show ip on eth1 for some reason
ylluminate
May 20, 2020 22:28
i got caught up in following some instructions i found re: the other file that i left that
ylluminate
May 20, 2020 22:28
ah, there is a default 50-cloud-init.yaml which could be the problem
ylluminate
May 20, 2020 22:27
i figured as much, just a sanity check due to him saying it was pulling dhcp4 for it as well
ylluminate
May 20, 2020 22:10
i seem to then need to add some routes - but i'm not clear yet on what is correct for netplan in this regard
ylluminate
May 20, 2020 22:08
so @slangasek are you saying i need to have something more along the lines of this for the yml and ip output?: gist.github.com/ylluminate/1a3c21f127bfe3d4c93fa79effc097c6
ylluminate
May 20, 2020 21:58
i'm now getting ipv4 ip on eth1 and eth2
ylluminate
May 20, 2020 21:58
so i commented out the parts on eth1 (pardon the crud floating around due to all of my fiddling): p153.p0.n0.cdn.getcloudapp.com/items/kpuLGbbl/…
ylluminate
May 20, 2020 21:41
hmm, but you are right, it doesn't seem to be pulling an ip from dhcp
ylluminate
May 20, 2020 21:37
so right now i have a local lan plugged into eth1 that should be giving a dhcp lease from a 192.168.0.0 subnet
ylluminate
May 20, 2020 21:36
@slangasek correct - since i'm not onsite the primary eth1 is not up and i'm mostly interested in testing and making sure eth2 is working which is the usb tether since that is going to be the main fallback and really the most important connection ultimately as such.
ylluminate
May 19, 2020 22:40
yep, catch you later, appreciate it!
ylluminate
May 19, 2020 22:37
absolutely, will do. i'm not clear if this chat will even pull him in since it's slug indicates that this is between just us...
ylluminate
May 19, 2020 22:35
right, i've seen his handle and apparently he's more or less "the man" :)
ylluminate
May 19, 2020 22:35
very, yes. it seems there is a lot of confusion as to what netplan can and cannot do even on irc it seems
ylluminate
May 19, 2020 22:34
hi
ylluminate
May 19, 2020 22:27
i would most certainly prefer to use netplan singularly and only at this point without ufw in the mix and if possible...
ylluminate
May 19, 2020 22:26
also please note my ufw remarks: askubuntu.com/questions/1240452/…
ylluminate
May 19, 2020 22:25
@slangasek as noted i added ip output: gist.github.com/ylluminate/6435840c37edc01e82c047c61f4c071b
ylluminate
May 18, 2020 17:38
```
$ nano /etc/ufw/sysctl.conf
# ADD: net/ipv4/ip_forward=1

$ nano /etc/default/ufw
# ADD: DEFAULT_FORWARD_POLICY="ACCEPT"

$ nano /etc/ufw/before.rules
# ADD:
# *nat :POSTROUTING ACCEPT [0:0] -A POSTROUTING -s 10.0.0.0/24 -o eth0 -j MASQUERADE COMMIT
# COMMIT
# # See this for error + adding extra COMMIT: https://lacyc3.eu/ufw-nat-bad-argument-nat

$ ufw allow 22/tcp
$ ufw enable
$ ufw disable && ufw enable
$ ping 1.1.1.1 # works on localhost, but not on LAN computers
```
ylluminate
May 18, 2020 17:37
so this is a little strange yet still. after doing that which was outlined there, I'm still running into problems; this is what I did:
ylluminate
May 18, 2020 15:11
fyi, i'm not yet clear about this, but someone mentioned that they don't THINK netplan does NAT'ing and you have to do the following: devops.ionos.com/tutorials/…
ylluminate
May 18, 2020 06:31
still haven't seen anything from slangasek as of yet - any chance you have a way to send him a friendly ping? perhaps he's just in a different timezone and thus the radio silence.
ylluminate
May 17, 2020 22:40
i updated it with that image and an update note while also commenting on slangasek's answer.
ylluminate
May 17, 2020 20:24
it's surprising that this info is not more readily available / documented for netplan :'(
ylluminate
May 17, 2020 20:24
catch you later and will keep you posted
ylluminate
May 17, 2020 20:23
lol, np. thanks so much for your time. i think it's a routing issue still
ylluminate
May 17, 2020 20:23
but then when i ping 192.168.10.1 it works, but ping 1.1.1.1 times out
ylluminate
May 17, 2020 20:22
so i statically set the test system to be .10.32 as you see with .10.1 as gateway and the dns to 1.1.1.1
ylluminate
May 17, 2020 20:22
the test system net config: p153.p0.n0.cdn.getcloudapp.com/items/eDu6bWLW/…
ylluminate
May 17, 2020 20:20
but doesn't get out to 1.1.1.1
ylluminate
May 17, 2020 20:20
internet works fine on the actual ubuntu system now and the test system pings to 192.168.10.1