IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 5 March 2019   (all times are UTC)

01:07gdi2k has joined IRC (gdi2k!~gdi2k@58.69.160.28)
02:16mmarconm has joined IRC (mmarconm!~mmarconm@unaffiliated/mmarconm)
02:41vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 264 seconds)
02:41vagrantc_ is now known as vagrantc
02:50mmarconm has left IRC (mmarconm!~mmarconm@unaffiliated/mmarconm, Quit: Leaving)
03:21vagrantc_ has joined IRC (vagrantc_!~vagrant@unaffiliated/vagrantc)
05:30vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Remote host closed the connection)
05:30vagrantc_ is now known as vagrantc
06:30ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:20spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Ping timeout: 255 seconds)
07:38statler has joined IRC (statler!~Georg@p5489790B.dip0.t-ipconnect.de)
08:09kjackal has joined IRC (kjackal!~quassel@2a02:587:3111:6500:c866:51b3:9bd4:7e90)
09:16vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
09:17statler has left IRC (statler!~Georg@p5489790B.dip0.t-ipconnect.de, Remote host closed the connection)
10:08kjackal has left IRC (kjackal!~quassel@2a02:587:3111:6500:c866:51b3:9bd4:7e90, Remote host closed the connection)
10:10kjackal has joined IRC (kjackal!~quassel@2a02:587:3111:6500:96d:3bb7:6ac1:b473)
10:15statler has joined IRC (statler!~Georg@gwrz3.lohn24.de)
12:26book` has left IRC (book`!~book`@68.ip-149-56-14.net, Quit: Leaving)
12:29book` has joined IRC (book`!~book`@68.ip-149-56-14.net)
13:49
<JuJUBee>
So I migrated to a new server, users homes mounted via nfs for now. Problem is students cannot get out of LAN. Can ping everything on LAN but nothing off. I think default gw is set to ltsp-server not my gateway device. Where is that configured in ltsp?
13:52
DO I need to re-image if I make changes to /etc/dnsmasq.d/ltsp-server-dnsmasq.conf ?
13:53
<||cw>
shouldn't need to reimage.
13:53
<JuJUBee>
thanks
13:53
<||cw>
make sure your proxy dchp settings are right. personally I don't sue them, I just put the needed pxe config options on the real dhcp server
13:54
<JuJUBee>
Isn't dnsmasq handling dhcp now?
13:54
<||cw>
which also lets me easily override the setting on a per mac basis
13:55
idk what you did, so you tell me
13:55
do you have another dhcp server?
13:55
<JuJUBee>
I thought with single nic I had to use dnsmasq
13:55
I turned off my other dhcp server
13:56
<||cw>
ok, then it is. so just need the gateway set right in that config
13:56
<JuJUBee>
ltsp-server-dnsmasq.conf ?
13:57
I have dhcp-option=eno1,3,192.168.67.200
13:57
<||cw>
and its regular config, idk where it's set, as I said I don't use that. for me it's simpler to set it in my main dhcp
14:01
<JuJUBee>
by regular config you mean lts.conf? or dnsmasq.conf?
14:04
my ltsp-server-dnsmasq.conf and /var/lib/tftpboot/images/amd64/lts.conf are identical to same configs on old server. I can't even ping 8.8.8.8 using new server ltsp client
14:04
Must be default gateway problem.
14:11
<||cw>
when in doubt, check everything. do non-ltsp clients get the right gateway?
14:12
<alkisg>
JuJUBee: turn on the other dhcp server, and run sudo ltsp-config dnsmasq --overwrite
14:12
proxydhcp mode means you need ANOTHER dhcp server
14:12
If you want to make the ltsp server the primary dhcp server, then you need to configure the gateway from dnsmasq.conf on your own
14:12
It's a single line, you can google it
14:12
But noone uses that setup
14:13
1 nic = proxydhcp
14:13
2 nic = real dhcp
14:13
<JuJUBee>
I have 1 nic
14:13
<alkisg>
you try to do 1 nic with real dhcp
14:13
Yes, I understand, re-read and ask again if you didn't understand what I wrote
14:13
<JuJUBee>
strange, old server also only had 1 nic and dhcp server was off.
14:14
<alkisg>
(03:55:34 PM) JuJUBee: I turned off my other dhcp server
14:14
So your other dhcp server was off, and not it's off again?
14:14
<JuJUBee>
correct, some time ago
14:14
still off
14:14
<alkisg>
Were you using isc-dhcp or dnsmasq?
14:14
<JuJUBee>
isc
14:15
<alkisg>
OK, read your configuration and see the line that sets the gateway
14:15
You need a similar line for dnsmasq as well
14:15
<JuJUBee>
in dnsmasq.conf ?
14:15
<alkisg>
It's just a single line, I'm sure if you google "set gateway dnsmasq" you'll find it in 1 minute
14:15
In /etc/dnsmasq.d/jujubee.conf
14:15
It's best to use a separate file for custom lines
14:17
By default, dhcp servers set their selves as the gateway; to set another gateway, you need 1 line, both in dnsmasq and in isc-dhcp
14:18
<JuJUBee>
I have dhcp-option=enp0s3,3,192.168.67.200 already in ltsp-server-dnsmasq.conf
14:18
<alkisg>
That's why proxydhcp setup is so much easier, people don't need to read up on dhcp configuration
14:18
Are you using epoptes?
14:18
<JuJUBee>
didn't you say noone uses that?
14:18
yes
14:19
<alkisg>
I said noone uses YOUR setup
14:19
People use proxydhcp with 1 nic
14:19
You use real dhcp with 1 nic
14:19
So YOUR setup is the very strange one
14:19
<JuJUBee>
How am I using real dhcp?
14:19
<alkisg>
Oh my
14:19
<JuJUBee>
maybe I am confused by the docs
14:19
<alkisg>
OK let's take it from the start
14:19
Normally, the dhcp server is a router
14:20
Do you have a router that has a dhcp server?
14:20
<JuJUBee>
Not at the moment. I used to a while ago
14:20
<alkisg>
What is your gateway device?
14:20
<JuJUBee>
An ubuntu box
14:20
running iptables
14:21
192.168.67.200
14:21
<alkisg>
OK, so the "correct" thing would be to put the dhcp server there
14:21
It's the one giving internet; it should also be the one to hand out ip addresses
14:21
So, you would make that 192.168.1.1
14:22
And put the ltsp server at 192.168.1.2
14:22
And then use proxydhcp in the ltsp server
14:22
I.e.: sudo ltsp-config dnsmasq --overwrite
14:22
<JuJUBee>
So only 2-nic requires the 67 network?
14:22
<alkisg>
And that's all
14:22
Yes
14:22
<JuJUBee>
OK, thanks for clarifying that for me.
14:23
<alkisg>
The .67 network has logic for 2 nic setup, with nat forwarding etc
14:23
<JuJUBee>
I am more familiar with isc-dhcp anyway. Can just reenable old configs.
14:23
<alkisg>
Right
14:23
You can also avoid proxydhcp as well
14:24
sudo ltsp-config dnsmasq --overwrite --no-proxydhcp
14:24
Since your dhcp server is configurable
14:24
But whatever, both will work, just revert to your old setup
14:27
If you want my advice, make your dhcp server a dummy one, similar to a dummy router/dhcp server, and use proxydhcp,
14:27
that way, when we update the proxydhcp setup in ltsp, you won't have to reconfigure anything
14:27
This setup works for both your use case AND for people that have dummy routers, so it's easier to have the same setup in all situations
14:27
(well, if you do want to avoid extra configurations...)
14:28
In this case, your dhcp server must not send a boot filename; the ltsp server will send it
14:42
<JuJUBee>
so the isc-dhcp server just sends the ip info?
14:43spaced0ut has joined IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut)
14:56
<Hyperbyte>
alkisg, hey... what do you think...
14:56
We're using fat clients in the office, and I need to configure some laptops to log in remotely
14:56
Now I'm thinking there's two viable options...
14:57
Load the fat client image onto the laptops SSD, and use OpenVPN to connect to the office during boot
14:57
Everything should then work like it does in the office
14:58
Or, load x2go locally and connect via that.
14:58
I'm thinking the 2nd one is a lot easier to set up, but the 1st one would probably give a lot better results for audio/video applications.
14:59
Any thoughts/experiences in this regard?
15:00
Although the 1st one might be tricky when used over wifi for example, because that would need to be set up first.
15:44
<alkisg>
Hyperbyte: if the connection is reliable, sshfs would work better for multimedia, sure
15:44
Setting up vpn or wifi makes no difference
15:44
It's just a net connection
15:44
Just make sure it's a system connection, not a user one
16:02
Btw, I prefer rdp over x2go nowadays, as x2go had a lot of problems with stale sessions
16:06
<Hyperbyte>
RDP on Linux? I must be behind a little...
16:06
Does RDP support two-way audio? It does huh?
16:19
<JuJUBee>
alkisg, if I run ltsp-config dnsmasq --overwrite I see a dhcp-range directive is that a problem if I am also running isc-dhcp on my gateway?
16:22
also, in the "dhcp-range=10.0.2.2,proxy" line, do I need to uncomment? should I change 10.0.2.2 to my real gateway IP?
16:31
Ah, I get it now. the 10.0.2.2 needs to be my ltsp server IP add and that line needs to be uncommented to use proxyDHCP. the ,proxy tells ltsp server to respond to dhcp with only additional info, ie boot files while the real dhcp server gives IP.
16:32
<alkisg>
Hyperbyte: well, x2go is "x", I don't think it'll continue living in the wayland era...
16:33
JuJUBee: right; that line should already be uncommented
16:34
<JuJUBee>
It was not
16:34
<alkisg>
Did you pass --no-proxy-dhcp?
16:34
Can I see?
16:34
<JuJUBee>
no
16:34
<alkisg>
Run: sudo ltsp-config dnsmasq --overwrite
16:34
And pastebin the result
16:34
cat /etc/dnsmasq.d/ltsp-server-dnsmasq.conf | nc termbin.com 9999
16:34
<JuJUBee>
I ran that command and had to uncomment the line
16:35
<alkisg>
That would be a bug then
16:35
One I've never seen
16:35
Hence the confirmation request
16:35
<JuJUBee>
I have students that just logged in... that going to be a problem?
16:35
<alkisg>
No
16:35
Unless you modified it afterwards
16:35
In which case, the modifications will be lost
16:35
Logged in clients are only affected if you --enable-dns
16:36
They don't use dnsmasq after boot otherwise
16:37
<JuJUBee>
done
16:38
<alkisg>
URL?
16:38
<JuJUBee>
termbin.com/zk8x
16:39
<alkisg>
Is that on ubuntu 18.04 with the greek schools ppa?
16:39
<JuJUBee>
yes
16:39
fresh install yesterday
16:39
followed docs
16:43
<alkisg>
JuJUBee: it does sound like a bug, could you try this?
16:43
wget https://termbin.com/iwn0f -O /tmp/testproxy && sh /tmp/testproxy
16:43
Does this show a line with the correct dhcp-range?
16:46
<JuJUBee>
is that a -zero or -"oh"
16:48
<alkisg>
Zero
16:49
Which one, the wget parameter?
16:49
That's a capital oh
16:49
<JuJUBee>
I don't see any IP in the output (excpet maybe termbin.com 5.39.93.71 ?)
16:49
<alkisg>
Did you download it correctly? md5sum /tmp/testproxy
16:49
203beea9816001e5070c3a9f2736265e /tmp/testproxy
16:50
sh /tmp/testproxy
16:50
dhcp-range=10.161.254.0,proxy
16:50
If it doesn't show a line like that for you, then the issue is there, in that function
16:50
<JuJUBee>
Does it matter that I am using the 192.168.67.0 network?
16:50
<alkisg>
Yes
16:51
That network doesn't work as a proxy, it works as a real dhcp
16:51
So if you're using that, do change it, as you now have 2 dhcp servers
16:51
<JuJUBee>
isc-dhcp is handing out that network
16:51
<alkisg>
And dnsmasq too
16:51
After that command
16:52
<JuJUBee>
or do you mean in the dhcp-range command?
16:52
<alkisg>
grep range /etc/dnsmasq.d/ltsp-server-dnsmasq.conf
16:52
Do you have the 67 network there?
16:52
It's there by default
16:52
<JuJUBee>
yes it was there by default
16:53
<alkisg>
Right
16:53
OK so you just misunderstood the docs
16:53
Do avoid the .67 network, it has special meaning in ltsp
16:53
So it can cause you numerous issues, and confuse people that try to support you
16:54
<JuJUBee>
when I asked about the dhcp-range=10.0.2.2 I was asking if 10.0.2.2 needed to be the IP of the ltsp server, currently 192.168.67.1
16:54
so that really needs to be 10.0.2.2 or something else other than 192.168.67.* ?
16:55
<alkisg>
I don't know how else to say it:
16:55
"dont use the 67 network unless you have 2 nics"
16:55
(04:21:54 PM) alkisg: So, you would make that 192.168.1.1
16:55
(04:22:06 PM) alkisg: And put the ltsp server at 192.168.1.2
16:56
<JuJUBee>
ugh, so I need to re-address my room then. I had originally used the .67 because that is my birth year doh!
17:03
so just to be clear, dhcp-range=192.168.1.1,proxy where the ltsp server ip is 192.168.1.2 (or any 2 IPs in whatever subnet I decide to use...) I am already using the 192.168.1.0/24 network
17:11JuJUBee has left IRC (JuJUBee!~knichel@24.148.115.153, Ping timeout: 240 seconds)
17:17statler has left IRC (statler!~Georg@gwrz3.lohn24.de, Remote host closed the connection)
17:25JuJUBee has joined IRC (JuJUBee!~knichel@24.148.115.153)
17:52kjackal has left IRC (kjackal!~quassel@2a02:587:3111:6500:96d:3bb7:6ac1:b473, Ping timeout: 258 seconds)
18:09
<alkisg>
JuJUBee: yes, any other network and any other IPs than the .67 network will do just fine
18:21
<JuJUBee>
Back up and running on the .6.0/24 network. Thanks alkisg
18:21
<alkisg>
np
19:29vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
19:37kjackal has joined IRC (kjackal!~quassel@2a02:587:3111:6500:96d:3bb7:6ac1:b473)
20:02adrianor1 has joined IRC (adrianor1!~adrianorg@177.18.49.170)
20:05adrianorg has left IRC (adrianorg!~adrianorg@177.156.60.170, Ping timeout: 245 seconds)
20:16adrianor1 has left IRC (adrianor1!~adrianorg@177.18.49.170, Ping timeout: 268 seconds)
20:24lucascastro has joined IRC (lucascastro!~lucascast@177-185-139-253.isotelco.net.br)
20:32adrianorg has joined IRC (adrianorg!~adrianorg@179.177.212.44.dynamic.adsl.gvt.net.br)
20:48vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 252 seconds)
20:49vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
21:12vagrantc_ has joined IRC (vagrantc_!~vagrant@unaffiliated/vagrantc)
21:27kjackal has left IRC (kjackal!~quassel@2a02:587:3111:6500:96d:3bb7:6ac1:b473, Ping timeout: 258 seconds)
21:49vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 252 seconds)
21:49vagrantc_ is now known as vagrantc
21:53ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)
22:17vagrantc_ has joined IRC (vagrantc_!~vagrant@unaffiliated/vagrantc)
22:37lucas_ has joined IRC (lucas_!~lucascast@186.193.177.105.jupiter.com.br)
22:40lucascastro has left IRC (lucascastro!~lucascast@177-185-139-253.isotelco.net.br, Ping timeout: 252 seconds)
23:02lucas__ has joined IRC (lucas__!~lucascast@177-185-139-253.isotelco.net.br)
23:04lucas_ has left IRC (lucas_!~lucascast@186.193.177.105.jupiter.com.br, Ping timeout: 252 seconds)
23:28lucas__ is now known as lucascastro
23:30lucascastro has left IRC (lucascastro!~lucascast@177-185-139-253.isotelco.net.br, Quit: Leaving)
23:30lucascastro has joined IRC (lucascastro!~lucascast@177-185-139-253.isotelco.net.br)