Debian Configuration :: LTSP How To Link To Another Server
Aug 24, 2010
I have four server :
- the first of them is the router (firewall, htb, squid, etc.)
- the second have installed apache2
- the third sql
- and the last one is LTSP server for 40 client.
When the ThinClient connect to the LTSP server ewerything works good, but i can't see all of them on squid access log. Isee one ip address (LTSP server), but i want to see 40 ip adrresses. The same situation is in htb. It's doesn't work on the thin client. Is there any way to get this work that how i want ?
I've been working on building an LTSP server for diskless booting. I have a tftp server that's booting the system. I followed the steps on [URL] .... to build the LTSP server.
I had to make one change from the guide. I have a cisco router that's acting as the DHCP, I'm not very familiar with Cisco IOS so instead of playing with that, I decided to modify the default file on the PXE.
I commented the kernel append line and added the following instead
I'm mounting the nfs as a rw file system for now. I'm planning to make it read only once I have it working the way I want. In addition to this, I also chroot into the LTSP root and installed lightdm + mate. As I understood what I read, this would boot the environment on the diskless system. All of this seem to work correctly.
What I need to do next is to find a way to setup the LTSP clients to log in by authenticating on the active directory. I understand that the login account used by the LTSP client has to exist on the LTSP server.
I have successfully added the LTSP server as a worksation within the windows domain and I can log into domain accounts from the LTSP server but domain credentials do not work when using an LTSP client, I can only log in if I use an account that exists on the LTSP server. I wanted to know if there is a way to accomplish AD authentication.
Do I have to build an LDAP server on the LTSP server, sync accounts with the Active Directory to be able to log in with AD credentials?
i set up an ltsp server on debian squeeze. after a standard installation, sound doesn't work on clients.
[code]...
when i start iceweasel normally (executed on server side), i get sound on the client. when i start ltsp-localapps iceweasel, i get no sound on flash sites and videos videos.what's wrong ? with local apps, is it possible that the flashplugin-nonfree doesn't talk to alsa ?
How to verify that Debian is running at 100 Mbps or 1000 Mbps? I can view the report from 'ifconfig eth0' but I can't see how fast the link has been established.
I recently set up a Debian-based gateway+router on a remote site. I've installed OpenVPN and made a VPN bridge to another network (that server is also Debian). The main network has all the resources and also a VoIP server (asterisk). Bridge seems to work fine, except that every time a Linksys phone is used to call - after a few seconds I get:
Jul 20 12:16:05 sklad kernel: [403987.817695] eth0: link down Jul 20 12:16:05 sklad kernel: [403987.817939] br0: port 1(eth0) entering disabled state Jul 20 12:16:07 sklad kernel: [403990.113701] eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[Code]....
So whenever the phone is used, network falls down for a few seconds. And of course this breaks the call. There is also another Linksys box (analog-to-voip) and it works fine most of the time. However sometimes this "eth0 link down" happens too. There is nothing more in syslog to analyze, so I don't know where to dig. Physical device of eth0 is D-link DFE520.
SYSTEM INFORMATION socram@t430:~$ lsb_release -a No LSB modules are available. Distributor ID:Debian Description:Debian GNU/Linux 8.2 (jessie) Release:8.2 Codename:jessie
I am *finally* getting around to rebuilding my file-sharing computer. I'll be sharing files with both Linux and Windoze machines. It's a home network, so there's nothing fancy needed. I know I have to tweak my smb.conf file until I'm satisfied with the features and security. I'm using SWAT and I'm starting with a bare-bones conf file. It's not secure but I can see the server and selected files/directories from my other Linux box.
My really dumb question is, do I have to reboot both the server and the client machines every time I change the SAMBA configuration? I thought I just had to stop and restart the SAMBA service in the SWAT software - but then the server disappears from my client. It looks like I need to reboot both machines for the client to see the server.
Currently have a problem with my LTSP server when using a gigabit switch with a megabit thin client.I am using K12LTSP with Fedora 9.The thin clients get most of the way through booting up then I get error messages saying:nfs: server 172.31.6.1 not responding, still trying.I don't get this problem if I use a 100 meg switch though.I have found several forum posts on the internet which all seem to point to the following webpage with a solution:However, when I make the recommended changes It doesnt make a difference.Below is an example of the default file located at /var/lib/tftpboot/ltsp/i386/pxelinux.cfg with its default settings:
I installed in Virtualbox many times and the clients would not connect. The config of the dhcpd.conf was the problem.Now, Everywhere I kept reading it said I had to turn off my hardware routers dhcp. Thats wrong, I have it working with it on and with one network card. Heres the nuts and bolts. Dlink 4100 hardware router assigning address block 192.168.2.200-250 to pcs on the lan. Router is set to reserve and IP for the ltps server nic so it gets the same IP assigned every time from the hardware router. No need to force linux to an ip when it can be set in the router. Then installed LTSP from alt-cd. Once done, dhcp wont run because it conflicts with the hardware dhcp. Found out by trying to restart it and it said stop - Fail when it tried to stop it.
sudo /etc/init.d/dhcp3-server restart So edit /etc/ltsp/dhcpd.conf. sudo gedit /etc/ltsp/dhcpd.conf
Mine attached below: The subnet, as long as the 1st three numbers match the rest of lan setup it will work.(192.168.2.0), rest of my lan is 192.168.2.x. Now notice the range is a different block than the hardware dhcp server uses. So all thin clients that connect will be assigned something 192.168.2.100-150 and all hardware connected pcs will be assigned 192.168.2.200-250 from the hardware router. So no conflicts. Then for the domain name server, set it to the hardware router ip. My hardware router is 192.168.2.2. Set option router to the same as hardware router of 192.168.2.2 Nothing in my dhcpd.conf file is pointing to the ltsp dhcp server. Nothing else had to be edited in the dhcpd.conf Next hurdle I had, after any change of the dhcpd.conf, ip's might have changed and you have to reconfig the ssh and the image. run these 2 commands.
sudo ltsp-update-sshkeys then sudo ltsp-upadte-image then sudo /etc/init.d/dhcp3-server restart
Then thin clients/lan boot pcs all can connect after that.
I have since installed again at work in virtual box, booted from another vbox client and booted from a separate lan pc. Then installed again at home on AMD 3200 Athlon, 1 gig mem. Booted from my main pc PhenomX4, no problems. Pc's must have lan boot available in the bios or net boot available on the network card(most consumer add on cards do not). But most motherboard lan connection do.
I setup Ubuntu 10.10 (edubuntu) along with ltsp. I have an environment with a windows network (192.168.1.0) and a subnet (192.168.0.0) that the new terminal server is on. Everything seemed to be connecting properly, but when I attempted to boot the first client, I get the error message: "Cannot connect to NBD server".
I'm trying to install/configure a LTSP in CentOS 5.3
I have dhcp, nfs and tftp installed, but i can't install/configure XDMCP. I was reading some manuals and "hows to" and all says that, to configure XDMCP, i have to change de atribute "Enable = true" in the file "/etc/X11/gdm/gdm.conf", but i don't have this rute, only "/etc/X11/", gdm folder doesnt' appear :S also... why i can configure XDMCP?
I will be relocating to a permanent residence sometime in the next year or two. I've recently begun thinking about the best way to implement a home-based network. It occurred to me that the most elegant solution might be the use of VM technology to eliminate as much hardware and wiring as possible.My thinking is this: Install a multi-core system and configure it to run several VMs, one each for a firewall, a caching proxy server, a mail server, a web server. Additionally, I would like to run 2-4 VMs as remote (RDP)workstations, using diskless workstations to boot the VMs over powerline ethernet.The latest powerline technology (available later this year) will allow multiple devices on a residential circuit operating at near gigabit speed, just like legacy wired networks.
In theory, the above would allow me to consolidate everything but the disklessworkstations on a single server and eliminate all wired (and wireless) connections except the broadband connection to the Internet and the cabling to the nearest power outlets. It appears technically possible, but I'm not sure about the various virtual connections among VMs. In theory, each VM should be able to communicate with the other as if it was on the same network via the server data bus, but what about setting up firewall zones? Any internal I/O bandwidth bottlenecks? Any other potential "gotchas", caveats, issues? (Other than the obvious requirement of having enough CPU and RAM).Any thoughts or observations welcome, especially if they are from real world experience in a VM environment. BTW--in case you're wondering why I'm posting here, it's because I run Debian on all my workstations/servers (running VirtualBox as a VM for Windows XP on one workstation).
I've just set up an LTSP server, with all its clients on a separate subnet to my main network - the main network is 192.168.1.x, and the LTSP clients are all 192.168.2.x. My LTSP server has 2 NICs, one on each network, and is merrily forwarding normal IP traffic from the clients to the rest of the network. I have a client/server application that has a server on one machine, and clients locate and attach to it using multicast protocols. The server is on the main network, and any other machines on the network can locate and talk to the server quite happily. The LTSP clients, however, cannot - I assume because the multicast communications aren't being forwarded by the LTSP server. How I can get this working?
My 32-bit Ubuntu 9.10 [Karmic Koala] LTSP server has two NICs, one with Dynamic IP set by a DSL modem and the other with static IP of 192.168.0.254. I also have 4 thin Clients that boot from this server without any problems and another computer with Ubuntu 9.04 running some PHP programs with dynamic IP given by the same DSL modem. When I send requests to these PHP programs from thin clients, they all give the LTSP server's dynamic IP as their IP so I cannot trace who has sent this request to response back.
I actually know this is logical. Because the requests are sent by a program that's actually running on the LTSP server rather than the thin client. But my question is How can I run a program on a thin client with it's own IP? I also should mention that the dhcp3-server service running on the LTSP server has no conflicts with the DSL dhcp on the network and I know that the 4 thin clients get the IPs ranging from 192.168.1.101 through 192.168.1.104 from the dhcp3-server service. Because I can ping them while they're on. but /sbin/ifconfig on them shows info about the LTSP server.
I have an Edubuntu server with two nics joined to the primary windows domain and I can log on with domain credentials and everything is AOK. I used LikewiseOpen 6 to join the server to the primary domain. So, on my Edubuntu server eth1 is connected to the primary domain and has a static IP. eth2 also has a static IP and is the DHCP for the thin client subnet, connected to a switch. IP forwarding is enabled.
So far, so good: I can log on the thin clients with one of the local accounts specified on the Edubuntu server and with that account I can surf the net and, if I supply domain credentials, browse the primary domain. Problem I have is:
I can't work out how to log on to the primary domain with a Active Directory account directly from a thin client. If I try DOMAINuser to log on, after giving the password, the password screen refreshes and 'domainuser@11.*.21.*'s password' appears under the blank password box. The IP in that message is the IP for the subnet and not the primary domain. I feel like I'm miss-understanding some basic simple step but I just can't figure it out.
I'm setting up an LTSP server using Ubuntu 10.4 64bit, and PXE connecting with thin clients using Atheros cards. The ltsp environment is 32bit.
Unfortunately I get an error message with "No interfaces found! Aborting..." and a kernel panic early during PXE boot.
After an enormous amount of investigation, I've narrowed it down to (probably) being the fact that the ltsp chroot environment doesn't have the correct driver for my network card (I believe it's atl1c). The correct driver IS available in Ubuntu, though, as I can successfully boot the thin client from both 64bit and 32bit live CDs and bring up the network interface.
how can I install the correct driver in the PXE environment?
I am trying to install and configure LTSP on a server for a HP thin client to boot off. The version of Ubuntu that I am using is 11.04 x86 and it is a fresh install on a dual core system with 2GB RAM. I followed a guide which comprised of these commands.
sudo apt-get install ltsp-server-standalone openssh-server sudo ltsp-build-client or if your on a 64-bit system with 32-bit machines do sudo ltsp-build-client arch i386 for editing the servers IP values use /etc/ltsp/dhcpd.conf after that you need to restart DHCP server sudo /etc/init.d/dhcp3-server restart and update sshkeys -sudo ltsp-update-sshkeys and if you updated dhcpd.conf then you need to update you image also by typing in terminal ltsp-update-image
Everything seemed to install as it should but when I try to boot from the thin client it just times out and says no DHCP or proxy invites received. I turned DHCP off on the router and even tried another router, but I still get nothing. I am at a bit of a loose end and I hope someone on here can point me in the right direction of where I am going wrong.
I'm running the current release of Debian with the 2.6.26-2 kernel. This is an upgrade from an older (2.4 kernel) series redhat release. One of the things I had working in the older system was a dns server with accompanying monthly update of the root hints file. I tried working through a dns how-to to set this up again, but it seems much has moved around since I last played with this. All of the files listed in the how-to are not where it says they should be. I am looking for a better reference on keeping the dns server running with current server information.
I have installed nfs-kernel-server on the server and nfs-common on the client. Assumeserver 192.168.1.1client 192.168.1.3
content of /etc/exports is: /home 192.168.1.0/255.255.255.0(rw,sync,no_root_squash) /home/nfsroot 192.168.1.0/255.255.255.0(rw,no_subtree_check,async,no_root_squash)
Please can some one help me to use my USB wireless card D-Link on my laptop.i want to configure it, I am using madriva 2010 my system Acer Aspire 4315.i want to know how to configure it and where to get special driver to download the driver.
I wanted to setup my server as a router/gateway just for educational purposes and also when it succeeded i will keep the gateway and place it on the front line right after my modem.
My current setup as it is now :
The GATEWAY/ROUTER will be doing the main work to act as a dhcp server and firewall.
Now my setup as it is now :
So now what i ment to do was :
Let the clients connect to the gateway via ETH1 and all the stuff being router to ETH0 which is the NIC that is connected to the internet.
But now i have two huge problems :
1. The DHCP configuration seems to be fine the client machines get their ip adresses and /etc/resolve.conf looks fine to. But somehow the GATEWAY/ROUTER wont let me use the specified external DNs server so i cant do anything on these machines.
2. The firewall script [url] at line 27 should be DROP but if i use this line of code the GATEWAY/ROUTER cannot use his dns server settings so when i try to browse the internet or ping a machine outside my local network it would came up with nothing.
I'm trying to get nfs server working at boot up and it isn't starting because it says portmapper isn't running. I've read through a bunch of documentation on this and have gotten to the point that if the documentation tells me to Code: Select all$ apt-get install nfs-kernel-server portmap I usually stop there as it is outdated. I cant find a process doc that utilizes rpcbind. So, here is what I've done on my own:
setup /etc/exports with a proper nfs dir and exportfs it Code: Select all$ apt-get install nfs-common nfs-kernel-server $ sysv-rc-conf ---│ nfs-kerne$ [ ] [X] [X] [X] [X] [ ] [ ] [ ] │ ---│ rpcbind [ ] [X] [X] [X] [X] [ ] [ ] [ ] │ $ service rpcbind start
[Code] ....
The errors however don't seem critical as I'm able to mount the exported directory. OK so it appears to me that nfs server is working. However through a boot, the nfs-kernel-server and the rpcbind services are not starting. The nfs-kernel-server didn't start because rpcbind wasn't running. So I start rpcbind and then nfs-kernel-server and then nfs server works. So what am I missing? Why will rpcbind not start at boot?
I'm having a lot of difficulty trying to use tab completion while working in my FTP server from a terminal.I access this server with other Linux distros and OSX and the completion works fine. I've tried changing a lot of Debian config, but it seems to only affect the completion within the local scope.
Tab completion does work for system related tasks, no problem.
System: Debian 8.2/Kernel 3.16.0-4-amd64
FTP Server: Trendnet TS-I300 NAS with FTP/upnp
Settings: Enabled in bashrc: Code: Select allif ! shopt -oq posix; then if [ -f /usr/share/bash-completion/bash_completion ]; then . /usr/share/bash-completion/bash_completion elif [ -f /etc/bash_completion ]; then . /etc/bash_completion fi fi
I tryed to install a DNS server on debian lenny, i installed bind9 and webmin, and then i installed a bind module for webmin. I created a domain with webmin but when i tryed to add a address record with it i had a Error-Missing Content-Type Header.
I have ssh and http server running on a linux box.The interface is DHCP configured, using dyndns.org to register its assigned IP, my ADSL modem does not do routing.When i reboot the system none of the servers are visible from the outside...Recently i got a hint to add "ping google.com" to cron run every 5mins. With this hack the servers become visible, and i can see/connect from the outside; - but for obvious reasons ont like this solution.Anyone is able to shed some light why the server needs to do outgoing tarffic to become visible?
I have since a couple of days a vps. I discovered that there's is no nameserver is running.
# host google.com Nameserver not running google.com A record not found, try again
Also there's no resolv.config in /etc/. I re-installed the OS several times without any changes. I ask my host about this but he has not answered my questions.
I'm trying to get my simple home web server on the internet but I cannot seem to make it work. I've set up a LAMP stack to host my website and it works perfectly on my local network (accessing from [URL].. but not from the internet. To test it for now before I set up a dynamic dns service, I am trying to access my website via my WAN IP address from within and outside of my home network (ie http://69. When I do this, I get a "taking too long to respond" message, instead of a host not found or 404 or something of that nature. My box has a pentium 4, 2 gigs of ram, and is on a DSL line so I have a hard time believing anything is "taking too long". Here are the software packages I've installed:
All of these packages work perfectly fine from within my home LAN, but NONE work outside of my network.
Other configs: -My router forwards traffic on port 80 to my server -My iptables allow incoming traffic on port 80 -My ISP, AT&T, does not block port 80 (or any port, according to various online sources)
Perhaps Apache is not configured correctly? What apache config options would be related to this problem?
I've previously tried a similar setup with the dyndns service fully configured (I followed a very thorough guide down to the t - wish I had the link it was excellent), but to no avail - I got the same "too long to respond" accessing from my domain name. I understand that there are a multitude of causes for this problem, so what can I do to narrow down the source? "How to set up a LAMP server" guide, because all of them have lead me to where I am now.
Let me start by saying its a school assignment, and therefore not a real world situation. Nevertheless, I would appreciate any help I can get.The company ProvidIT has contacted us, their website has been hacked. Instead of their normal website, it shows Buy creditcard details online, click here (cc4u.jpg). A classical defacement.The following offenses also might have been committed. So its our job to find evidence for those offences.(I had to translate the Dutch law articles, so they might not be 100% acurate legally speaking, but you get the idea)
- Unlawfully accessing automated systems - Copy or tap (eavesdrop) data after hacking - Unlawfully access or use system resources of a 3rd party computer
