IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 29 July 2020 (all times are UTC)
| 02:12 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 02:36 | lucascastro has left IRC (lucascastro!~lucascast@177-185-139-222.dynamic.isotelco.net.br, Read error: Connection reset by peer) | |
| 02:36 | lucas_ has joined IRC (lucas_!~lucascast@177-185-139-222.dynamic.isotelco.net.br) | |
| 04:27 | <alkisg> Vercas: you can just put stuff under [mac:address] in ltsp.conf, so that you don't even need to check for mac-address
| |
| 04:27 | There's no need to re-implement ltsp.conf yourself..
| |
| 11:08 | zerkalo has joined IRC (zerkalo!myricae@gateway/shell/hashbang/x-xkyxkczipuvpwqzr) | |
| 11:09 | mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Ping timeout: 240 seconds) | |
| 12:23 | mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy) | |
| 12:38 | <Vercas> alkisg: What I was trying to do is figuring out the boot interface so I can create a VLAN interface on top of it.
| |
| 12:39 | That part was successful. Now I'm trying to figure out how to instance a DHCP client.
| |
| 12:41 | <alkisg> Vercas: it's `echo $MAC_ADDRESS` from ltsp.conf, e.g. POST_INIT_CREATE_VLAN="my-create-vlan $MAC_ADDRESS"
| |
| 12:42 | <Vercas> Ah, interesting.
| |
| 12:42 | Well, I figured it out anyway, but that's really good to know!
| |
| 12:42 | <alkisg> Vercas: where will sshfs be connected to, the "real" lan or the vlan?
| |
| 12:42 | <Vercas> Real LAN.
| |
| 12:42 | Is SSHFS instanced under the user account?
| |
| 12:43 | <alkisg> So the users will have access to the real lan
| |
| 12:43 | No, it's ran as root
| |
| 12:43 | <Vercas> Ow, then that's good.
| |
| 12:43 | I don't mind the system accessing my LAN.
| |
| 12:43 | What I want is the guest account's own stuff to be limited to my guest VLAN.
| |
| 12:43 | This works perfectly with a static IP.
| |
| 12:43 | But I don't know how to reserve two static IPs for the same MAC in OpenWrt.
| |
| 12:43 | <alkisg> Wouldn't it be simpler to just force a proxy for them?
| |
| 12:44 | And drop all other lan packets?
| |
| 12:44 | <Vercas> Not really, since I've already managed to make everything work except the DHCP client. :D
| |
| 12:44 | <alkisg> dhcp client in what interface, you'll create a second interface?
| |
| 12:45 | <Vercas> The new network namespace for guests has an interface for the guest VLAN.
| |
| 12:45 | That interface.
| |
| 12:45 | Not the boot interface, of course.
| |
| 12:45 | <alkisg> What's that interface name?
| |
| 12:45 | <Vercas> Simply "guest".
| |
| 12:46 | <alkisg> What kind of device is it?
| |
| 12:46 | <Vercas> VLAN
| |
| 12:46 | <alkisg> ip create vlan?
| |
| 12:46 | <Vercas> ip link add link "$BOOTIF" name guest type vlan id 1234
| |
| 12:47 | <alkisg> Can you assign an ip to that via network-manager?
| |
| 12:47 | <Vercas> Hm, I don't know how.
| |
| 12:47 | That interface is moved to the guest namespace.
| |
| 12:47 | <alkisg> Click on the network manager menu
| |
| 12:48 | <Vercas> NetworkManager is running in the root namespace.
| |
| 12:48 | <alkisg> Hmm
| |
| 12:48 | <Vercas> It might be possible to start another instance of it.
| |
| 12:48 | <alkisg> dhclient needs root, right?
| |
| 12:48 | <Vercas> Yes, it needs to send raw Ethernet packets.
| |
| 12:49 | <alkisg> (03:47:53 PM) Vercas: That interface is moved to the guest namespace. ==> when, by which hook?
| |
| 12:49 | Did you create the guest namespace with pam_exec?
| |
| 12:55 | <Vercas> No, I've got a script that runs as root.
| |
| 12:55 | <alkisg> When?
| |
| 12:55 | <Vercas> The pam module I use just uses an existing namespace.
| |
| 12:55 | Right now I run it manually as root.
| |
| 12:55 | I can make it run whenever needed.
| |
| 12:56 | <alkisg> OK, then why not run dhclient from that script too
| |
| 12:56 | <Vercas> I tried to, nothing happens.
| |
| 12:56 | Not 100% sure why.
| |
| 12:59 | ip netns exec guest dhclient -pf /run/dhclient_guest.pid guest
| |
| 12:59 | Nothing happens.
| |
| 12:59 | It doesn't exit either.
| |
| 13:01 | <alkisg> Try to run /usr/lib/klibc/bin/ipconfig -n guest instead
| |
| 13:01 | It's more verbose
| |
| 13:05 | <Vercas> Will try that.
| |
| 13:06 | It outputs only one line so far: IP-Config: guest hardware address bla:bla:bla mtu 1500 DHCP RARP
| |
| 13:17 | Okay, this is odd.
| |
| 13:17 | Apparently no traffic gets out.
| |
| 13:22 | So this seems to be a limitation of my hypervisor.
| |
| 13:22 | On real hardware, it works.
| |
| 13:23 | dhclient works perfectly there.
| |
| 13:32 | If all this works, I'll add it to the wiki.
| |
| 13:32 | I'm sure others will find this useful. :)
| |
| 14:12 | My test physical machine has a borked trackpad so I could only test with a tty login, not a graphical login.
| |
| 14:13 | With tty login it works perfectly.
| |
| 14:13 | DHCP client works, I get an IP address and a route.
| |
| 14:13 | DNS works too.
| |
| 14:49 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 15:19 | lucas_ has left IRC (lucas_!~lucascast@177-185-139-222.dynamic.isotelco.net.br, Read error: Connection reset by peer) | |
| 15:20 | lucascastro has joined IRC (lucascastro!~lucascast@186.193.183.215.jupiter.com.br) | |
| 15:40 | mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Ping timeout: 256 seconds) | |
| 16:58 | lucascastro has left IRC (lucascastro!~lucascast@186.193.183.215.jupiter.com.br, Ping timeout: 240 seconds) | |
| 17:05 | mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy) | |
| 17:14 | lucascastro has joined IRC (lucascastro!~lucascast@177-185-131-162.corp.isotelco.net.br) | |
| 18:10 | lucascastro has left IRC (lucascastro!~lucascast@177-185-131-162.corp.isotelco.net.br, Ping timeout: 240 seconds) | |
| 18:21 | pw77 has joined IRC (pw77!a7152a19@167.21.42.25) | |
| 18:22 | <pw77> Howdy, can I ask for help in troubleshooting an LTSP5 issue here or is this just for the latest version of LTSP?
| |
| 18:26 | <vagrantc> you can try :)
| |
| 18:26 | <pw77> True ;-)
| |
| 18:29 | I have a working LTSP5 system running Mate 18.04 and the Greek PPA version of LTSP. Some model of machines boot fine and work well. Some models of Dell Optiplexes boot very slowly and get stuck at "A Start job is running for Raise Network interfaces". It eventually gets past that point after 5mins, but then the system is really slow and
| |
| 18:29 | unresponsive.
| |
| 18:29 | These same systems worked fine under Ubuntu 16.04 and the non-Greek version of LTSP
| |
| 18:44 | lucascastro has joined IRC (lucascastro!~lucascast@189.89.8.207) | |
| 19:30 | <alkisg> pw77: there's no "greek version of ltsp"; the greek school ppa just has the most recent ltsp (which gets to debian/ubuntu a bit later)
| |
| 19:30 | !netplan
| |
| 19:30 | <ltspbot> netplan: To work around https://bugs.launchpad.net/netplan/+bug/1763608/comments/47, either update to a new LTSP version, or put this in lts.conf: INIT_COMMAND_RM_NETPLAN="rm -rf /lib/systemd/system-generators/netplan /run/netplan"
| |
| 19:30 | <alkisg> Try this ^
| |
| 19:31 | How much RAM do these systems have? Newer ubuntu versions need more ram, so they get unresponsive if there's not enough ram and swap gets used
| |
| 19:40 | mmarconm has joined IRC (mmarconm!~Marcelo@unaffiliated/mmarconm) | |
| 19:43 | <alkisg> The output of `dmesg` might also help, in case there are kernel messages regarding the issue...
| |
| 19:43 | (on the client)
| |
| 19:48 | pw77 has left IRC (pw77!a7152a19@167.21.42.25, Ping timeout: 245 seconds) | |
| 20:16 | woernie has joined IRC (woernie!~werner@pd9f60310.dip0.t-ipconnect.de) | |
| 20:34 | woernie has left IRC (woernie!~werner@pd9f60310.dip0.t-ipconnect.de, Ping timeout: 256 seconds) | |
| 20:43 | mmarconm has left IRC (mmarconm!~Marcelo@unaffiliated/mmarconm, Quit: Leaving) | |
| 23:31 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |