Channel log from 24 April 2016 (all times are UTC)

kev has joined IRC (kev!49a4fcd2@gateway/web/freenode/ip.73.164.252.210)

01:55

<kev>

Hi Istarted a chat last week with some one on here in Portland about a capstone project I'm doing using LTSP. It had to do with equipping classrooms in third world countries. Is that individual on line presently?

gwd_ has joined IRC (gwd_!bed53089@gateway/web/freenode/ip.190.213.48.137)

03:51

<gwd_>

hi, newbie here ... can i get help with dhcp on virtual box for setting up an ubuntu ltsp server? my virtual network card is recognised but not my virtual NAT card to connect to the Internet

03:52

<maldridge>

if I understand you correctly you are trying to virtualize an ltsp server?

03:53

<gwd_>

yes, for test purposes, so i can deploy to an actual lab ... i've got the ltsp part to work, but not the internet part

03:54

<maldridge>

in theory you can bind the external adapter to the VM and it will "just work"

04:01

<gwd_>

installing ubuntu using an adapter with internet connection went fine, but the internal adapter was added afterwards used the interface address i set in dhcp.conf and the external adapter isnt accessible anymore

04:02

<maldridge>

if you type "ip link" within the vm do you see the number of adapters you expect to see

04:03

<gwd_>

i want access to both adapters, the internal one to give out addresses to terminals and the external one for internet connectivity

04:04

<maldridge>

yes, do you actually have both still attatched to the VM

04:05

<gwd_>

yes, ip link (and ip addr) shows both adapters, but the external one is using a random address i never set in dhcp.conf

04:06

i set the internal network to 10.10.10.0 but the external one is using 10.0.3.0; i don't know where it's getting that address from

04:07

<maldridge>

that sounds like virtualbox NAT

04:10

<gwd_>

yes, i had virtual box use NAT for the external network to access internet from my host computer; it worked before on the classic ltsp install, but i'm using standalone ltsp on the latest ubuntu (xenial) now

04:11

so i don't know what changed between the classic and the recent version; even the interface naming is different: no more eth0, etc

04:20

the previous classic installation (using the alternate distro, 12.04) pretty much "just worked", like you said; this latest version requires some "dhcp surgery"

04:29

<maldridge>

hmm, not sure as I don't really run ubuntu anymore

04:29

it could be something in your vbox install (likely) or something in your ubuntu config (less likely)

04:37

<gwd_>

well, i haven't installed the virtualbox guest additions as yet, so i'll give that a crap shoot; i hope transitioning to a physical ltsp implementation would be more straightforward, like the virtualised classic install was

alkisg: ltsp-pnp seems requires/assumes that the internal adapter is addressed to 192.168.67.1; makes me wonder if i should have left the default network ip scheme instead of basing it on network10.10.10.0

alkisg: i'd begun reinstalling ubuntu on virtualbox but starting off with both adapters setup this time, instead of using one then swapping in a second, and the installation seems to be progressing just fine with both cards detected! hopefully i'll get coherent results when i finish with the standalone ltsp (and sticking with the default addressing for the while); i think i'll fire up a single adapter ltsp-pnp install for comparison late

(learn [<channel>] <key> as <value>) -- Associates <key> with <value>. <channel> is only necessary if the message isn't sent on the channel itself. The word 'as' is necessary to separate the key from the value. It can be changed to another word via the learnSeparator registry value.