Re: [Ltsp-discuss] DHCP server on external network
Thank you Andre. I will take a look! Regards Patrick On 11/03/14 00:21, Andre Laforest wrote: Hi, My first look would point to NX (or Neat x) for the server part. The client outside the network could use any NX client. For my part Remina is doing great. Regards, André - Original Message - From: Patrick Reynolds Sent: 03/06/14 08:00 AM To: ltsp-discuss@lists.sourceforge.net Subject: [Ltsp-discuss] DHCP server on external network -- Subversion Kills Productivity. Get off Subversion Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk Cordialement, \\|// (@ @) ---oOOo-(_)-oOOo- André Laforest Dessin technique et conception mécanique en 3D Spécialiste d'application CAD et CAE. téléphone / phone : 581 701-1023 courriel / e-mail : alafor...@mail.com -Oooo oooO( ) ( )) / \ ((_/ \_) Devez-vous vraiment imprimer ce courriel? Pensons à l'environnement. -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP server on external network
Hi, My first look would point to NX (or Neat x) for the server part. The client outside the network could use any NX client. For my part Remina is doing great. Regards, André - Original Message - From: Patrick Reynolds Sent: 03/06/14 08:00 AM To: ltsp-discuss@lists.sourceforge.net Subject: [Ltsp-discuss] DHCP server on external network -- Subversion Kills Productivity. Get off Subversion Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk Cordialement, \\|// (@ @) ---oOOo-(_)-oOOo- André Laforest Dessin technique et conception mécanique en 3D Spécialiste d'application CAD et CAE. téléphone / phone : 581 701-1023 courriel / e-mail : alafor...@mail.com -Oooo oooO ( ) ( ) ) / \ ( (_/ \_) Devez-vous vraiment imprimer ce courriel? Pensons à l'environnement. -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] DHCP server on external network
Can Kiwi-ltsp be set to use a DHCP server on the external network and how do you do it? Many thanks Patrick -- Subversion Kills Productivity. Get off Subversion Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk_ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP load balancing w/ DHCP proxy?
Le mardi 8 juin 2010 22:04:18, Steve Cayford a écrit : I'm looking at expanding my LTSP installation with another server (I already have /home, LDAP authentication, and CUPS offloaded onto another server). It appears that the primary options at the moment are load balancing across a pair of DHCP servers or moving to ltsp-cluster is that correct? The tricky part is that I don't control the enterprise DHCP so will need to use a DHCP proxy and it doesn't look like dnsmasq will do load balancing. Ltsp-cluster sounds like the only way to go, does that sound right? Thanks for any comments. You can also let the thin-client decide on which server it will boot. A server with a lot of load will answer later than the one with less Another possibility: at ldm login, users can be presented a list of servers. Then they choose on which server they login. Xavier xav...@alternatif.org - 09 54 06 16 26 -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP load balancing w/ DHCP proxy?
On 06/09/2010 02:16 AM, Xavier Brochard wrote: You can also let the thin-client decide on which server it will boot. A server with a lot of load will answer later than the one with less Another possibility: at ldm login, users can be presented a list of servers. Then they choose on which server they login. Thanks for the suggestions. How well does it work to use the server's response delay for load balancing? The simplicity is appealing, but it sounds a bit haphazard. Some terminal users here get confused enough as it is, so I don't want to present them with more choices they don't understand. :) -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP load balancing w/ DHCP proxy?
Le mercredi 9 juin 2010 17:48:45, Steve Cayford a écrit : On 06/09/2010 02:16 AM, Xavier Brochard wrote: You can also let the thin-client decide on which server it will boot. A server with a lot of load will answer later than the one with less Another possibility: at ldm login, users can be presented a list of servers. Then they choose on which server they login. Thanks for the suggestions. How well does it work to use the server's response delay for load balancing? The simplicity is appealing, but it sounds a bit haphazard. Some terminal users here get confused enough as it is, so I don't want to present them with more choices they don't understand. :) I used it for 2 years in a little room (around 10 clients), it was working quite well. But my DHCP servers were the same as my LTSP servers (the dhcp server tells on which server to boot). It is simple but not very different than DHCP setup with a DHCP failover and a 50/50 split. Look here http://web.archive.org/web/20080410200233/http://theseus.sourceforge.net/projects/ets/supplemental.html http://web.archive.org/web/20080410200233/http://wiki.ltsp.org/twiki/bin/view/Ltsp/WorkInProgress#LTSP_load_balancer if you need more explanations. Another option is to use a boot disk with the server address built in (I think it is feasible with Etherboot). But in your case, ltsp-cluster looks like a better solution. Xavier xav...@alternatif.org - 09 54 06 16 26 -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] DHCP load balancing w/ DHCP proxy?
I'm looking at expanding my LTSP installation with another server (I already have /home, LDAP authentication, and CUPS offloaded onto another server). It appears that the primary options at the moment are load balancing across a pair of DHCP servers or moving to ltsp-cluster is that correct? The tricky part is that I don't control the enterprise DHCP so will need to use a DHCP proxy and it doesn't look like dnsmasq will do load balancing. Ltsp-cluster sounds like the only way to go, does that sound right? Thanks for any comments. -Steve -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] DHCP / clinet NAME
Hello, Im using the Kiwi-ltsp without dhcp because this services running already on our Schoolserver (OSS 2.6.2 based on SLES 9). The Schoolserver (DHCP/LDAP/DNS/SAMBA etc.) provides typical names like hangar18-pc01 to the clients. the KIWI-LTSP doesn't recognize that and gave them names like WS1, WS2 .. How do I sync them ?? Greetings from Germany Frank -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP Exclusion Lists Windows 2003
Torsdag 16. juli 2009 10:58, skrev Sean Carte: I hope someone has done this before and can tell me how to do it: I need to run an LTSP server in an environment where DHCP leases are handed out by a Windows 2003 DHCP server. I know that it is possible on Novel to specify a list of clients to exclude, is this also possible on Windows 2003? Or is there a better way: how easy is it to configure Windows server to redirect a client to the LTSP server? Presumably this would mean that I wouldn't need the DHCP server on the LTSP server? I don't have a Windows 2003 server with which to experiment, so I'd be grateful for assistance from someone who does. Sean I did that a few years ago, and this is what you need to add to the dhcp-server on windows: 17 Root Path10.0.2.2:/opt/ltsp/i386 66 Boot Server Host 10.0.2.2 67 Bootfile Name/var/lib/tftpboot/ltsp/i386/pxelinux.0 -- Klaus Ade 67E61D18B2C44F8A3DA35C6D849F9F5F 26FA477D signature.asc Description: This is a digitally signed message part. -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge_ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP Exclusion Lists Windows 2003
Sean Carte kirjoitti: Or is there a better way: how easy is it to configure Windows server to redirect a client to the LTSP server? Presumably this would mean that I wouldn't need the DHCP server on the LTSP server? You can do that in two ways. I use Ubuntu 8.04 LTS, so here we go. I do use first one. But I have tested second one and it works just great (Linksys/DD-WRT as a DHCP Server). 1. With Windows Server, no DHCP server on LTSP server http://www.arkki.info/howto/Wiki/LTSP5-Kokkola/Windows_dhcpd.png https://help.ubuntu.com/community/UbuntuLTSP/LTSPWindowsDHCP 2. With Windows Server and Proxy DHCP on LTSP server, no DHCP server on LTSP server https://help.ubuntu.com/community/UbuntuLTSP/ProxyDHCP All other HOWTOs for Ubuntu LTSP server. https://help.ubuntu.com/community/UbuntuLTSP Best Regards Asmo Koskinen. -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP Exclusion Lists Windows 2003
Thank you Asmo and Klaus. I'll try your suggestions. Sean -- Sean Carte esAL Library Systems Manager +27 72 898 8775 +27 31 373 2490 fax: 0866741254 http://esal.dut.ac.za/ -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP address request problem WORK AROUND
Hi, I was with Lars when we were troubleshooting this. We tried downgrading dhcp3-server to the same version that the Hardy server was running. But that didn't help at all. I dont know what else on the server could make the DHCP server act this way. On Fri, Jan 9, 2009 at 4:44 PM, Gavin McCullagh gmccull...@gmail.comwrote: Hi, On Fri, 09 Jan 2009, Lars Andersson wrote: If this is for any help for you we found a work around. After hours of wiresharking and reconfiguring of dhcpd we decided to try another dhcp server. We put a Hardy Heron server with dhcp3-server beside our Intrepid Ibex server and after that the clients got thier addresses. Of course it required that the next server statement in dhcpd.conf is pointed to the LTSP server. It seems that running dhcpd with all the other services on the LTSP server is simply to much even if the server idles 90% of CPU time. Good work, thanks. It's far from ideal, but at least it helps fix it and further pinpoint the issue. I wonder if running an alternative dhcp server such as udhcpd or dnsmasq on the server would fix this (if so, this indicates a bug somewhere in dhcp3-server). If you have time to try that out, it would be brilliant. Gavin -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword_ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP address request problem WORK AROUND
I have a show stopper problem with my LTSP installation. I run Ubuntu 8.10 with Edubuntu Add on. Sometimes my clients doesn't seem to get an ip address from the server. Usually I can boot about 4 to 5 clients with no problems at all but when I turn on some more clients they hang when they try to get their addresses. You're not the first to describe this sort of issue, but I've yet to hear anyone with any good idea why it's happening and I haven't seen it myself. From the previous descriptions, it sounded like the server was somehow to busy and wasn't responding quick enough to dhcp requests -- which is pretty strange as dhcp is not exactly a heavy duty task. Checking the logs and network traffic (wireshark) says DHCP DISCOVER broadcast from the clients and DHCP OFFER from the server but no REQUEST and ACK. Your description of the packet trace is interesting. I hope our friends at Microsoft won't mind me quoting one of their images. http://i.technet.microsoft.com/cc780760.0e354224-5f96-42e5-9044-000a53d629c3(en-us).gif If the above is correct, you're not waiting on the server at all, the two have had a handshake and now the server's waiting on a request from the client but it isn't getting it. I guess this either means 1. The client isn't seeing the dhcp offer and is waiting on it 2. It gets it but for some reason doesn't respond with a dhcp request 3. It sends the dhcp request but the server doesn't see it But I can't see why any of those would be caused by just 4-5 clients being online. Could it be that something's wrong and they're swamping the network? Is the load high on the server? Do you have something you could watch the network load with? The dhcp request should be a broadcast, can you see it on another machine on the network? I'm sort of reaching here, sorry. If this is for any help for you we found a work around. After hours of wiresharking and reconfiguring of dhcpd we decided to try another dhcp server. We put a Hardy Heron server with dhcp3-server beside our Intrepid Ibex server and after that the clients got thier addresses. Of course it required that the next server statement in dhcpd.conf is pointed to the LTSP server. It seems that running dhcpd with all the other services on the LTSP server is simply to much even if the server idles 90% of CPU time. Lars -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP address request problem WORK AROUND
Hi, On Fri, 09 Jan 2009, Lars Andersson wrote: If this is for any help for you we found a work around. After hours of wiresharking and reconfiguring of dhcpd we decided to try another dhcp server. We put a Hardy Heron server with dhcp3-server beside our Intrepid Ibex server and after that the clients got thier addresses. Of course it required that the next server statement in dhcpd.conf is pointed to the LTSP server. It seems that running dhcpd with all the other services on the LTSP server is simply to much even if the server idles 90% of CPU time. Good work, thanks. It's far from ideal, but at least it helps fix it and further pinpoint the issue. I wonder if running an alternative dhcp server such as udhcpd or dnsmasq on the server would fix this (if so, this indicates a bug somewhere in dhcp3-server). If you have time to try that out, it would be brilliant. Gavin -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] DHCP address request problem
Hi,
I have a show stopper problem with my LTSP installation. I run Ubuntu 8.10 with
Edubuntu Add on. Sometimes my clients doesn't seem to get an ip address from
the server. Usually I can boot about 4 to 5 clients with no problems at all but
when I turn on some more clients they hang when they try to get their
addresses. Checking the logs and network traffic (wireshark) says DHCP DISCOVER
broadcast from the clients and DHCP OFFER from the server but no REQUEST and
ACK.
The clients are HP T5530 thin clients. The server is an IBM 346 (2xXeon 3.0Ghz
4Gb RAM). There's 3 switches between server and clients, 2 Cisco 2970's and 1
2960. There is nothing else but the server and the clients on the same VLAN.
Any ideas? I'm getting desperate, don't know where to find answer.
My dhcpd.conf:
authoritative;
subnet XXX.XXX.128.0 netmask 255.255.255.0 {
range XXX.XXX.128.50 XXX.XXX.128.199;
option domain-name xxx.xxx.se;
option domain-name-servers XXX.XXX.154.16;
option broadcast-address XXX.XXX.128.255;
option routers XXX.XXX.128.1;
next-server XXX.XXX.128.5;
#get-lease-hostnames true;
option subnet-mask 255.255.255.0;
option root-path /opt/ltsp/i386;
if substring( option vendor-class-identifier, 0, 9 ) = PXEClient {
filename /ltsp/i386/pxelinux.0;
} else {
filename /ltsp/i386/nbi.img;
}
}
Regards
Lars
--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP address request problem
Hi, On Wed, 07 Jan 2009, Lars Andersson wrote: I have a show stopper problem with my LTSP installation. I run Ubuntu 8.10 with Edubuntu Add on. Sometimes my clients doesn't seem to get an ip address from the server. Usually I can boot about 4 to 5 clients with no problems at all but when I turn on some more clients they hang when they try to get their addresses. You're not the first to describe this sort of issue, but I've yet to hear anyone with any good idea why it's happening and I haven't seen it myself. From the previous descriptions, it sounded like the server was somehow to busy and wasn't responding quick enough to dhcp requests -- which is pretty strange as dhcp is not exactly a heavy duty task. Checking the logs and network traffic (wireshark) says DHCP DISCOVER broadcast from the clients and DHCP OFFER from the server but no REQUEST and ACK. Your description of the packet trace is interesting. I hope our friends at Microsoft won't mind me quoting one of their images. http://i.technet.microsoft.com/cc780760.0e354224-5f96-42e5-9044-000a53d629c3(en-us).gif If the above is correct, you're not waiting on the server at all, the two have had a handshake and now the server's waiting on a request from the client but it isn't getting it. I guess this either means 1. The client isn't seeing the dhcp offer and is waiting on it 2. It gets it but for some reason doesn't respond with a dhcp request 3. It sends the dhcp request but the server doesn't see it But I can't see why any of those would be caused by just 4-5 clients being online. Could it be that something's wrong and they're swamping the network? Is the load high on the server? Do you have something you could watch the network load with? The dhcp request should be a broadcast, can you see it on another machine on the network? I'm sort of reaching here, sorry. Gavin -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP
On Mon, 7 Apr 2008, jam wrote: but my via epia TC gets the DHCP info from .254 as it should and then tries to tftp the files from .254 not from .120. Is this a defect on via's pxe or me being ultra stupid ? I had similar problem with pxe boot of an ibm lenovo (see earlier posts)... You can try to update the BIOS (though I am not sure of it) or setup tftpd on the host serving DHCP requests (and do not forget sync /var/lib/tftpboot from the ltsp-server after updating the ltsp-kernel). -- Zsolt - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP
On Mon, 7 Apr 2008, Sudev Barar wrote: #next-server 192.168.5.254; next-server 192.168.5.120; You are missing: option root-path 192.168.5.120:/opt/ltsp/i386; This is only relevant if the client asks for the kernel *from .120* ... if it does not then the pxe-rom may not interpret (well) the next-server line. One can try to define the IP of the tftpd server in an option line but I had no luck with it (man dhcp-options). Zsolt - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP
Hi,
Use k12-ltsp project..it's working fine... if face any problems, then send
me mail on [EMAIL PROTECTED]
Bye
Vishu
On 07/04/2008, jam [EMAIL PROTECTED] wrote:
Hi
frustration is the obvious not working ...
I'm trying to use DHCP on my system server (.254) to run LTSP5 on my
ltsp server (.120)
I see the next-server correctly set in the DHCP offer (.120)
I can get the files from .120 by tftp
but my via epia TC gets the DHCP info from .254 as it should and then
tries to tftp the files from .254 not from .120.
Is this a defect on via's pxe or me being ultra stupid ?
dhcpd.conf
ddns-update-style ad-hoc;
option subnet-mask255.255.255.0;
option broadcast-address 192.168.5.255;
option routers192.168.5.1;
option domain-name-servers192.168.5.254;
option domain-namehome; # You really should fix this
option option-128 code 128 = string;
option option-129 code 129 = text;
get-lease-hostnames true;
#next-server 192.168.5.254;
next-server 192.168.5.120;
subnet 192.168.5.0 netmask 255.255.255.0 {
range 192.168.5.121 192.168.5.125;
if substring (option vendor-class-identifier, 0, 9) = PXEClient {
filename /ltsp/i386/pxelinux.0;
}
else{
filename /ltsp/vmlinuz-2.6.20.9-ltsp-1;
}
[snip]
host pos01 {
#next-server192.168.5.120;
hardware ethernet 00:40:63:da:67:8d;
fixed-address ws123;
filename/ltsp/i386/pxelinux.0;
}
}
Thanks
James
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] DHCP
Hi
frustration is the obvious not working ...
I'm trying to use DHCP on my system server (.254) to run LTSP5 on my
ltsp server (.120)
I see the next-server correctly set in the DHCP offer (.120)
I can get the files from .120 by tftp
but my via epia TC gets the DHCP info from .254 as it should and then
tries to tftp the files from .254 not from .120.
Is this a defect on via's pxe or me being ultra stupid ?
dhcpd.conf
ddns-update-style ad-hoc;
option subnet-mask255.255.255.0;
option broadcast-address 192.168.5.255;
option routers192.168.5.1;
option domain-name-servers192.168.5.254;
option domain-namehome; # You really should fix this
option option-128 code 128 = string;
option option-129 code 129 = text;
get-lease-hostnames true;
#next-server 192.168.5.254;
next-server 192.168.5.120;
subnet 192.168.5.0 netmask 255.255.255.0 {
range 192.168.5.121 192.168.5.125;
if substring (option vendor-class-identifier, 0, 9) = PXEClient {
filename /ltsp/i386/pxelinux.0;
}
else{
filename /ltsp/vmlinuz-2.6.20.9-ltsp-1;
}
[snip]
host pos01 {
#next-server192.168.5.120;
hardware ethernet 00:40:63:da:67:8d;
fixed-address ws123;
filename/ltsp/i386/pxelinux.0;
}
}
Thanks
James
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP
On 07/04/2008, jam [EMAIL PROTECTED] wrote: Hi frustration is the obvious not working ... I'm trying to use DHCP on my system server (.254) to run LTSP5 on my ltsp server (.120) I see the next-server correctly set in the DHCP offer (.120) I can get the files from .120 by tftp but my via epia TC gets the DHCP info from .254 as it should and then tries to tftp the files from .254 not from .120. Is this a defect on via's pxe or me being ultra stupid ? dhcpd.conf ddns-update-style ad-hoc; option subnet-mask255.255.255.0; option broadcast-address 192.168.5.255; option routers192.168.5.1; option domain-name-servers192.168.5.254; option domain-namehome; # You really should fix this option option-128 code 128 = string; option option-129 code 129 = text; get-lease-hostnames true; #next-server 192.168.5.254; next-server 192.168.5.120; You are missing: option root-path 192.168.5.120:/opt/ltsp/i386; -- Regards, Sudev Barar Read http://blog.sudev.in for topics ranging from here to there. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] dhcp
Hallo, I'm testing ltsp on ubuntu, I need some help for the dhcp, we have two networks, 192.168.2.0 is the main network and 192.168.0.0 is the lts network. I want to distribute fixed ip based on mac address for the main network and only if the mac address is not in the list of allowed client I'll give to the client an ip of 192.168.0.0 network. Is it possible? How? Thanks, Pietro -- I will build myself a copper tower With four ways out and no way in But mine the glory, mine the power (So I chose AmigaOS, GNU/Linux and OpenBSD) - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] dhcp
On Tuesday 04 September 2007 20:46:25 [EMAIL PROTECTED] wrote:
Hallo, I'm testing ltsp on ubuntu, I need some help for the dhcp, we have
two networks, 192.168.2.0 is the main network and 192.168.0.0 is the lts
network. I want to distribute fixed ip based on mac address for the main
network and only if the mac address is not in the list of allowed client
I'll give to the client an ip of 192.168.0.0 network. Is it possible? How?
Thanks, Pietro
Hello Pietro,
Absolutely possible.
Here's an example:
# This dhcpd.conf is used to accomodate the need to:
# 1. Give unknown clients ip address from pool of range of 192.168.0.20 to
192.168.0.30
# 2. Give known clients ip address from pool of range of 192.168.0.50 to
192.168.0.60
# 3. Give LTSP service to known clients from pool of range of 192.168.0.100 to
192.168.0.150
authoritative;
server-identifier centos5a;
#ddns-updateson;
#ddns-update-style interim;
ddns-domainname jauh.com.;
ddns-rev-domainname in-addr.arpa.;
ignore client-updates;
#include /etc/ddns_key.key;
subnet 192.168.0.0 netmask 255.255.255.0 {
option domain-name jauh.com;
option domain-name-servers 192.168.0.199, 10.1.2.253;
option broadcast-address 192.168.0.255;
option routers 192.168.0.254;
option subnet-mask 255.255.255.0;
next-server 192.168.0.197;
pool {
allow unknown-clients;
range 192.168.0.20 192.168.0.30;
}
pool {
deny unknown-clients;
range 192.168.0.50 192.168.0.60;
host nonltsp1 {
hardware ethernet 00:16:11:23:30:9f;
fixed-address 192.168.0.50;
}
}
#LTSP Clients by Mac Address
pool {
use-host-decl-names on;
deny unknown-clients;
range 192.168.0.100 192.168.0.150;
# The TFTP server:
next-server 192.168.0.197;
if substring( option vendor-class-identifier, 0, 9 ) = PXEClient {
filename /ltsp/i386/pxelinux.0;
}
else{
filename /ltsp/i386/nbi.img;
}
option root-path /opt/ltsp/i386;
host client1 {
hardware ethernet 00:16:d3:18:a5:68;
fixed-address 192.168.0.91;
}
}
}
HTH,
--
Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial
http://linux2.arinet.org
21:30:29 up 23 min, 2.6.20-16-generic GNU/Linux
Let's use OpenOffice. http://www.openoffice.org
pgpbAPlELgYDF.pgp
Description: PGP signature
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now http://get.splunk.com/_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP fails on Suse 10.2/LTSP 4.2
Perseu schrieb: Message: 1 Date: Mon, 16 Jul 2007 08:51:26 +0200 From: Rolf-Werner Eilert [EMAIL PROTECTED] Subject: [Ltsp-discuss] DHCP fails on Suse 10.2/LTSP 4.2 To: ltsp-discuss@lists.sourceforge.net Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-15; format=flowed Hi everyone, I've got a new server here to be equipped with LTSP. There is a Suse 10.2 running on this machine. I can log in via X from my terminal to the old server like from a big client. After setting up LTSP 4.2 and copying (from the old server) and editing (new IPs etc.) all the necessary configuration files (lts.conf, dhcpd.conf etc.), I found that DHCP receives a request from the clients but the answer is never received. Instead of Jun 15 07:06:11 server02 dhcpd: DHCPDISCOVER from 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPOFFER on 192.168.10.132 to 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPREQUEST for 192.168.10.132 (192.168.10.102) from 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPACK on 192.168.10.132 to 00:e0:4c:07:4a:35 via eth0 it just does Jun 15 07:06:11 server02 dhcpd: DHCPDISCOVER from 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPOFFER on 192.168.10.132 to 00:e0:4c:07:4a:35 via eth0 over and over again. The client just says No IP address and tries again. The firewall is off (I couldn't reach the new server via X otherwise). I looked over the configuration but to no avail. All IP numbers and stuff seem to be correctly set. So, where should I start searching for any mis-configurations? Maybe there is something weird left from the firewall? Regards Rolf In Debian Etch, or anything with dhcp3-server = 3.0.3, the next-server statement is needed or Etherboot will walk in circles saying No IP address. To activate, uncomment the line: next-server 192.168.0.254; # -- Change IP ! in dhcpd.conf file on your server. Perseu. Hurray, that was it! Thank you very much, it's running now. :-) Regards Rolf - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] DHCP fails on Suse 10.2/LTSP 4.2
Hi everyone, I've got a new server here to be equipped with LTSP. There is a Suse 10.2 running on this machine. I can log in via X from my terminal to the old server like from a big client. After setting up LTSP 4.2 and copying (from the old server) and editing (new IPs etc.) all the necessary configuration files (lts.conf, dhcpd.conf etc.), I found that DHCP receives a request from the clients but the answer is never received. Instead of Jun 15 07:06:11 server02 dhcpd: DHCPDISCOVER from 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPOFFER on 192.168.10.132 to 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPREQUEST for 192.168.10.132 (192.168.10.102) from 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPACK on 192.168.10.132 to 00:e0:4c:07:4a:35 via eth0 it just does Jun 15 07:06:11 server02 dhcpd: DHCPDISCOVER from 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPOFFER on 192.168.10.132 to 00:e0:4c:07:4a:35 via eth0 over and over again. The client just says No IP address and tries again. The firewall is off (I couldn't reach the new server via X otherwise). I looked over the configuration but to no avail. All IP numbers and stuff seem to be correctly set. So, where should I start searching for any mis-configurations? Maybe there is something weird left from the firewall? Regards Rolf - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP fails on Suse 10.2/LTSP 4.2
Mandag 16 juli 2007 08:51 skrev Rolf-Werner Eilert: Hi everyone, I've got a new server here to be equipped with LTSP. There is a Suse 10.2 running on this machine. I can log in via X from my terminal to the old server like from a big client. After setting up LTSP 4.2 and copying (from the old server) and editing (new IPs etc.) all the necessary configuration files (lts.conf, dhcpd.conf etc.), I found that DHCP receives a request from the clients but the answer is never received. Instead of Jun 15 07:06:11 server02 dhcpd: DHCPDISCOVER from 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPOFFER on 192.168.10.132 to 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPREQUEST for 192.168.10.132 (192.168.10.102) from 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPACK on 192.168.10.132 to 00:e0:4c:07:4a:35 via eth0 it just does Jun 15 07:06:11 server02 dhcpd: DHCPDISCOVER from 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPOFFER on 192.168.10.132 to 00:e0:4c:07:4a:35 via eth0 over and over again. The client just says No IP address and tries again. The firewall is off (I couldn't reach the new server via X otherwise). I looked over the configuration but to no avail. All IP numbers and stuff seem to be correctly set. So, where should I start searching for any mis-configurations? Maybe there is something weird left from the firewall? Regards Rolf - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net HI Try a new dhcpd.conf file, without anything for LTSP in it. Then see if you can get your machine to work as an ordinay DHCP server. If ok, then work from there. Also, check and make SURE that there are no other DHCP servers in the network (from small printerboxes and the like...) -- - Med venlig hilsen/Best regards Verner Kjærsgaard - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP fails on Suse 10.2/LTSP 4.2
Verner Kjærsgaard schrieb: Mandag 16 juli 2007 08:51 skrev Rolf-Werner Eilert: Hi everyone, I've got a new server here to be equipped with LTSP. There is a Suse 10.2 running on this machine. I can log in via X from my terminal to the old server like from a big client. After setting up LTSP 4.2 and copying (from the old server) and editing (new IPs etc.) all the necessary configuration files (lts.conf, dhcpd.conf etc.), I found that DHCP receives a request from the clients but the answer is never received. Instead of Jun 15 07:06:11 server02 dhcpd: DHCPDISCOVER from 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPOFFER on 192.168.10.132 to 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPREQUEST for 192.168.10.132 (192.168.10.102) from 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPACK on 192.168.10.132 to 00:e0:4c:07:4a:35 via eth0 it just does Jun 15 07:06:11 server02 dhcpd: DHCPDISCOVER from 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPOFFER on 192.168.10.132 to 00:e0:4c:07:4a:35 via eth0 over and over again. The client just says No IP address and tries again. The firewall is off (I couldn't reach the new server via X otherwise). I looked over the configuration but to no avail. All IP numbers and stuff seem to be correctly set. So, where should I start searching for any mis-configurations? Maybe there is something weird left from the firewall? Regards Rolf - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net HI Try a new dhcpd.conf file, without anything for LTSP in it. Then see if you can get your machine to work as an ordinay DHCP server. If ok, then work from there. Alright - although I cannot see the difference, I'll check it out. Also, check and make SURE that there are no other DHCP servers in the network (from small printerboxes and the like...) Yes, of course there aren't any. I also switched off the old server's DHCP before doing any tests. The strange thing is that the DHCP server on the new server seems to receive requests from the NICs but its response isn't heard. I understand that DHCP runs over two different UDP channels, so maybe the incoming calls are received but outgoing ones are blocked? Rolf - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP fails on Suse 10.2/LTSP 4.2
Message: 1 Date: Mon, 16 Jul 2007 08:51:26 +0200 From: Rolf-Werner Eilert [EMAIL PROTECTED] Subject: [Ltsp-discuss] DHCP fails on Suse 10.2/LTSP 4.2 To: ltsp-discuss@lists.sourceforge.net Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-15; format=flowed Hi everyone, I've got a new server here to be equipped with LTSP. There is a Suse 10.2 running on this machine. I can log in via X from my terminal to the old server like from a big client. After setting up LTSP 4.2 and copying (from the old server) and editing (new IPs etc.) all the necessary configuration files (lts.conf, dhcpd.conf etc.), I found that DHCP receives a request from the clients but the answer is never received. Instead of Jun 15 07:06:11 server02 dhcpd: DHCPDISCOVER from 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPOFFER on 192.168.10.132 to 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPREQUEST for 192.168.10.132 (192.168.10.102) from 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPACK on 192.168.10.132 to 00:e0:4c:07:4a:35 via eth0 it just does Jun 15 07:06:11 server02 dhcpd: DHCPDISCOVER from 00:e0:4c:07:4a:35 via eth0 Jun 15 07:06:11 server02 dhcpd: DHCPOFFER on 192.168.10.132 to 00:e0:4c:07:4a:35 via eth0 over and over again. The client just says No IP address and tries again. The firewall is off (I couldn't reach the new server via X otherwise). I looked over the configuration but to no avail. All IP numbers and stuff seem to be correctly set. So, where should I start searching for any mis-configurations? Maybe there is something weird left from the firewall? Regards Rolf In Debian Etch, or anything with dhcp3-server = 3.0.3, the next-server statement is needed or Etherboot will walk in circles saying No IP address. To activate, uncomment the line: next-server 192.168.0.254; # -- Change IP ! in dhcpd.conf file on your server. Perseu. --- Perseu Angelo Santoro O homem verdadeiramente sábio é aquele que vez por outra reconhece a si mesmo como um imbecil Dostoievski. Novo Yahoo! Cadê? - Experimente uma nova busca. http://yahoo.com.br/oqueeuganhocomisso - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] DHCP on alternate ports
Hello,
I'm setting up an LTSP (v.5) server on Xubuntu 6.10. I'm trying to work around
an existing DHCP server by running on ports 1067 and 1068. I've got the
etherboot part working. The client gets an IP and downloads the kernel via
tftp successfully, but is unable to mount the root filesystem via nfs. Once
the kernel takes over it switches back to trying the default dhcp ports.
I followed the recommendations in this discussion,
http://www.mail-archive.com/edubuntu-users@lists.ubuntu.com/msg00175.html ,
however the ipconfig -p 1068 ${DEVICE} line in /scripts/nfs doesn't seem to
help. I verified that it is changed in the new initrd that I created in
/opt/ltsp/i386.
After the client fails to get a valid nfs mount (since it's talking to the
wrong dhcp server) it goes to a busybox prompt. I tested the ipconfig command
above at the prompt and it works so I'm not sure why it's not being succeeding
in the script.
Thanks for any suggestions.
--
Steven Cayford
McNamara Academic Center
University of Minnesota
http://gopheracademics.com
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP on alternate ports
Steve Cayford wrote:
[...]
I followed the recommendations in this discussion,
http://www.mail-archive.com/edubuntu-users@lists.ubuntu.com/msg00175.html ,
however the ipconfig -p 1068 ${DEVICE} line in /scripts/nfs doesn't seem to
help. I verified that it is changed in the new initrd that I created in
/opt/ltsp/i386.
If I may reply to myself...
I was missing the mkelf-linux step. I ran that to create a new nbi image,
copied it into /var/lib/tftpboot/i386/ and now things are good to go.
--
Steven Cayford
McNamara Academic Center
University of Minnesota
http://gopheracademics.com
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP will not start
[EMAIL PROTECTED] wrote:
You must allow the interfaces in /etc/sysconfig/dhcpd
# Examples: DHCPD_INTERFACE=eth0
# DHCPD_INTERFACE=eth0 eth1 eth2 tr0 wlan0
# DHCPD_INTERFACE=internal0 internal1
# DHCPD_INTERFACE=id-00:50:fc:e4:f2:65 id-00:a0:24:cb:cc:5c wlan0
#
DHCPD_INTERFACE=br0
James
I added eth0 eth1 to the DHCPD_INTERFACE= without success.
Also, I used the id argument to no avail.
I have attached the following files for evaluation:
/etc/dhcpd.conf
/etc/hosts
/opt/ltsp/i386/etc/lts.conf
/etc/sysconfig/dhcpd
Thanks,
Nathan
## Path:Network/DHCP/DHCP server
## Description: DHCP server settings
## Type:string
## Default:
## ServiceRestart: dhcpd
#
# Interface(s) for the DHCP server to listen on.
#
# Instead of the interface name, the name of its configuration can be given.
# If the configuration file is named
#/etc/sysconfig/network/ifcfg-eth-id-00:50:fc:e4:f2:65
# then id-00:50:fc:e4:f2:65 would be suitable to identify the configuration.
#
# A special keyword is ANY, it will cause dhcpd to autodetect available
# interfaces.
#
# Examples: DHCPD_INTERFACE=eth0
# DHCPD_INTERFACE=eth0 eth1 eth2 tr0 wlan0
# DHCPD_INTERFACE=internal0 internal1
# DHCPD_INTERFACE=id-00:50:fc:e4:f2:65 id-00:a0:24:cb:cc:5c wlan0
# DHCPD_INTERFACE=ANY
#
DHCPD_INTERFACE=id-00:08:54:14:0d:73
## Type:yesno
## Default: yes
## ServiceRestart: dhcpd
#
# Shall the DHCP server dhcpd run in a chroot jail (/var/lib/dhcp)?
#
# Each time you start dhcpd with the init script, /etc/dhcpd.conf will
# be copied to /var/lib/dhcp/etc/.
#
# Some files that are important for hostname to IP address resolution
# (/etc/{hosts,host.conf,resolv.conf,localtime}, /lib/libnss_dns.so.2,
# /lib/libresolv.so.2) will also be copied to the chroot jail by the
# init script when you start it (about 100kB altogether).
#
# The pid file will be in /var/lib/dhcp/var/run/dhcpd.pid.
#
DHCPD_RUN_CHROOTED=yes
## Type:string
## Default:
## ServiceRestart: dhcpd
#
# Since version 3, dhcpd.conf can contain include statements.
# If you enter the names of any include files here, _all_ conf
# files will be copied to $chroot/etc/, when dhcpd is started in the
# chroot jail. (/etc/dhcpd.conf is always copied.)
#
# For your convenience, you can also specify entire directories, like
# /etc/dhcpd.conf.d.
#
# Example: /etc/dhcpd.conf.shared /etc/dhcpd.conf.bootp-clients
#
DHCPD_CONF_INCLUDE_FILES=
## Type:string
## Default: dhcpd
## ServiceRestart: dhcpd
#
# Leave empty or enter root to let dhcpd run as root.
# Enter dhcpd to run dhcpd as user 'dhcpd'.
#
DHCPD_RUN_AS=dhcpd
## Type:string
## Default:
## ServiceRestart: dhcpd
#
# Other arguments that you want dhcpd to be started with
# (e.g. -p 1234 for a non-standard port to listen on)
#
DHCPD_OTHER_ARGS=
## Type:string
## Default:
## ServiceRestart: dhcpd
#
# You may specify another dhcpd binary to be run.
# The full path needs to be specified.
#
# If empty, the default applies.
#
DHCPD_BINARY=
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option root-path 192.168.0.254:/opt/ltsp/i386;
option option-128 code 128 = string;
option option-129 code 129 = text;
option domain-name ltsp;
option domain-name-servers 192.168.0.254;
option routers 192.168.0.254;
next-server 192.168.0.254;
#
# Sample configuration file for ISC dhcpd
#
# Make changes to this file and copy it to /etc/dhcpd.conf.sample
#
ddns-update-style none;
max-lease-time 21600;
default-lease-time 21600;
subnet 192.168.0.0 netmask 255.255.255.0 {
option log-servers 192.168.0.254;
use-host-decl-names on;
default-lease-time 14400;
max-lease-time 172800;
##
## If you want to use static IP address for your workstations, then un-comment
## the following section and modify to suit your network.
## Then, duplicate this section for each workstation that needs a static
## IP address.
##
host ws001 {
hardware ethernet00:08:54:14:0D:47;
fixed-address 192.168.0.1;
filename /lts/vmlinuz-2.4.26-ltsp-3;
}
host ws002 {
hardware ethernet00:08:54:14:0D:78;
fixed-address 192.168.0.2;
filename /lts/vmlinuz-2.4.26-ltsp-3;
}
host ws003 {
hardware ethernet00:08:54:14:0D:53;
fixed-address 192.168.0.3;
filename /lts/vmlinuz-2.4.26-ltsp-3;
}
host ws004 {
hardware ethernet00:08:54:14:0D:5B;
fixed-address 192.168.0.4;
filename /lts/vmlinuz-2.4.26-ltsp-3;
}
host ws005 {
hardware ethernet00:08:54:14:0D:79;
fixed-address 192.168.0.5;
filename /lts/vmlinuz-2.4.26-ltsp-3;
}
host ws006 {
hardware ethernet00:50:FC:E6:A0:7A;
fixed-address 192.168.0.6;
filename /lts/vmlinuz-2.4.26-ltsp-3;
}
host ws007 {
hardware ethernet00:08:54:14:2A:FA;
fixed-address 192.168.0.7;
filename /lts/vmlinuz-2.4.26-ltsp-3;
}
host ws008 {
hardware ethernet
[Ltsp-discuss] DHCP will not start
I keep getting the following error message when I try to start dhcp (# dhcpd start): Internet Systems Consortium DHCP Server V3.0.5 Copyright 2004-2005 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file Wrote 0 deleted host decls to leases file. Wrote 0 new dynamic host decls to leases file. Wrote 0 leases to leases file. No subnet declaration for start (0.0.0.0). ** Ignoring requests on start. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface start is attached. ** Not configured to listen on any interfaces! If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the [EMAIL PROTECTED] mailing list, please read the section on the README about submitting bug reports and requests for help. Please do not under any circumstances send requests for help directly to the authors of this software - please send them to the appropriate mailing list as described in the README file. exiting. I had a working LTSP setup running on Suse 9.3. I am trying to upgrade to openSuse 10.2. The dhcp config file has been slightly modified (changed the kernel version number entries). Also, I have tried adding the next-server xxx.xxx.xxx.xxx line. This did not work, either. Let me know if I need to supply more info. Thanks, Nathan - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP will not start
On Friday 12 January 2007 00:41, [EMAIL PROTECTED] wrote: I had a working LTSP setup running on Suse 9.3. I am trying to upgrade to openSuse 10.2. The dhcp config file has been slightly modified (changed the kernel version number entries). Also, I have tried adding the next-server xxx.xxx.xxx.xxx line. This did not work, either. Let me know if I need to supply more info. You must allow the interfaces in /etc/sysconfig/dhcpd # Examples: DHCPD_INTERFACE=eth0 # DHCPD_INTERFACE=eth0 eth1 eth2 tr0 wlan0 # DHCPD_INTERFACE=internal0 internal1 # DHCPD_INTERFACE=id-00:50:fc:e4:f2:65 id-00:a0:24:cb:cc:5c wlan0 # DHCPD_INTERFACE=br0 James - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] dhcp, maybe OT
[EMAIL PROTECTED] schrieb: Hallo, I'm using LTSP on K12LTSP, now I have a problem configuring the dhcp, I have only one dhcp, but I want to use it for serving two different networks. Some mac address must receive a random 192.168.99.xxx address (ltsp network), some mac address must receive 192.168.2.xxx address, our internal network (192.168.2.10, 192.168.2.11, depends on the nic phisical address), is it possible? Thanks, Pietro Leone. This shouldn't be a problem IMHO as long as you know the MAC addresses in advance. I haven't done this, so it's just a guess: Normally there is one subnet stated in the head of the dhcpd.conf and the MACs and their fixed IPs under each workstation declaration. What I've done for some clients is to declare a specific LTSP kernel to be loaded for THIS workstation. Now take a look at man dhcpd.conf, there is a way of declaring different subnets, ranges of IPs etc. It should be possible to change this in a way that helps you :-) combining these features. Rolf - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] dhcp, maybe OT
Hallo, I'm using LTSP on K12LTSP, now I have a problem configuring the dhcp, I have only one dhcp, but I want to use it for serving two different networks. Some mac address must receive a random 192.168.99.xxx address (ltsp network), some mac address must receive 192.168.2.xxx address, our internal network (192.168.2.10, 192.168.2.11, depends on the nic phisical address), is it possible? Thanks, Pietro Leone. -- I will build myself a copper tower With four ways out and no way in But mine the glory, mine the power (So I chose AmigaOS, GNU/Linux and OpenBSD) - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP and Thin Clients
Eduardo, Thank you. But I have actually tried that already. The problem seems to be that I have my dhcpd server for LTSP and a Firewall providing dhcpd for the windows and wireless clients. I have also found that they seem to request an IP once more right after a user logs in. The reason I know is I have tried administering the thin client before a person logs in and after using ltspinfo, I am able to restart that client before anyone logs in, while its at the login screen. Also, upon running last | grep still | uniq, I find that the client IP has changed after they login. I have actually solved my problem already by manually specifying the thin clients in the second dhcp server, but I wanted to reply to this in hopes that someone is able to confirm whether or not the thin clients request dhcp at that time, and maybe how to change that? Thank you for your help! Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eduardo Costa Lisboa Sent: Tuesday, October 03, 2006 7:39 AM To: ltsp-discuss@lists.sourceforge.net Subject: Re: [Ltsp-discuss] DHCP and Thin Clients Hi, Chris. First of all, it is important to say that the thin clients do DHCP requests at least two times: one during the boot, before getting the bootstrap file and the kernel via TFTP and other, during the boot process, when starting the network(ing) script. What happens is that physically, you have two DHCP servers. And when you get in such a situation, it is a must to: - use fixed addresses for your clients; - ignore unknown clients; There is an option in dhcpd that ignores unknown clients, take a look at the manual (man dhcpd.conf) and search for ignore. -- Eduardo Costa Lisboa - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDE V _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP and Thin Clients
Hmm... Have you ever tried rising your lease-time and max-lease-time values? -- Eduardo Costa Lisboa - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] DHCP and Thin Clients
I currently have
been operating roughly 10 Thin clients on LTSP 4.1.1 at this one site for about
a year now. They always get a static IP via dhcpd from the ltsp server,
everything just works(ed).
Now when the thin
clients boot up, they get to the login screen for ltsp and everything, only
problem is they seem to be getting an address from another dhcp server I use for
everything but ltsp.
For
example:
ws002
{ hardware
ethernet
00:13:90:00:xx:xx:;
fixed-address
10.1.1.36;
filename
"/lts/vmlinuz-2.4.26-ltsp-3"; }
a line from my
dhcpd.conf file. This still seems to work because when the thin clients
boots it says " Me:10.1.1.36 and continues.
When I run the
command last | less | grep still | uniq, I get this as one if the lines
for that thin client:
username
10.1.1.239:0 10.1.1.239 Mon Sep 18 06:19 still logged
in
It seems like this
address is being obtained after the Thin Client has booted otherwise I would
assume it just wouldn't boot. Is there anything I can do to get this
operating normally again? I need to be able to set params in lts.conf, use
ltspinfo, etc.
Any help is much
appreciated.
Chris
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] DHCP and Thin Clients
I currently have
been operating roughly 10 Thin clients on LTSP 4.1.1 at this one site for about
a year now. They always get a static IP via dhcpd from the ltsp server,
everything just works(ed).
Now when the thin
clients boot up, they get to the login screen for ltsp and everything, only
problem is they seem to be getting an address from another dhcp server I use for
everything but ltsp.
For
example:
ws002
{ hardware
ethernet
00:13:90:00:xx:xx:;
fixed-address
10.1.1.36;
filename
"/lts/vmlinuz-2.4.26-ltsp-3"; }
a line from my
dhcpd.conf file. This still seems to work because when the thin clients
boots it says " Me:10.1.1.36 and continues.
When I run the
command last | less | grep still | uniq, I get this as one if the lines
for that thin client:
username
10.1.1.239:0 10.1.1.239 Mon Sep 18 06:19 still logged
in
It seems like this
address is being obtained after the Thin Client has booted otherwise I would
assume it just wouldn't boot. Is there anything I can do to get this
operating normally again? I need to be able to set params in lts.conf, use
ltspinfo, etc.
Any help is much
appreciated.
Chris
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP and Thin Clients
On 19/09/06, Chris Northstrum [EMAIL PROTECTED] wrote: Now when the thin clients boot up, they get to the login screen for ltsp and everything, only problem is they seem to be getting an address from another dhcp server I use for everything but ltsp. a line from my dhcpd.conf file. This still seems to work because when the thin clients boots it says Me:10.1.1.36 and continues. When I run the command last | less | grep still | uniq, I get this as one if the lines for that thin client: username 10.1.1.239:0 10.1.1.239Mon Sep 18 06:19 still logged in [With Snips] How can you berunning two DHCPD servers within same sub net xxx.xxx.1.xxx?? Are you using stock ltsp or k12ltsp? On ther server run: sudo tail -f /var/log/messages Now boot the thin client. The messages shoulkd tell you how IP allocation is happening? -- Regards, Sudev Barar - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] DHCP conflict question
(sorry if this is a duplicate, the first post had a bad header) Hi, I'm a LTSP and DHCP noob, and need to understand how I should work with a LTSP DHCP server in a large company with it's own DHCP servers. So when the LTSP workstation starts, it broadcasts for a DHCP server to meet it's needs. My questions below: 1. If I am in a large company intranet network situation and introduce an LTSP server into that network, how will my LTSP workstations (which may be in other parts of the country) find my LTSP DHCP server? 2. What is to keep other DHCP computers in the company not wanting to use LTSP from accidentally finding my LTSP DHCP server? 3. How can you even experiment with LTSP without causing DHCP havoc and irritating your companies intranet police? Are you all on disconnected networks? thanks for your ideas, fred- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642_ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP conflict question
On 9/7/06, Fred Clewis [EMAIL PROTECTED] wrote: Hi, I'm a LTSP and DHCP noob, and need to understand how I should work with a LTSP DHCP server in a large company with it's own DHCP servers. So when the LTSP workstation starts, it broadcasts for a DHCP server to meet it's needs. My questions below: 1. If I am in a large company intranet network situation and introduce an LTSP server into that network, how will my LTSP workstations (which may be in other parts of the country) find my LTSP DHCP server? They won't, because LTSP will not work over WAN. 2. What is to keep other DHCP computers in the company not wanting to use LTSP from accidentally finding my LTSP DHCP server? Configure your dhcp LTSP server to not give out leases to unknown clients and only add known LTSP clients to the DHCP server configuration. This is a ISC Dhcpd issue and not really pertaining LTSP. 3. How can you even experiment with LTSP without causing DHCP havoc and irritating your companies intranet police? Are you all on disconnected networks? Configure the LTSP dhcp server to listen to a different port and use Etherboot images (floppy or cdrom) to boot your ltsp clients. The Etherboot boot images can use a different bootp port number and will only query your dhcp server. See www.rom-o-matic.net for information on how to obtain such images. You can get away without a special dhcp server, you just need to hand over to you LTSP booting clients the boot loader (pxelinux if using pxe or the path to the tftp server if using Etherboot). You just need to understand the basics of booting a LTSP client first. -- mitu - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP conflict question
Cristi Mitrana wrote: On 9/7/06, Fred Clewis [EMAIL PROTECTED] wrote: Hi, I'm a LTSP and DHCP noob, and need to understand how I should work with a LTSP DHCP server in a large company with it's own DHCP servers. So when the LTSP workstation starts, it broadcasts for a DHCP server to meet it's needs. My questions below: 2. What is to keep other DHCP computers in the company not wanting to use LTSP from accidentally finding my LTSP DHCP server? Configure your dhcp LTSP server to not give out leases to unknown clients and only add known LTSP clients to the DHCP server configuration. This is a ISC Dhcpd issue and not really pertaining LTSP. Or try to use other subnet for LTSP server and terminals if possible. (subnet can be 2 or 255^2 IP's - as much as you need) 've a nice day! JK -- Ing. Jan Kunder jan.kunder-HATESPAM-gmail.com http://www.kunder.sk JKjkjk rozpmnqestka - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP conflict question
Dear All: Interesting discussion! Thanks for the food for thought. My $0.02 worth is inserted below... Yours Truly! Krishna On Thu, 7 Sep 2006, Cristi Mitrana wrote: On 9/7/06, Fred Clewis [EMAIL PROTECTED] wrote: Hi, I'm a LTSP and DHCP noob, and need to understand how I should work with a LTSP DHCP server in a large company with it's own DHCP servers. So when the LTSP workstation starts, it broadcasts for a DHCP server to meet it's needs. My questions below: 1. If I am in a large company intranet network situation and introduce an LTSP server into that network, how will my LTSP workstations (which may be in other parts of the country) find my LTSP DHCP server? They won't, because LTSP will not work over WAN. Actually, I think it can be made to work if you're truly committed. It is not likely to be worth the trouble, though - especially since there are so many other alternatives available. 2. What is to keep other DHCP computers in the company not wanting to use LTSP from accidentally finding my LTSP DHCP server? I recommend having only one DHCP server active on the ONE subnet where you'll have true LTSP clients. Despite the fact that other setups can be made to work, it's just asking for trouble to have more than one going. What you need for running over subnet boundaries is something more like Thinstation - see http://www.thinstation.org/ for more (don't worry about their hardware being required - it's not.) Configure your dhcp LTSP server to not give out leases to unknown clients and only add known LTSP clients to the DHCP server configuration. This is a ISC Dhcpd issue and not really pertaining LTSP. This won't be an issue at all if you run only one DHCP server per subnet. You'll still want to recognize individual MAC addresses and hand out a fixed IP address for that station in the majority of cases, with a config that matches the hardware at that station. 3. How can you even experiment with LTSP without causing DHCP havoc and irritating your companies intranet police? Are you all on disconnected networks? Not disconnected! Truly connected, probably at high speed, too. It's just a matter of where you get the lease, etc.; it should be local. Configure the LTSP dhcp server to listen to a different port and use Etherboot images (floppy or cdrom) to boot your ltsp clients. The Etherboot boot images can use a different bootp port number and will only query your dhcp server. See www.rom-o-matic.net for information on how to obtain such images. You can also have the remote clients use an image from a floppy or cdrom and skip DHCP altogether. Or simply do an X login over the Internet. One way I had success with was to use the options in a SUSE 10 (installed linux) login screen to connect to the LTSP server itself; the only flaw was in the case of an application that required a specific screen font that wasn't there (when there's a difference between the X fonts available - and expected - in the LTSP tree and what's on the machine that is logging in.) You can get away without a special dhcp server, you just need to hand over to you LTSP booting clients the boot loader (pxelinux if using pxe or the path to the tftp server if using Etherboot). You just need to understand the basics of booting a LTSP client first. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP Failure
Thank you for the willingness to help. Michael Crider of Howell-Oregon Electric Cooperative assisted me greatly by giving me a phone call and being willing to temporarily post some of the April LTSP releases of the 2.6.16 kernel.He provided the following files: ltsp-kernel-2.6.16.1-ltsp-2-0-i386.ltsp ltsp-kernel-2.6.16.1-ltsp-2-0-i386.tgz ltsp-modules-2.6.16.1-ltsp-2-0-i386.ltsp ltsp-modules-2.6.16.1-ltsp-2-0-i386.tgz Which did in fact work to get my Neoware e90 (with a Via Rhine II nic) running. I'm sure that anyone else with this problem should be able to get things going. Unfortunately, I do not have the ability to post these files myself for download, but if you are still in search of these files as a solution to the DHCP problems, I'd be willing to try to arrange to send them directly to you if you desire. Thank you again to everyone involved. Jeremy Young Programmer/Analyst O'Reilly Auto Parts [EMAIL PROTECTED] Jim McQuillan [EMAIL PROTECTED] To 08/31/2006 23:28 [EMAIL PROTECTED] cc Ltsp-discuss@lists.sourceforge.net, [EMAIL PROTECTED] Subject Re: [Ltsp-discuss] DHCP Failure I will try producing a 2.6.16 kernel package to solve the Rhine problems. The problem is I just moved into a new office, and i'm still sorting out all my networking, and I won't have my development server back online until at least saturday. Jim McQuillan [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Greetings everyone, I work for a company that is investigating deploying LTSP at each of our retail locations with Visara and Neoware thin-clients. We currently have approximately 1500 locations, with 5 - 20 clients per location. I've downloaded and installed LTSP 4.2 update 4 on a Suse Professional 9.3 box, and when PXE booting a Neoware e90 (with a Via Rhine II nic), the initial DHCP portion works excellently, and we get connected to the TFTP server. Following this, it displays the following: Running /linuxrc Mounting /proc input: AT Translated Set 2 keyboard as /class/input/input0 linuxrc: Installing via-rhine driver modprobe via-rhine insmod /lib/modules/2.6.17.8-ltsp-1/kernel/drivers/net/via-rhine.ko via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 ACPI: PCI Interrupt :00:12.0[A] - Link [LNKA] - GSI 11 (level, low) - IRQ 11 eth0: VIA Rhine II at 0x1e400, 00:e0:c5:57:71:0b, IRQ 11. eth0: MII PHY found at address 1, status 0x786d advertising 01e1 Link 41e1. Running dhcpcd on port 67 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 input: ImPS/2 Generic Wheel Mouse as /class/input/input1 ERROR! dhcpcd failed! Kernel panic - not syncing: Attempted to kill init! -- At this point it hangs indefinitely, and I can go no further. I'd like to attempt to use the 2.6.16 kernel packages from LTSP, but I cannot find anywhere to download them. I've noticed other people recently asking a similar question regarding problems that were solved reverting from the 2.6.17 kernel to the 2.6.16. I've compiled kernels before, but I don't think it would be a wise use of my time to download the source to 2.6.16 and attempt to re-create the already created kernel packages and modules provided by LTSP. If the kernel itself isn't available, I'd be willing to put forth the effort if a config file was available (The one that selects which options should be compiled into the kernel, which ones should be insertable as modules, and which are excluded). Sorry to be extra wordy, but I just looked at my local package cache, and if the previous version of these two files could be made available, I'd be extremely happy. Maybe on a mirror that keeps old packages? ltsp-kernel-2.6.17.8-ltsp-1-0-i386.tgz ltsp-modules-2.6.17.8-ltsp-1-0-i386.tgz Additionally
[Ltsp-discuss] DHCP Failure
Greetings everyone, I work for a company that is investigating deploying LTSP at each of our retail locations with Visara and Neoware thin-clients. We currently have approximately 1500 locations, with 5 - 20 clients per location. I've downloaded and installed LTSP 4.2 update 4 on a Suse Professional 9.3 box, and when PXE booting a Neoware e90 (with a Via Rhine II nic), the initial DHCP portion works excellently, and we get connected to the TFTP server. Following this, it displays the following:Running /linuxrcMounting /procinput: AT Translated Set 2 keyboard as /class/input/input0linuxrc: Installing via-rhine drivermodprobe via-rhineinsmod /lib/modules/2.6.17.8-ltsp-1/kernel/drivers/net/via-rhine.kovia-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald BeckerACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11ACPI: PCI Interrupt :00:12.0[A] - Link [LNKA] - GSI 11 (level, low) - IRQ 11eth0: VIA Rhine II at 0x1e400, 00:e0:c5:57:71:0b, IRQ 11.eth0: MII PHY found at address 1, status 0x786d advertising 01e1 Link 41e1.Running dhcpcd on port 67eth0: link up, 100Mbps, full-duplex, lpa 0x41E1input: ImPS/2 Generic Wheel Mouse as /class/input/input1ERROR! dhcpcd failed!Kernel panic - not syncing: Attempted to kill init!--At this point it hangs indefinitely, and I can go no further. I'd like to attempt to use the 2.6.16 kernel packages from LTSP, but I cannot find anywhere to download them. I've noticed other people recently asking a similar question regarding problems that were solved reverting from the 2.6.17 kernel to the 2.6.16. I've compiled kernels before, but I don't think it would be a wise use of my time to download the source to 2.6.16 and attempt to re-create the already created kernel packages and modules provided by LTSP. If the kernel itself isn't available, I'd be willing to put forth the effort if a config file was available (The one that selects which options should be compiled into the kernel, which ones should be insertable as modules, and which are excluded). Sorry to be extra wordy, but I just looked at my local package cache, and if the previous version of these two files could be made available, I'd be extremely happy. Maybe on a mirror that keeps old packages? ltsp-kernel-2.6.17.8-ltsp-1-0-i386.tgzltsp-modules-2.6.17.8-ltsp-1-0-i386.tgzAdditionally, if anyone has direct experience with this problem, and can tell me that I'm barking up the wrong tree, then that would be valuable as well. I'm very excited about being involved in this project, and with the potential deployment of 10,000 clients, I would be very interested in convincing my bosses to allow my work to be contributed back to the community. Jeremy YoungProgrammer/AnalystO'Reilly Auto Parts(417) 862-2674 x1858[EMAIL PROTECTED] - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642_ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP Failure
I've compiled kernels before, but I don't think it would be a wise use of my time to download the source to 2.6.16 and attempt to re-create the already created kernel packages and modules provided by LTSP. If the kernel itself isn't available, I'd be willing to put forth the effort if a config file was available (The one that selects which options should be compiled into the kernel, which ones should be insertable as modules, and which are excluded). Helo, You could find the kernel config files in the kernel kit on the LTSP wiki web site. Just download the kernel kit plus the kernel source. The kernel kit will provide you the configuraation files used to compile LTSP kernels. Then conpile the kernel as described on the LTSP site (just follow the steps one after one). ++ Nicolas - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP Failure
I will try producing a 2.6.16 kernel package to solve the Rhine problems. The problem is I just moved into a new office, and i'm still sorting out all my networking, and I won't have my development server back online until at least saturday. Jim McQuillan [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Greetings everyone, I work for a company that is investigating deploying LTSP at each of our retail locations with Visara and Neoware thin-clients. We currently have approximately 1500 locations, with 5 - 20 clients per location. I've downloaded and installed LTSP 4.2 update 4 on a Suse Professional 9.3 box, and when PXE booting a Neoware e90 (with a Via Rhine II nic), the initial DHCP portion works excellently, and we get connected to the TFTP server. Following this, it displays the following: Running /linuxrc Mounting /proc input: AT Translated Set 2 keyboard as /class/input/input0 linuxrc: Installing via-rhine driver modprobe via-rhine insmod /lib/modules/2.6.17.8-ltsp-1/kernel/drivers/net/via-rhine.ko via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 ACPI: PCI Interrupt :00:12.0[A] - Link [LNKA] - GSI 11 (level, low) - IRQ 11 eth0: VIA Rhine II at 0x1e400, 00:e0:c5:57:71:0b, IRQ 11. eth0: MII PHY found at address 1, status 0x786d advertising 01e1 Link 41e1. Running dhcpcd on port 67 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 input: ImPS/2 Generic Wheel Mouse as /class/input/input1 ERROR! dhcpcd failed! Kernel panic - not syncing: Attempted to kill init! -- At this point it hangs indefinitely, and I can go no further. I'd like to attempt to use the 2.6.16 kernel packages from LTSP, but I cannot find anywhere to download them. I've noticed other people recently asking a similar question regarding problems that were solved reverting from the 2.6.17 kernel to the 2.6.16. I've compiled kernels before, but I don't think it would be a wise use of my time to download the source to 2.6.16 and attempt to re-create the already created kernel packages and modules provided by LTSP. If the kernel itself isn't available, I'd be willing to put forth the effort if a config file was available (The one that selects which options should be compiled into the kernel, which ones should be insertable as modules, and which are excluded). Sorry to be extra wordy, but I just looked at my local package cache, and if the previous version of these two files could be made available, I'd be extremely happy. Maybe on a mirror that keeps old packages? ltsp-kernel-2.6.17.8-ltsp-1-0-i386.tgz ltsp-modules-2.6.17.8-ltsp-1-0-i386.tgz Additionally, if anyone has direct experience with this problem, and can tell me that I'm barking up the wrong tree, then that would be valuable as well. I'm very excited about being involved in this project, and with the potential deployment of 10,000 clients, I would be very interested in convincing my bosses to allow my work to be contributed back to the community. Jeremy Young Programmer/Analyst O'Reilly Auto Parts (417) 862-2674 x1858 [EMAIL PROTECTED] - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] dhcp substring question
If you use get-lease-hostnames instead of use-host-decl in your
dhcpd.conf, the hostnames passed to the thin client will come
from /etc/hosts (or DNS). So, you can use that trick in the generic
section, and then just have hostname entries in /etc/hosts for each IP
in the range.
NOTE:
Be sure to put:
ip hostname
in /etc/hosts and NOT
ip hostname.domainname
if you use hostnames in your lts.conf file when you specify settings.
HTH,
-Gideon
On Tue, 2006-08-15 at 16:22 +0200, Richard Bos wrote:
This piece of magic looks very interesting as it may prevent a lot of system
administration work:
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.100 192.168.0.199;
if substring (option vendor-class-identifier, 0, 9) = PXEClient {
filename /tftpboot/lts/2.4.26-ltsp-3/pxelinux.0;
}
else{
filename /tftpboot/lts/vmlinuz-2.4.26-ltsp-3;
}
}
It's from: http://wiki.ltsp.org/twiki/bin/view/Ltsp/DhcpExample
But will this allow the current locale device impletation still to keep on
working. AFAIK the current locale device implementation needs names to be
able to work. In the configuration above no names are configured, in
contradiction to my dhcp file, that has e.g.:
host ws01 {
hardware ethernet ;
fixed-address ...;
filename;
}
if the host { } is left out of configuration file, the workstation may get
different ip addresses each times it connects to the server. It will get the
name that corresponds to the ip address from the DNS server so, all in all it
looks to me that substring dhcp configuration will just work, but a
confirmation would be nice.
A related question to this, in case the thin client needs requires additional
options, can this work in combination with the substring dhcp
configuration? If this can work how should it be done? If;
host ws15 {
hardware ethernet ;
fixed-address ...;
filename;
option option-128 .;
option option-129 .;
}
Doesn't the 'host ws15' configuration conflict with the name given out by the
DNS server?
Perhaps I get it, the ip range of the subnet of the substring dhcp
configuration, should be outside the ip addresses that the host { } part
gives out. Is that correct?
--
Gideon Romm | Proud LTSP Developer
[EMAIL PROTECTED]
Support LTSP! Buy your hardware at:
www.DisklessWorkstations.com
www.DisklessThinClients.com
(use coupon code: LTSP5P for 5% off thin clients from DisklessThinClients.com)
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] dhcp substring question
This piece of magic looks very interesting as it may prevent a lot of system
administration work:
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.100 192.168.0.199;
if substring (option vendor-class-identifier, 0, 9) = PXEClient {
filename /tftpboot/lts/2.4.26-ltsp-3/pxelinux.0;
}
else{
filename /tftpboot/lts/vmlinuz-2.4.26-ltsp-3;
}
}
It's from: http://wiki.ltsp.org/twiki/bin/view/Ltsp/DhcpExample
But will this allow the current locale device impletation still to keep on
working. AFAIK the current locale device implementation needs names to be
able to work. In the configuration above no names are configured, in
contradiction to my dhcp file, that has e.g.:
host ws01 {
hardware ethernet ;
fixed-address ...;
filename;
}
if the host { } is left out of configuration file, the workstation may get
different ip addresses each times it connects to the server. It will get the
name that corresponds to the ip address from the DNS server so, all in all it
looks to me that substring dhcp configuration will just work, but a
confirmation would be nice.
A related question to this, in case the thin client needs requires additional
options, can this work in combination with the substring dhcp
configuration? If this can work how should it be done? If;
host ws15 {
hardware ethernet ;
fixed-address ...;
filename;
option option-128 .;
option option-129 .;
}
Doesn't the 'host ws15' configuration conflict with the name given out by the
DNS server?
Perhaps I get it, the ip range of the subnet of the substring dhcp
configuration, should be outside the ip addresses that the host { } part
gives out. Is that correct?
--
TIA,
Richard Bos
Without a home the journey is endless
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] dhcp substring question
Am Dienstag, den 15.08.2006, 16:22 +0200 schrieb Richard Bos:
This piece of magic looks very interesting as it may prevent a lot of system
administration work:
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.100 192.168.0.199;
if substring (option vendor-class-identifier, 0, 9) = PXEClient {
filename /tftpboot/lts/2.4.26-ltsp-3/pxelinux.0;
}
else{
filename /tftpboot/lts/vmlinuz-2.4.26-ltsp-3;
}
}
It's from: http://wiki.ltsp.org/twiki/bin/view/Ltsp/DhcpExample
But will this allow the current locale device impletation still to keep on
working. AFAIK the current locale device implementation needs names to be
able to work. In the configuration above no names are configured, in
contradiction to my dhcp file, that has e.g.:
host ws01 {
hardware ethernet ;
fixed-address ...;
filename;
}
if the host { } is left out of configuration file, the workstation may get
different ip addresses each times it connects to the server. It will get the
name that corresponds to the ip address from the DNS server so, all in all it
looks to me that substring dhcp configuration will just work, but a
confirmation would be nice.
You can copy those five lines if substring {} else {}
and paste them instead of any filename line, be that in a host {}
statement or not. It will work fine.
A related question to this, in case the thin client needs requires additional
options, can this work in combination with the substring dhcp
configuration? If this can work how should it be done? If;
host ws15 {
hardware ethernet ;
fixed-address ...;
filename;
option option-128 .;
option option-129 .;
}
Yep, and you can replace the filename line as explained above, if you
wish.
You could also have only one filename line in the global part of the
dhcpd.conf, which then is the default if nothing else is given in the
host{} specific sections.
Doesn't the 'host ws15' configuration conflict with the name given out by the
DNS server?
Nope, they do not necessarily interfere.
Perhaps I get it, the ip range of the subnet of the substring dhcp
configuration, should be outside the ip addresses that the host { } part
gives out. Is that correct?
You can have both, but the range should better not include IP
addresses that appear in separate host sections. I seem to remember
that dhcpd is intelligent enough to not hand out IP addresses out of the
range that also are in host{} statements, but I'd not guarantee for
that.
Anselm
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP conflict
Am Montag, den 17.07.2006, 10:54 -0400 schrieb Krishna Murphy: Hey- It appears that I need to have two DHCP servers running on one sub-net. Apparently this causes a conflict with one in particular (inside a router provided by an ISP) and the DHCP3 server under Debian that I'm using to identify the workstations (using use-host-decl-names on; to make it so) and thus make the things that pertain to each of them apply. It works fine with a couple of different little wireless routers (one from Vonage) at my development/shop site, but not with the one from the ISP. Perhaps that one sends the filename parameter (for whatever reason). So - I am given to understand that there is an option to make your dhcp server authoritative and that may help in this situation. Does anyone have a good handle on that to share? I'd really like to resolve this and not have to hack things up too much (like segregating my network into non-terminals only here vs. terminals only over here.) Making it authoritative will probably not help too much. When two DHCP offers are sent to the client and both look valid (i.e. contain a filename or root-path resp.), the client will probably pick the one that arrived first. If that happens to be the router's packet, bad luck. I see two viable strategies for you: 1/ Use the alternate DHCP ports (only possible with Etherboot and LTSP WITHOUT vendor PXE) 2/ Create a separate subnet. Reconfiguring the router to send out valid root-path and next-server and filename is probably not possible anyway. Regards, Anselm - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP conflict
Anselm- It looks like I can use a single DHCP3 server to do both dynamically- assigned addresses to non-MAC-identified PCs as well as the ones we have to have MAC-based entries for and assign statically. It's just a matter of leaving the get-lease-hostnames true; statement out so it does not conflict with the use-host-decl-names on; statement required for the MAC- based entries. Thanks for your help! -Krishna On Tue, 18 Jul 2006, Anselm Martin Hoffmeister wrote: Am Montag, den 17.07.2006, 10:54 -0400 schrieb Krishna Murphy: Hey- It appears that I need to have two DHCP servers running on one sub-net. Apparently this causes a conflict with one in particular (inside a router provided by an ISP) and the DHCP3 server under Debian that I'm using to identify the workstations (using use-host-decl-names on; to make it so) and thus make the things that pertain to each of them apply. It works fine with a couple of different little wireless routers (one from Vonage) at my development/shop site, but not with the one from the ISP. Perhaps that one sends the filename parameter (for whatever reason). So - I am given to understand that there is an option to make your dhcp server authoritative and that may help in this situation. Does anyone have a good handle on that to share? I'd really like to resolve this and not have to hack things up too much (like segregating my network into non-terminals only here vs. terminals only over here.) Making it authoritative will probably not help too much. When two DHCP offers are sent to the client and both look valid (i.e. contain a filename or root-path resp.), the client will probably pick the one that arrived first. If that happens to be the router's packet, bad luck. I see two viable strategies for you: 1/ Use the alternate DHCP ports (only possible with Etherboot and LTSP WITHOUT vendor PXE) 2/ Create a separate subnet. Reconfiguring the router to send out valid root-path and next-server and filename is probably not possible anyway. Regards, Anselm - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP conflict
On Wednesday 19 July 2006 07:46, [EMAIL PROTECTED] wrote: p.s. unfortunately IRC is blocked so I cannot use IRC while at the school to troubleshoot this issue Can you do ssh? if so ssh port forwarding is magic eg From (even a dynamic ip) home to school: ssh -R 1200:localhost:194 [EMAIL PROTECTED] then at school: irc 1200 at localhost or from school: ssh -C -g -L 5678:localhost:194 [EMAIL PROTECTED] irc 5678 at localhost James - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] DHCP conflict
Hey- It appears that I need to have two DHCP servers running on one sub-net. Apparently this causes a conflict with one in particular (inside a router provided by an ISP) and the DHCP3 server under Debian that I'm using to identify the workstations (using use-host-decl-names on; to make it so) and thus make the things that pertain to each of them apply. It works fine with a couple of different little wireless routers (one from Vonage) at my development/shop site, but not with the one from the ISP. So - I am given to understand that there is an option to make your dhcp server authoritative and that may help in this situation. Does anyone have a good handle on that to share? I'd really like to resolve this and not have to hack things up too much (like segregating my network into non-terminals only here vs. terminals only over here.) -Krishna p.s. For more background, see http://marc.theaimsgroup.com/?l=ltsp-discussm=112736488402825w=2 - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] dhcp query (Krishna Murphy)
Jim- You're right, there was a range statement left over in my dhcp.conf from the past when I was (unwisely) doing DHCP with both a pool of addresses and specific MAC addresses. I had picked up on the need to comment out the get-lease-hostnames true; line when using use-host-decl-nameson; from one of the wiki pages, but the line with the range statement escaped my notice. If anyone knows a really good BASIC tutorial on DHCP, perhaps that would be worth linking on the wiki as well as the stuff specific to LTSP. Thanks, as always, for your leadership. LTSP is a great contribution to the community, and I appreciate it enormously. -Krishna On Sat, 17 Jun 2006, [EMAIL PROTECTED] wrote: On Saturday 17 June 2006 03:03, [EMAIL PROTECTED] wrote: FYI, my router will do that if the DHCP server on the server doesn't give it an address first. But I'm pretty sure my setup is similar to Joey's and I have seen addresses assigned that were not specified in the dhcpd.conf. Guys, there is no magic, and it's logged EITHER you have a pool OR you hand out addresses by MAC (or both). Why don't you post the log of where you think I have seen addresses assigned that were not specified in the dhcpd.conf. James _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] dhcp next-server problems
On Fri, 16 Jun 2006 06:30:20 +0100, toman [EMAIL PROTECTED] wrote: Hi, Does anyone know if the next-server command works in the version of dhcpd that Ubuntu (dapper) uses ? Let me ask it this way: what is it supposed to do, and does it actually do that? I was trying to split off LTSP services from our DHCP/DNS/LTSP box that I recently upgraded to Dapper. (The upgrade is a whole different nightmare.) After much fussing around I had to move my boot images back to my DHCP server, because that seemed to be the only TFTP server it would query. Ideas? This seems to work on my suse machines at home. The changes that made next-server NECESSARY happened somewhere in the development of dhcp3. It should work in older versions, and it specifies where a machine should look next for it's files after getting a DHCP lease. The dhcp3-server package in Dapper, version 3.0.3, is late enough to mean that the next-server bit is necessary for PXE and Etherboot to work. Regardless, it should do what it's meant to do in any version of dhcp3. There will be other dhcp packages in Dapper, just as there are in debian, but that's the one I can confirm does what it should. We use next-server here to mean that our one DHCP server will point our clients to the LTSP box for it's kernel, and not the DHCP box itself, most handy. -- From Ben Green _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] dhcp query
Joey,
There's nothing in your dhcpd.conf file that would cause it to give out IP
addresses to other clients.
So, i'm not sure how it could possibly be doing that.
Jim McQuillan
[EMAIL PROTECTED]
On Thu, June 15, 2006 11:41 pm, Joey S. Eisma wrote:
hi!
my dhcp (ltsp) server responds, gives out addresses to clients not on
the list.
what i want to do is ignore other requests other than those indicated
(via MAC).
=
ddns-update-style none;
default-lease-time 21600;
max-lease-time 21600;
option subnet-mask 255.255.254.0;
option broadcast-address192.168.1.255;
option routers 192.168.0.20;
option domain-name-servers192.168.0.20;
option domain-name domain.com;
option root-path192.168.0.20:/opt/ltsp/i386;
option option-128 code 128 = string;
option option-129 code 129 = text;
option option-128 e4:45:74:68:00:00;
option option-129 MOPTS=nolock,ro,rsize=4096,wsize=4096,proto=tcp;
subnet 192.168.0.0 netmask 255.255.254.0 {
use-host-decl-names on;
option log-servers 192.168.0.20;
host ws001 {
hardware ethernet 00:50:DA:8D:78:BC;
fixed-address 192.168.1.70;
filename
/lts/vmlinuz-2.4.26-ltsp-3;
}
}
=
thank you!
joey
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] dhcp query
FYI, my router will do that if the DHCP server on the server doesn't give
it an address first. But I'm pretty sure my setup is similar to Joey's and
I have seen addresses assigned that were not specified in the dhcpd.conf.
-Krishna
On Fri, 16 Jun 2006, Jim McQuillan wrote:
Joey,
There's nothing in your dhcpd.conf file that would cause it to give out IP
addresses to other clients.
So, i'm not sure how it could possibly be doing that.
Jim McQuillan
[EMAIL PROTECTED]
On Thu, June 15, 2006 11:41 pm, Joey S. Eisma wrote:
hi!
my dhcp (ltsp) server responds, gives out addresses to clients not on
the list.
what i want to do is ignore other requests other than those indicated
(via MAC).
=
ddns-update-style none;
default-lease-time 21600;
max-lease-time 21600;
option subnet-mask 255.255.254.0;
option broadcast-address192.168.1.255;
option routers 192.168.0.20;
option domain-name-servers192.168.0.20;
option domain-name domain.com;
option root-path192.168.0.20:/opt/ltsp/i386;
option option-128 code 128 = string;
option option-129 code 129 = text;
option option-128 e4:45:74:68:00:00;
option option-129 MOPTS=nolock,ro,rsize=4096,wsize=4096,proto=tcp;
subnet 192.168.0.0 netmask 255.255.254.0 {
use-host-decl-names on;
option log-servers 192.168.0.20;
host ws001 {
hardware ethernet 00:50:DA:8D:78:BC;
fixed-address 192.168.1.70;
filename
/lts/vmlinuz-2.4.26-ltsp-3;
}
}
=
thank you!
joey
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] dhcp query (Krishna Murphy)
On Saturday 17 June 2006 03:03, [EMAIL PROTECTED] wrote: FYI, my router will do that if the DHCP server on the server doesn't give it an address first. But I'm pretty sure my setup is similar to Joey's and I have seen addresses assigned that were not specified in the dhcpd.conf. Guys, there is no magic, and it's logged EITHER you have a pool OR you hand out addresses by MAC (or both). Why don't you post the log of where you think I have seen addresses assigned that were not specified in the dhcpd.conf. James _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] dhcp next-server problems
Ben Green wrote: On Fri, 16 Jun 2006 06:30:20 +0100, toman [EMAIL PROTECTED] wrote: Hi, Does anyone know if the next-server command works in the version of dhcpd that Ubuntu (dapper) uses ? Let me ask it this way: what is it supposed to do, and does it actually do that? I was trying to split off LTSP services from our DHCP/DNS/LTSP box that I recently upgraded to Dapper. (The upgrade is a whole different nightmare.) After much fussing around I had to move my boot images back to my DHCP server, because that seemed to be the only TFTP server it would query. Ideas? This seems to work on my suse machines at home. The changes that made next-server NECESSARY happened somewhere in the development of dhcp3. It should work in older versions, and it specifies where a machine should look next for it's files after getting a DHCP lease. The dhcp3-server package in Dapper, version 3.0.3, is late enough to mean that the next-server bit is necessary for PXE and Etherboot to work. Regardless, it should do what it's meant to do in any version of dhcp3. There will be other dhcp packages in Dapper, just as there are in debian, but that's the one I can confirm does what it should. We use next-server here to mean that our one DHCP server will point our clients to the LTSP box for it's kernel, and not the DHCP box itself, most handy. Well thanks, but as I said this seems to work on my suse 10.0 boxes at home, but not on the dapper-upgraded machine at work. I've decided it doesn't matter, as the TFTP server only gets hit once on booting a terminal, and I would rather have only one TFTP server up on the network. J. Toman _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] dhcp query
hi!
my dhcp (ltsp) server responds, gives out addresses to clients not on
the list.
what i want to do is ignore other requests other than those indicated
(via MAC).
=
ddns-update-style none;
default-lease-time 21600;
max-lease-time 21600;
option subnet-mask 255.255.254.0;
option broadcast-address192.168.1.255;
option routers 192.168.0.20;
option domain-name-servers192.168.0.20;
option domain-name domain.com;
option root-path192.168.0.20:/opt/ltsp/i386;
option option-128 code 128 = string;
option option-129 code 129 = text;
option option-128 e4:45:74:68:00:00;
option option-129 MOPTS=nolock,ro,rsize=4096,wsize=4096,proto=tcp;
subnet 192.168.0.0 netmask 255.255.254.0 {
use-host-decl-names on;
option log-servers 192.168.0.20;
host ws001 {
hardware ethernet 00:50:DA:8D:78:BC;
fixed-address 192.168.1.70;
filename /lts/vmlinuz-2.4.26-ltsp-3;
}
}
=
thank you!
joey
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] dhcp next-server problems
Hi, Does anyone know if the next-server command works in the version of dhcpd that Ubuntu (dapper) uses ? Let me ask it this way: what is it supposed to do, and does it actually do that? I was trying to split off LTSP services from our DHCP/DNS/LTSP box that I recently upgraded to Dapper. (The upgrade is a whole different nightmare.) After much fussing around I had to move my boot images back to my DHCP server, because that seemed to be the only TFTP server it would query. Ideas? This seems to work on my suse machines at home. J. Toman _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP OFFER never gets to workstation
Am Freitag, den 24.03.2006, 00:48 -0700 schrieb Dormition Skete:
I have a very perplexing problem with dhcp. I had to rebuild my server due
to a hard disk failure, and I decided to try SuSE 10.0 for a change. I have
installed LTSP several times on Redhat and Slackware without any significant
problems.
With SuSE 10.0, however, my dhcpd daemon receives the request, and offers
the correct IP Address response for the workstation. The workstation never
gets it, though. It just hangs on Searching for server (DHCP) A
second LTSP workstation does the same thing, but it gives a message saying
No IP address.
Now for the really perplexing part. I gave up on SuSE because I didn't want
to fight with this, or bother any of you with it. But now that I've put
Fedora 5 on it, it does the exact same thing! I just had Red Hat Enterprise
Linux 4 on it, and it worked fine, so something must have changed since it
came out, that both FC5 and SuSE 10 now have.
I have the firewall turned off, so it should not be getting in the way. The
# iptables -L -v command gives a response like what the LTSP
troubleshooting section says means that it is not getting in the way.
Does anyone have any idea what could be going wrong, and how I can get this
to work?
You seem to be missing the next-server statement in dhcpd.conf.
Technical explanation:
In between two dhcp daemon releases (3.0.2 and 3.0.3) the ISC people
decided to change default values. Older dhcpd versions would, if not
specifically configured to do else, send a next-server field with the
IP of the DHCP server. This field defaults to be empty now.
Of course, Etherboot cannot work correctly if there is no information
which server the boot files shall be fetched from, so DHCP offers
without the next-server information are discarded.
Fix:
Add a line
next-server 192.168.0.2;
with the ip address of your tftp server (probably the same machine as
dhcpd server, isn't it?)
I would *greatly* appreciate some help here.
Below is my dhcpd.conf file, which has previously worked fine for the past
three years, I think.
# Sample configuration file for ISCD dhcpd
#
# Make changes to this file and copy it to /etc/dhcpd.conf
#
ddns-update-style none;
default-lease-time21600;
max-lease-time21600;
option subnet-mask255.255.255.0;
option broadcast-address 192.168.0.255;
option routers192.168.0.2;
option domain-name-servers192.168.0.2;
option domain-nameds;
option root-path 192.168.0.2:/opt/ltsp/i386;
** somewhere like here.
option option-128 code 128 = string;
option option-129 code 129 = text;
log-facility local7;
shared-network WORKSTATIONS {
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.100 192.168.0.254;
}
}
group {
use-host-decl-names on;
option log-servers192.168.0.2;
host ws101 {
# Sony
hardware ethernet 00:04:5a:7e:75:10;
fixed-address 192.168.0.101;
filename /lts/vmlinuz-2.6.9-ltsp-3;
##option option-128 e4:45:74:68:00:00; #This is NOT a MAC
address
##option option-129 NIC=ne IO=0x300;
HTH
Anselm
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP OFFER never gets to workstation
That's it!
Thank you all, very, very much!
I really appreciate it a lot.
From: Anselm Martin Hoffmeister [EMAIL PROTECTED]
To: Dormition Skete [EMAIL PROTECTED]
CC: ltsp-discuss@lists.sourceforge.net
Subject: Re: [Ltsp-discuss] DHCP OFFER never gets to workstation
Date: Fri, 24 Mar 2006 08:56:21 +0100
Am Freitag, den 24.03.2006, 00:48 -0700 schrieb Dormition Skete:
I have a very perplexing problem with dhcp. I had to rebuild my server
due
to a hard disk failure, and I decided to try SuSE 10.0 for a change. I
have
installed LTSP several times on Redhat and Slackware without any
significant
problems.
With SuSE 10.0, however, my dhcpd daemon receives the request, and
offers
the correct IP Address response for the workstation. The workstation
never
gets it, though. It just hangs on Searching for server (DHCP) A
second LTSP workstation does the same thing, but it gives a message
saying
No IP address.
Now for the really perplexing part. I gave up on SuSE because I didn't
want
to fight with this, or bother any of you with it. But now that I've put
Fedora 5 on it, it does the exact same thing! I just had Red Hat
Enterprise
Linux 4 on it, and it worked fine, so something must have changed since
it
came out, that both FC5 and SuSE 10 now have.
I have the firewall turned off, so it should not be getting in the way.
The
# iptables -L -v command gives a response like what the LTSP
troubleshooting section says means that it is not getting in the way.
Does anyone have any idea what could be going wrong, and how I can get
this
to work?
You seem to be missing the next-server statement in dhcpd.conf.
Technical explanation:
In between two dhcp daemon releases (3.0.2 and 3.0.3) the ISC people
decided to change default values. Older dhcpd versions would, if not
specifically configured to do else, send a next-server field with the
IP of the DHCP server. This field defaults to be empty now.
Of course, Etherboot cannot work correctly if there is no information
which server the boot files shall be fetched from, so DHCP offers
without the next-server information are discarded.
Fix:
Add a line
next-server 192.168.0.2;
with the ip address of your tftp server (probably the same machine as
dhcpd server, isn't it?)
I would *greatly* appreciate some help here.
Below is my dhcpd.conf file, which has previously worked fine for the
past
three years, I think.
# Sample configuration file for ISCD dhcpd
#
# Make changes to this file and copy it to /etc/dhcpd.conf
#
ddns-update-style none;
default-lease-time21600;
max-lease-time21600;
option subnet-mask255.255.255.0;
option broadcast-address 192.168.0.255;
option routers192.168.0.2;
option domain-name-servers192.168.0.2;
option domain-nameds;
option root-path 192.168.0.2:/opt/ltsp/i386;
** somewhere like here.
option option-128 code 128 = string;
option option-129 code 129 = text;
log-facility local7;
shared-network WORKSTATIONS {
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.100 192.168.0.254;
}
}
group {
use-host-decl-names on;
option log-servers192.168.0.2;
host ws101 {
# Sony
hardware ethernet 00:04:5a:7e:75:10;
fixed-address 192.168.0.101;
filename /lts/vmlinuz-2.6.9-ltsp-3;
##option option-128 e4:45:74:68:00:00; #This is NOT a MAC
address
##option option-129 NIC=ne IO=0x300;
HTH
Anselm
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] DHCP OFFER never gets to workstation
I have a very perplexing problem with dhcp. I had to rebuild my server due
to a hard disk failure, and I decided to try SuSE 10.0 for a change. I have
installed LTSP several times on Redhat and Slackware without any significant
problems.
With SuSE 10.0, however, my dhcpd daemon receives the request, and offers
the correct IP Address response for the workstation. The workstation never
gets it, though. It just hangs on Searching for server (DHCP) A
second LTSP workstation does the same thing, but it gives a message saying
No IP address.
Now for the really perplexing part. I gave up on SuSE because I didn't want
to fight with this, or bother any of you with it. But now that I've put
Fedora 5 on it, it does the exact same thing! I just had Red Hat Enterprise
Linux 4 on it, and it worked fine, so something must have changed since it
came out, that both FC5 and SuSE 10 now have.
I have the firewall turned off, so it should not be getting in the way. The
# iptables -L -v command gives a response like what the LTSP
troubleshooting section says means that it is not getting in the way.
Does anyone have any idea what could be going wrong, and how I can get this
to work?
I would *greatly* appreciate some help here.
Below is my dhcpd.conf file, which has previously worked fine for the past
three years, I think.
# Sample configuration file for ISCD dhcpd
#
# Make changes to this file and copy it to /etc/dhcpd.conf
#
ddns-update-style none;
default-lease-time21600;
max-lease-time21600;
option subnet-mask255.255.255.0;
option broadcast-address 192.168.0.255;
option routers192.168.0.2;
option domain-name-servers192.168.0.2;
option domain-nameds;
option root-path 192.168.0.2:/opt/ltsp/i386;
option option-128 code 128 = string;
option option-129 code 129 = text;
log-facility local7;
shared-network WORKSTATIONS {
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.100 192.168.0.254;
}
}
group {
use-host-decl-names on;
option log-servers192.168.0.2;
host ws101 {
# Sony
hardware ethernet 00:04:5a:7e:75:10;
fixed-address 192.168.0.101;
filename /lts/vmlinuz-2.6.9-ltsp-3;
##option option-128 e4:45:74:68:00:00; #This is NOT a MAC
address
##option option-129 NIC=ne IO=0x300;
}
host ws102 {
# Packard Bell P1-200
hardware ethernet 00:04:5a:7e:75:28;
fixed-address 192.168.0.102;
filename /lts/vmlinuz-2.6.9-ltsp-3;
}
host ws103 {
# Meteora Dell
hardware ethernet 00:01:02:42:cf:79;
fixed-address 192.168.0.103;
filename /lts/vmlinuz-2.6.9-ltsp-3;
}
host ws104 {
# HTMMeteora Dell
hardware ethernet 00:11:43:ae:ad:c4;
fixed-address 192.168.0.104;
filename /lts/vmlinuz-2.6.9-ltsp-3;
option option-128 e4:45:74:68:00:00; #This is NOT a MAC
address
option option-129 NIC=tg3 IO=0x1677;
}
}
With kind regards,
Peter, hieromonk
Dormition Skete
Our Monastery Website: http://www.DormitionSkete.org
Our Catechetical Website: http://www.TrueOrthodoxy.Info
GOC of Greece Website: http://www.omologitis.org
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] dhcp on pII
am setting up some new compaq en 266 64mb computers in our lan with 3com cards 905c-txm. These are the same cards that boot perfectly off of dell optiplex gx1 350mhz. They seem to boot until they get to the part where I think they hook up to dhcp IP-Config: eth0 hardware address 00:08:c7:ea:3a:0e mtu dhcp RARP They get here then freeze. Does anyone know where I can get some help? -- -- Thanks, James --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP don't start on 172.16.XX.YY network
Sudev Barar wrote: On 12/12/05, DenisG [EMAIL PROTECTED] wrote: Jim McQuillan a écrit : Denis, Look and see if you have a /etc/ltsp/dhcpd.conf file. That is used by Ubuntu's implementation of LTSP. Jim McQuillan [EMAIL PROTECTED] Yes, you were right, once again Jim! I copied my dhcpd.conf to /etc/ltsp/dhcpd.conf and it worked. I didn't find anything about that in the wiki's distrib area (but maybe I didn't search enough...) 8-( Scratching my head. Jim says ltsp will work if /etc/ltsp/dhcpd.conf if set for dhcpd service. And Denis gets LTSP working by copying dhcpd.conf there. I did LTSP install on Ubuntu 5.04 5.10 in last three days four time but everytime ltspadmin created dhcpd.conf in /etc/dhcp3/dhcpd.conf and everything worked!!! The only time you need the dhcpd.conf file in /etc/ltsp/dhcpd.conf is when you are using Ubuntu 5.10 (Breezy), and you've installed the 'ltsp-standalone-server' package made for breezy. If you haven't installed that, then dhcpd is configured as normal, with the config file in /etc/dhcp3/dhcpd.conf Jim. What gives? -- Sudev Barar Learning Linux --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP don't start on 172.16.XX.YY network
Jim McQuillan a écrit : Sudev Barar wrote: 8-( Scratching my head. Jim says ltsp will work if /etc/ltsp/dhcpd.conf if set for dhcpd service. And Denis gets LTSP working by copying dhcpd.conf there. I did LTSP install on Ubuntu 5.04 5.10 in last three days four time but everytime ltspadmin created dhcpd.conf in /etc/dhcp3/dhcpd.conf and everything worked!!! The only time you need the dhcpd.conf file in /etc/ltsp/dhcpd.conf is when you are using Ubuntu 5.10 (Breezy), and you've installed the 'ltsp-standalone-server' package made for breezy. If you haven't installed that, then dhcpd is configured as normal, with the config file in /etc/dhcp3/dhcpd.conf Jim. That's exactly what I did. I wanted to try this package and compare. Are there other things to know when using it? DenisG --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP don't start on 172.16.XX.YY network
Jim McQuillan a écrit : Denis, Look and see if you have a /etc/ltsp/dhcpd.conf file. That is used by Ubuntu's implementation of LTSP. Jim McQuillan [EMAIL PROTECTED] Yes, you were right, once again Jim! I copied my dhcpd.conf to /etc/ltsp/dhcpd.conf and it worked. I didn't find anything about that in the wiki's distrib area (but maybe I didn't search enough...) Thanks again DenisG --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP don't start on 172.16.XX.YY network
On 12/12/05, DenisG [EMAIL PROTECTED] wrote: Jim McQuillan a écrit : Denis, Look and see if you have a /etc/ltsp/dhcpd.conf file. That is used by Ubuntu's implementation of LTSP. Jim McQuillan [EMAIL PROTECTED] Yes, you were right, once again Jim! I copied my dhcpd.conf to /etc/ltsp/dhcpd.conf and it worked. I didn't find anything about that in the wiki's distrib area (but maybe I didn't search enough...) 8-( Scratching my head. Jim says ltsp will work if /etc/ltsp/dhcpd.conf if set for dhcpd service. And Denis gets LTSP working by copying dhcpd.conf there. I did LTSP install on Ubuntu 5.04 5.10 in last three days four time but everytime ltspadmin created dhcpd.conf in /etc/dhcp3/dhcpd.conf and everything worked!!! What gives? -- Sudev Barar Learning Linux --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP don't start on 172.16.XX.YY network
Jim McQuillan a écrit : Denis, Look and see if you have a /etc/ltsp/dhcpd.conf file. That is used by Ubuntu's implementation of LTSP. Jim McQuillan [EMAIL PROTECTED] Thanks I can't see that until monday (I don't carry the server with me when back home!) but I'll tell you. Why put a /etc/ltsp/dhcpd.conf when there is already a /etc/dhcp3-server/dhcpd.conf? DenisG --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP don't start on 172.16.XX.YY network
On 12/10/05, DenisG [EMAIL PROTECTED] wrote: Jim McQuillan a écrit : Denis, Look and see if you have a /etc/ltsp/dhcpd.conf file. That is used by Ubuntu's implementation of LTSP. Jim McQuillan [EMAIL PROTECTED] Thanks I can't see that until monday (I don't carry the server with me when back home!) but I'll tell you. Why put a /etc/ltsp/dhcpd.conf when there is already a /etc/dhcp3-server/dhcpd.conf? In ubuntu it is /etc/dhcp3-server/dhcpd.conf Make sure first you stop eth0 or whatever by ifdown eth0, stop dhcpd by /etc/init.d/dhcp3 stop and then bring up the interface by ifup eth0 and restart dhcpd service by /etc/init.d/dhcp3 restart. Why? Because I found to my surprise that if you change the network IP this is what makes it work. -- Sudev Barar Learning Linux --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP don't start on 172.16.XX.YY network
DenisG wrote: Jim McQuillan a écrit : Denis, Look and see if you have a /etc/ltsp/dhcpd.conf file. That is used by Ubuntu's implementation of LTSP. Jim McQuillan [EMAIL PROTECTED] Thanks I can't see that until monday (I don't carry the server with me when back home!) but I'll tell you. Why put a /etc/ltsp/dhcpd.conf when there is already a /etc/dhcp3-server/dhcpd.conf? You'd have to ask the Ubuntu guys. It doesn't make sense to me either. Jim. DenisG --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP don't start on 172.16.XX.YY network
On Fri, 9 Dec 2005, DenisG wrote:
subnet 172.16.0.0 netmask 255.255.0.0 {
use-host-decl-names on;
option log-servers 172.16.122.10;
}
host cdi5 {
hardware ethernet 00:C0:4F:A9:89:E3;
fixed-address 172.16.122.6;
filename /tftpboot/lts/vmlinuz-2.4.26-ltsp-3;
}
This looks wrong to me.
The host part should be inside the subnet brackets { }
Remove the { above the word host and put it at the bottom.
--
Phil Davey
Computer Officer
Hughes Hall, University of Cambridge
Email [EMAIL PROTECTED]
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP don't start on 172.16.XX.YY network
Phil Davey a écrit :
On Fri, 9 Dec 2005, DenisG wrote:
subnet 172.16.0.0 netmask 255.255.0.0 {
use-host-decl-names on;
option log-servers 172.16.122.10;
}
host cdi5 {
hardware ethernet 00:C0:4F:A9:89:E3;
fixed-address 172.16.122.6;
filename /tftpboot/lts/vmlinuz-2.4.26-ltsp-3;
}
This looks wrong to me.
The host part should be inside the subnet brackets { }
Remove the { above the word host and put it at the bottom.
I saw the whole two possibilities on the net, and tried them, no change...
DenisG
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] DHCP don't start on 172.16.XX.YY network
Hi all
I'm trying to configure a LTSP server (Ubuntu 5.10) on a 172.16.XX.YY
network, but dhcpd refuses to start. Here's my config, I don't
understand what's wrong.
#cat /var/log/syslog
...
Dec 9 13:35:54 ltsp dhcpd: No subnet declaration for eth0 (172.16.122.10).
Dec 9 13:35:54 ltsp dhcpd: ** Ignoring requests on eth0. If this is
not what
Dec 9 13:35:54 ltsp dhcpd:you want, please write a subnet declaration
Dec 9 13:35:54 ltsp dhcpd:in your dhcpd.conf file for the network
segment
Dec 9 13:35:54 ltsp dhcpd:to which interface eth0 is attached. **
Dec 9 13:35:54 ltsp dhcpd:
Dec 9 13:35:54 ltsp dhcpd:
Dec 9 13:35:54 ltsp dhcpd: Not configured to listen on any interfaces!
#ifconfig
eth0 Link encap:Ethernet HWaddr 00:12:3F:A2:D6:D3
inet addr:172.16.122.10 Bcast:172.16.255.255 Mask:255.255.0.0
inet6 addr: fe80::212:3fff:fea2:d6d3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6344 errors:0 dropped:0 overruns:0 frame:0
TX packets:1257 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1619811 (1.5 MiB) TX bytes:211002 (206.0 KiB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:78 errors:0 dropped:0 overruns:0 frame:0
TX packets:78 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6192 (6.0 KiB) TX bytes:6192 (6.0 KiB)
#cat /etc/dhcp3-server/dhcpd.conf
ddns-update-stylenone;
default-lease-time 21600;
max-lease-time 21600;
option subnet-mask 255.255.0.0;
option broadcast-address 172.16.255.255;
option routers 172.16.122.10;
option domain-name-servers 172.16.122.10;
option domain-name ltsp; # --Fix this domain name
option root-path 172.16.122.10:/opt/ltsp/i386;
option option-128 code 128 = string;
option option-129 code 129 = text;
subnet 172.16.0.0 netmask 255.255.0.0 {
use-host-decl-names on;
option log-servers 172.16.122.10;
}
host cdi5 {
hardware ethernet 00:C0:4F:A9:89:E3;
fixed-address 172.16.122.6;
filename /tftpboot/lts/vmlinuz-2.4.26-ltsp-3;
}
#cat /etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback
# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
script grep
map eth0
# The primary network interface
iface eth0 inet static
address 172.16.122.10
netmask 255.255.0.0
network 172.16.0.0
broadcast 172.16.255.255
gateway 172.16.0.1
dns-nameservers 172.16.0.1
#cat /etc/default/dhcp3-server
INTERFACES=eth0
#cat /etc/default/portmap
OPTIONS=
--
DenisG
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP don't start on 172.16.XX.YY network
Denis,
Look and see if you have a /etc/ltsp/dhcpd.conf file.
That is used by Ubuntu's implementation of LTSP.
Jim McQuillan
[EMAIL PROTECTED]
DenisG wrote:
Hi all
I'm trying to configure a LTSP server (Ubuntu 5.10) on a 172.16.XX.YY
network, but dhcpd refuses to start. Here's my config, I don't
understand what's wrong.
#cat /var/log/syslog
...
Dec 9 13:35:54 ltsp dhcpd: No subnet declaration for eth0
(172.16.122.10).
Dec 9 13:35:54 ltsp dhcpd: ** Ignoring requests on eth0. If this is
not what
Dec 9 13:35:54 ltsp dhcpd:you want, please write a subnet
declaration
Dec 9 13:35:54 ltsp dhcpd:in your dhcpd.conf file for the network
segment
Dec 9 13:35:54 ltsp dhcpd:to which interface eth0 is attached. **
Dec 9 13:35:54 ltsp dhcpd:
Dec 9 13:35:54 ltsp dhcpd:
Dec 9 13:35:54 ltsp dhcpd: Not configured to listen on any interfaces!
#ifconfig
eth0 Link encap:Ethernet HWaddr 00:12:3F:A2:D6:D3
inet addr:172.16.122.10 Bcast:172.16.255.255 Mask:255.255.0.0
inet6 addr: fe80::212:3fff:fea2:d6d3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6344 errors:0 dropped:0 overruns:0 frame:0
TX packets:1257 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1619811 (1.5 MiB) TX bytes:211002 (206.0 KiB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:78 errors:0 dropped:0 overruns:0 frame:0
TX packets:78 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6192 (6.0 KiB) TX bytes:6192 (6.0 KiB)
#cat /etc/dhcp3-server/dhcpd.conf
ddns-update-stylenone;
default-lease-time 21600;
max-lease-time 21600;
option subnet-mask 255.255.0.0;
option broadcast-address 172.16.255.255;
option routers 172.16.122.10;
option domain-name-servers 172.16.122.10;
option domain-name ltsp; # --Fix this domain name
option root-path 172.16.122.10:/opt/ltsp/i386;
option option-128 code 128 = string;
option option-129 code 129 = text;
subnet 172.16.0.0 netmask 255.255.0.0 {
use-host-decl-names on;
option log-servers 172.16.122.10;
}
host cdi5 {
hardware ethernet 00:C0:4F:A9:89:E3;
fixed-address 172.16.122.6;
filename /tftpboot/lts/vmlinuz-2.4.26-ltsp-3;
}
#cat /etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback
# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
script grep
map eth0
# The primary network interface
iface eth0 inet static
address 172.16.122.10
netmask 255.255.0.0
network 172.16.0.0
broadcast 172.16.255.255
gateway 172.16.0.1
dns-nameservers 172.16.0.1
#cat /etc/default/dhcp3-server
INTERFACES=eth0
#cat /etc/default/portmap
OPTIONS=
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP problem since NIC change on server
Dennis, You should be able to shut off the on-board NIC in the BIOS setup on the server. That should cause the system to recognize the new PCI card as eth0. Otherwise you can use something like webmin to configure the DHCP server to use eth1. Todd --- DenisG [EMAIL PROTECTED] wrote: Hi list I changed the network card on my LTSP server, and since that the client can't get an IP at boot, displaying Searching for server (DHCP)No IP address .No IP address .No IP address The old net card is still here (but not configured) as eth0, the new is eth1 with the same IP than before and works fine (I can surf, ping others...). I can't remove the old one because it is integrated on the motherboard. What's hapening? How can I tell DHCP to use eth1 now (if it is the problem...) Thanks DenisG --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP problem since NIC change on server
Denis, Did you change your DHCP server settings to listen on eth1? Pete Billson -- http://www.elbnet.com ELB Internet Service, Inc. Web Design, Computer Consulting, Internet Hosting DenisG wrote: Hi list I changed the network card on my LTSP server, and since that the client can't get an IP at boot, displaying Searching for server (DHCP)No IP address .No IP address .No IP address The old net card is still here (but not configured) as eth0, the new is eth1 with the same IP than before and works fine (I can surf, ping others...). I can't remove the old one because it is integrated on the motherboard. What's hapening? How can I tell DHCP to use eth1 now (if it is the problem...) Thanks DenisG --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP problem since NIC change on server
Denis, It depends on the distro. For Redhat, it's in /etc/sysconfig/dhcp Jim McQuillan [EMAIL PROTECTED] On Tue, 1 Nov 2005, DenisG wrote: Hi list I changed the network card on my LTSP server, and since that the client can't get an IP at boot, displaying Searching for server (DHCP)No IP address .No IP address .No IP address The old net card is still here (but not configured) as eth0, the new is eth1 with the same IP than before and works fine (I can surf, ping others...). I can't remove the old one because it is integrated on the motherboard. What's hapening? How can I tell DHCP to use eth1 now (if it is the problem...) Thanks DenisG --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP problem since NIC change on server
Denis, Did you change your DHCP server settings to listen on eth1? Pete Billson Thanks for your reply (and thanks to Todd too) That's exactly what I want to do, but I don't find where to do this! I use dhcp3-server on Ubuntu. There's nothing about it in dhcpd.conf. Not sure where Ubuntu changes this but on Rh it's in /etc/sysconfig/dhcpd DHCPDARGS=eth1 DHCPDARGS are used in the init.d/dhcpd start up file. Or you could just add the parameter eth1 in the dhcpd init file. Hope it helps. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP problem since NIC change on server
YEEES !! Thanks Jim, that was the information I was looking for, and it worked. I thought everything was in dhcpd.conf. I learnt something today again ;) Thanks to Todd and Peter too. DenisG Jim McQuillan a écrit : Denis, Ah, now we have enough information to really help you. On Ubuntu, with dhcp3, you need to edit the /etc/default/dhcp3-server file, and set: INTERFACES=eth1 Then, restart dhcp3-server Jim McQuillan [EMAIL PROTECTED] On Tue, 1 Nov 2005, DenisG wrote: Peter Billson a écrit : Denis, Did you change your DHCP server settings to listen on eth1? Pete Billson Thanks for your reply (and thanks to Todd too) That's exactly what I want to do, but I don't find where to do this! I use dhcp3-server on Ubuntu. There's nothing about it in dhcpd.conf. DenisG --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP problem since NIC change on server
Peter Billson a écrit : Denis, Did you change your DHCP server settings to listen on eth1? Pete Billson Thanks for your reply (and thanks to Todd too) That's exactly what I want to do, but I don't find where to do this! I use dhcp3-server on Ubuntu. There's nothing about it in dhcpd.conf. DenisG --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP problem since NIC change on server
Denis, Ah, now we have enough information to really help you. On Ubuntu, with dhcp3, you need to edit the /etc/default/dhcp3-server file, and set: INTERFACES=eth1 Then, restart dhcp3-server Jim McQuillan [EMAIL PROTECTED] On Tue, 1 Nov 2005, DenisG wrote: Peter Billson a écrit : Denis, Did you change your DHCP server settings to listen on eth1? Pete Billson Thanks for your reply (and thanks to Todd too) That's exactly what I want to do, but I don't find where to do this! I use dhcp3-server on Ubuntu. There's nothing about it in dhcpd.conf. DenisG --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP problem since NIC change on server
Denis, I don't use Ubuntu but (since it is Debian-based) in Debian the setting is in a file under /etc/defaults - file name is something like dhcp or dhcp3. You can also look in the /etc/init.d/dhcp* start up script. Pete Billson -- http://www.elbnet.com ELB Internet Service, Inc. Web Design, Computer Consulting, Internet Hosting DenisG wrote: Peter Billson a écrit : Denis, Did you change your DHCP server settings to listen on eth1? Pete Billson Thanks for your reply (and thanks to Todd too) That's exactly what I want to do, but I don't find where to do this! I use dhcp3-server on Ubuntu. There's nothing about it in dhcpd.conf. DenisG --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP problem with VLAN
Hi, other reasons lead me to change distro from Ubuntu to Gentoo... and I must say now the lab really rocks. Everything is up and running without a pain. The dhcp requests came on the eth0, I've successfully setup an eth0.1 for the vlan linked to the gateway and we're going to live happily ever after ;-) Enrico ps just for the record, I've not used the Gentoo LTSP ebuild instead I've downloaded it with the LTSP tool as Jim McQuillan suggested on IRC -- The only thing necessary for the triumph of evil is for good men to do nothing Edmund Burke --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] Dhcp probs
Hi Jim,
Would the following imply that /etc/dhcpd.conf should include
'192.168.0.2' rather 192.168.0.1' in the 'next-server- entry ?
Adam Bogacki,
[EMAIL PROTECTED]
ep 21 20:45:02 tux CRON[9489]: (pam_unix) session closed for user root
Sep 21 20:45:45 tux dhcpd: DHCPDISCOVER from 00:0b:2b:03:d2:57 via eth1
Sep 21 20:45:45 tux dhcpd: DHCPOFFER on 192.168.0.2 to
00:0b:2b:03:d2:57 via eth1
Sep 21 20:48:24 tux dhcpd: DHCPDISCOVER from 00:0b:2b:03:d2:57 via eth1
Sep 21 20:48:24 tux dhcpd: DHCPOFFER on 192.168.0.2 to
00:0b:2b:03:d2:57 via eth1
Current /etc/dhcpd.conf
option domain-name-servers 203.96.152.4, 203.96.152.12;
next-server 192.168.0.1;
option routers 192.168.0.1;
#next-server 192.168.0.1;
option subnet-mask 255.255.255.0;
default-lease-time 21600;
max-lease-time 21600;
#next-server 192.168.0.1;
option root-path 192.168.0.1:/opt/ltsp/i386;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
option log-servers 192.168.0.1;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.3 192.168.0.10;
}
Anyone who believes that exponential growth can go on /forever/ in a
finite world is either a madman or an economist. --- Kenneth E.
Boulding
0x4E553910.asc
Description: application/pgp-keys
[Ltsp-discuss] DHCP problem with VLAN
hi,
I've finally figured out how to configure the vlan network with my
LTSP lab... right now the server using eth0.1 can browse the internet.
So I've changed the clients network to the vlan's one (from
192.168.1.0 to 192.168.57.0), and also the dhcp config's ip.
But DHCP is no longer working.
When the client boot via the PXE enabled nic, it starts looking for
the DHCP server but nothing happen!
On the server I've got the following interfaces:
eth0 Link encap:Ethernet HWaddr 00:04:75:99:FA:A4
inet6 addr: fe80::204:75ff:fe99:faa4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3779 errors:1 dropped:0 overruns:1 frame:1
TX packets:1017 errors:0 dropped:0 overruns:0 carrier:0
collisions:1 txqueuelen:1000
RX bytes:823318 (804.0 KiB) TX bytes:156041 (152.3 KiB)
Interrupt:201 Base address:0xcc00
eth0.1Link encap:Ethernet HWaddr 00:04:75:99:FA:A4
inet addr:192.168.57.150 Bcast:192.168.57.255 Mask:255.255.255.0
inet6 addr: fe80::204:75ff:fe99:faa4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1418 errors:0 dropped:0 overruns:0 frame:0
TX packets:1012 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:611451 (597.1 KiB) TX bytes:155425 (151.7 KiB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:47033 errors:0 dropped:0 overruns:0 frame:0
TX packets:47033 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7202174 (6.8 MiB) TX bytes:7202174 (6.8 MiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth0.1 is the VLAN where I'm connected.
so I've setted up /etc/default/dhcp with
INTERFACES=eth0.1
and you'll find the complete DHCP config file at the end of the mail.
the server's log syslog and messages doesn't show DHCP request
the file was working so I assume it's something about my last vlan changes
I've restarted the server's dhcp after the changes and no warning has appeared
someone has suggestions?
Thanks,
Enrico
route -n
---
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
192.168.57.00.0.0.0 255.255.255.0 U 0 00 eth0.1
0.0.0.0 192.168.57.252 0.0.0.0 UG0 00 eth0.1
dhcpd.conf
default-lease-time 21600;
max-lease-time 21600;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.57.255;
option routers 192.168.57.150;
option domain-name-servers 192.168.57.150;
option domain-name ltsp; # --Fix this domain name
option root-path 192.168.57.150:/opt/ltsp/i386;
subnet 192.168.57.0 netmask 255.255.255.0 {
use-host-decl-names on;
option log-servers 192.168.57.150;
host ws001 {
hardware ethernet00:0a:5e:55:5e:33; #00:04:75:99:fb:61;
fixed-address192.168.57.151;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
#/tftpboot/lts/vmlinuz-2.4.26-ltsp-2;
}
host ws002 {
hardware ethernet00:04:75:99:f8:c4;
fixed-address192.168.57.152;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws003 {
hardware ethernet00:04:75:99:fb:27;
fixed-address192.168.57.153;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws004 {
hardware ethernet00:04:75:99:fb:0b;
fixed-address192.168.57.154;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws005 {
hardware ethernet00:01:02:b6:af:45;
fixed-address192.168.57.155;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws006 {
hardware ethernet00:04:75:99:f8:46;
fixed-address192.168.57.156;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws007 {
hardware ethernet00:04:75:99:fa:d7;
fixed-address192.168.57.157;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws008 {
hardware ethernet00:04:75:99:f8:df;
fixed-address192.168.57.158;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws009 {
hardware ethernet00:04:75:99:fa:41;
fixed-address
Re: [Ltsp-discuss] DHCP problem with VLAN
try:
INTERFACES=eth0
How did you setup the VLANs? Are they really VLANs or just alias ip adrresses?
Regards,
Umberto
On 9/15/05, Enrico Teotti [EMAIL PROTECTED] wrote:
hi,
I've finally figured out how to configure the vlan network with my
LTSP lab... right now the server using eth0.1 can browse the internet.
So I've changed the clients network to the vlan's one (from
192.168.1.0 to 192.168.57.0), and also the dhcp config's ip.
But DHCP is no longer working.
When the client boot via the PXE enabled nic, it starts looking for
the DHCP server but nothing happen!
On the server I've got the following interfaces:
eth0 Link encap:Ethernet HWaddr 00:04:75:99:FA:A4
inet6 addr: fe80::204:75ff:fe99:faa4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3779 errors:1 dropped:0 overruns:1 frame:1
TX packets:1017 errors:0 dropped:0 overruns:0 carrier:0
collisions:1 txqueuelen:1000
RX bytes:823318 (804.0 KiB) TX bytes:156041 (152.3 KiB)
Interrupt:201 Base address:0xcc00
eth0.1Link encap:Ethernet HWaddr 00:04:75:99:FA:A4
inet addr:192.168.57.150 Bcast:192.168.57.255 Mask:255.255.255.0
inet6 addr: fe80::204:75ff:fe99:faa4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1418 errors:0 dropped:0 overruns:0 frame:0
TX packets:1012 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:611451 (597.1 KiB) TX bytes:155425 (151.7 KiB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:47033 errors:0 dropped:0 overruns:0 frame:0
TX packets:47033 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7202174 (6.8 MiB) TX bytes:7202174 (6.8 MiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth0.1 is the VLAN where I'm connected.
so I've setted up /etc/default/dhcp with
INTERFACES=eth0.1
and you'll find the complete DHCP config file at the end of the mail.
the server's log syslog and messages doesn't show DHCP request
the file was working so I assume it's something about my last vlan changes
I've restarted the server's dhcp after the changes and no warning has appeared
someone has suggestions?
Thanks,
Enrico
route -n
---
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
192.168.57.00.0.0.0 255.255.255.0 U 0 00 eth0.1
0.0.0.0 192.168.57.252 0.0.0.0 UG0 00 eth0.1
dhcpd.conf
default-lease-time 21600;
max-lease-time 21600;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.57.255;
option routers 192.168.57.150;
option domain-name-servers 192.168.57.150;
option domain-name ltsp; # --Fix this domain name
option root-path 192.168.57.150:/opt/ltsp/i386;
subnet 192.168.57.0 netmask 255.255.255.0 {
use-host-decl-names on;
option log-servers 192.168.57.150;
host ws001 {
hardware ethernet00:0a:5e:55:5e:33; #00:04:75:99:fb:61;
fixed-address192.168.57.151;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
#/tftpboot/lts/vmlinuz-2.4.26-ltsp-2;
}
host ws002 {
hardware ethernet00:04:75:99:f8:c4;
fixed-address192.168.57.152;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws003 {
hardware ethernet00:04:75:99:fb:27;
fixed-address192.168.57.153;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws004 {
hardware ethernet00:04:75:99:fb:0b;
fixed-address192.168.57.154;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws005 {
hardware ethernet00:01:02:b6:af:45;
fixed-address192.168.57.155;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws006 {
hardware ethernet00:04:75:99:f8:46;
fixed-address192.168.57.156;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws007 {
hardware ethernet00:04:75:99:fa:d7;
fixed-address192.168.57.157;
filename
Re: [Ltsp-discuss] DHCP problem with VLAN
Encico,
Is there any chance you've upgraded your dhcp server along the way, to
3.0.3? In which case, you'd be getting bit by this issue:
http://wiki.ltsp.org/twiki/bin/view/Ltsp/DhcpdSiaddr
Jim McQuillan
[EMAIL PROTECTED]
On Thu, 15 Sep 2005, Enrico Teotti wrote:
hi,
I've finally figured out how to configure the vlan network with my
LTSP lab... right now the server using eth0.1 can browse the internet.
So I've changed the clients network to the vlan's one (from
192.168.1.0 to 192.168.57.0), and also the dhcp config's ip.
But DHCP is no longer working.
When the client boot via the PXE enabled nic, it starts looking for
the DHCP server but nothing happen!
On the server I've got the following interfaces:
eth0 Link encap:Ethernet HWaddr 00:04:75:99:FA:A4
inet6 addr: fe80::204:75ff:fe99:faa4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3779 errors:1 dropped:0 overruns:1 frame:1
TX packets:1017 errors:0 dropped:0 overruns:0 carrier:0
collisions:1 txqueuelen:1000
RX bytes:823318 (804.0 KiB) TX bytes:156041 (152.3 KiB)
Interrupt:201 Base address:0xcc00
eth0.1Link encap:Ethernet HWaddr 00:04:75:99:FA:A4
inet addr:192.168.57.150 Bcast:192.168.57.255 Mask:255.255.255.0
inet6 addr: fe80::204:75ff:fe99:faa4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1418 errors:0 dropped:0 overruns:0 frame:0
TX packets:1012 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:611451 (597.1 KiB) TX bytes:155425 (151.7 KiB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:47033 errors:0 dropped:0 overruns:0 frame:0
TX packets:47033 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7202174 (6.8 MiB) TX bytes:7202174 (6.8 MiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth0.1 is the VLAN where I'm connected.
so I've setted up /etc/default/dhcp with
INTERFACES=eth0.1
and you'll find the complete DHCP config file at the end of the mail.
the server's log syslog and messages doesn't show DHCP request
the file was working so I assume it's something about my last vlan changes
I've restarted the server's dhcp after the changes and no warning has appeared
someone has suggestions?
Thanks,
Enrico
route -n
---
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
192.168.57.00.0.0.0 255.255.255.0 U 0 00 eth0.1
0.0.0.0 192.168.57.252 0.0.0.0 UG0 00 eth0.1
dhcpd.conf
default-lease-time 21600;
max-lease-time 21600;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.57.255;
option routers 192.168.57.150;
option domain-name-servers 192.168.57.150;
option domain-name ltsp; # --Fix this domain name
option root-path 192.168.57.150:/opt/ltsp/i386;
subnet 192.168.57.0 netmask 255.255.255.0 {
use-host-decl-names on;
option log-servers 192.168.57.150;
host ws001 {
hardware ethernet00:0a:5e:55:5e:33; #00:04:75:99:fb:61;
fixed-address192.168.57.151;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
#/tftpboot/lts/vmlinuz-2.4.26-ltsp-2;
}
host ws002 {
hardware ethernet00:04:75:99:f8:c4;
fixed-address192.168.57.152;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws003 {
hardware ethernet00:04:75:99:fb:27;
fixed-address192.168.57.153;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws004 {
hardware ethernet00:04:75:99:fb:0b;
fixed-address192.168.57.154;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws005 {
hardware ethernet00:01:02:b6:af:45;
fixed-address192.168.57.155;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws006 {
hardware ethernet00:04:75:99:f8:46;
fixed-address192.168.57.156;
filename /tftpboot/lts/2.4.26-ltsp-2/pxelinux.0;
}
host ws007 {
hardware ethernet00:04:75:99:fa:d7;
fixed-address
Re: [Ltsp-discuss] DHCP problem with VLAN
INTERFACES=eth0 at the beginning it was so, but after restarting dhcp it complained about that... I'm not a DHCP expert but I assume it complain the ip of eth0 (0.0.0.0) was different from the dhcpd.conf subnets and ips ... How did you setup the VLANs? Are they really VLANs or just alias ip adrresses? I've setted eth0 to 0.0.0.0 then I've added eth0 to vlan1 vconfig add eth0 1 then I've configured the eth0.1 ip (192.168.57.150) setting the default gw to the proxy's IP this way I can ping the proxy and get internet access Is there any chance you've upgraded your dhcp server along the way, to 3.0.3? In which case, you'd be getting bit by this issue: http://wiki.ltsp.org/twiki/bin/view/Ltsp/DhcpdSiaddr next week I'll be back at the school and I'll check the dhcp version, but I'm almost sure it's not changed. I've just installed on the Ubuntu system a Sarge vconfig package to enable the vlan tools. thanks for the tips guys, I'll let you know! Enrico -- The only thing necessary for the triumph of evil is for good men to do nothing Edmund Burke --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] DHCP problem with VLAN
Couldn't you use alias ip addresses instead of using vlans? I'll check but I think I can't cause they are using vlan lans on the school network. And the proxy is on vlan1 so I must be on vlan1 to ping it, it's not enought to use the same network mask. -- The only thing necessary for the triumph of evil is for good men to do nothing Edmund Burke --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] Dhcp problems
Thanks Jim, I have copied output from tcpdump and netstat below - at least the cable and connections are working, together with the original error message. (1) tcpdump Tux:/var/log# tcpdump -i eth1 port 67 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes 20:12:18.839441 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:12:19.313829 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:12:29.383419 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:12:29.384031 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:12:49.321069 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:12:49.321692 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:13:29.525990 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:13:29.526630 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:14:48.837241 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:14:48.837908 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:17:27.569570 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:17:27.570080 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 (2) netstat Tux:/home/adam# netstat -anp | grep :67 udp0 0 0.0.0.0:67 0.0.0.0:* 3 669/dhcpd3 Tux:/home/adam# (3) Error message (transcribed, possibly with human error) Loading ROM image ROM segment 0x length 0x reloc 0x0002 Etherboot 5.2.5 (GPL) http://etherboot.org Tagged ELF for [RTL8139] Relocating text from: [00013a50,0002454) to [05cef510,05f0) Boot from (N)etwork or (Q)uit ? Probing pci nic ... [rtl8139] - ioaddr 0x1400, addr 00:0B:2B:03:D2:57 100Mbps full-duplex Searching for server (DHCP) ... I'd welcome any constructive suggestions .. the natives are restless. Adam Bogacki, [EMAIL PROTECTED] On Thu, Sep 08, 2005 at 09:43:19AM -0400 or thereabouts, Jim McQuillan wrote: Adam, I've missed the initial conversation of what's going on. If your client is saying 'Seeking server (DHCPD)' (btw, I think you need to reread what it says on the screen, because although I've seen something similar, I don't think that's exactly what it says). Anyway, if it says something like that, then it sounds like the client can't find the DHCP server. Any monkeying around with the 'next-server' parameter in dhcpd.conf won't have any effect on this, cuz the client hasn't even found the dhcp server. next-server is for the next step AFTER the dhcp reply. Watch in your log files. Depends on the distro, but look in /var/log/daemon.log, or /var/log/messages or /var/log/syslog for info, as the client is searching for the dhcp server. Also, try using tcpdump to watch the packets, and see if you are seeing any DHCP packets. The syntax would be: tcpdump -i eth1 port 67 or 68 Adjust your 'eth1' as appropriate for your server. Once tcpdump is running, then turn on the client, and see what you get. If you don't see anything, then your clients dhcp requests aren't getting to the server. Check cables and switches. If you do see DHCP requests, then the packets are getting to the server, so now you need to figure out if the server is actually paying attention to them. Is dhcpd actually listening? netstat -anp | grep :67 Should tell you. If you get no output from that command, then you need to figure out why dhcpd isn't listening. Hope that helps, Jim McQuillan [EMAIL PROTECTED] On Thu, 8 Sep 2005, Adam Bogacki wrote: On Tue, Sep 06, 2005 at 06:03:41PM +0200 or thereabouts, Dave Cotton wrote: On Tue, 2005-09-06 at 21:01 +1200, Adam Bogacki wrote: On Tue, Sep 06, 2005 at 08:47:23AM +0200 or thereabouts, Dave Cotton wrote: On Tue, 2005-09-06 at 18:40 +1200, Adam Bogacki wrote: It seems I have the same problem but having looked at 'ltspcfg' I can find no 'next-server' entry. Could you be more specific where it may be found ? It isn't in ltspcfg (yet, Jim? :)) just edit dhcpd.conf directly. I now have:- next-server [ip-of-original-server]; Seems also to give a speed boost to finding the server. -- Dave Cotton [EMAIL PROTECTED] Thanks .. but it still hangs at Searching for server [DHCPD] ... Is this what you had in mind ? Adam. [1] dhcpd.conf option domain-name-servers 203.96.152.4, 203.96.152.12;
Re: [Ltsp-discuss] Dhcp problems
Am Dienstag, den 13.09.2005, 20:39 +1200 schrieb Adam Bogacki: Thanks Jim, I have copied output from tcpdump and netstat below - at least the cable and connections are working, together with the original error message. (1) tcpdump Tux:/var/log# tcpdump -i eth1 port 67 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes 20:12:18.839441 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:12:19.313829 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:12:29.383419 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:12:29.384031 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:12:49.321069 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:12:49.321692 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:13:29.525990 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:13:29.526630 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:14:48.837241 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:14:48.837908 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:17:27.569570 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:17:27.570080 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 (2) netstat Tux:/home/adam# netstat -anp | grep :67 udp0 0 0.0.0.0:67 0.0.0.0:* 3 669/dhcpd3 Tux:/home/adam# [1] dhcpd.conf option domain-name-servers 203.96.152.4, 203.96.152.12; option routers 192.168.0.1; option subnet-mask 255.255.255.0; default-lease-time 21600; max-lease-time 21600; next-server 203.79.110.81; Set next-server to 192.168.0.1 (or did you do that already?), and make sure that a filename is set also. If in doubt, please post your entire dhcpd.conf. Anselm --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] Dhcp problems
Adam, What version of dhcpd are you using? If it's 3.0.3, there's a problem. Fortunately, the fix is easy. Take a look at this article: http://wiki.ltsp.org/twiki/bin/view/Ltsp/DHCP Jim McQuillan [EMAIL PROTECTED] On Tue, 13 Sep 2005, Adam Bogacki wrote: Thanks Jim, I have copied output from tcpdump and netstat below - at least the cable and connections are working, together with the original error message. (1) tcpdump Tux:/var/log# tcpdump -i eth1 port 67 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes 20:12:18.839441 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:12:19.313829 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:12:29.383419 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:12:29.384031 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:12:49.321069 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:12:49.321692 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:13:29.525990 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:13:29.526630 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:14:48.837241 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:14:48.837908 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:17:27.569570 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:17:27.570080 IP 192.168.0.1.bootps 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 (2) netstat Tux:/home/adam# netstat -anp | grep :67 udp0 0 0.0.0.0:67 0.0.0.0:* 3 669/dhcpd3 Tux:/home/adam# (3) Error message (transcribed, possibly with human error) Loading ROM image ROM segment 0x length 0x reloc 0x0002 Etherboot 5.2.5 (GPL) http://etherboot.org Tagged ELF for [RTL8139] Relocating text from: [00013a50,0002454) to [05cef510,05f0) Boot from (N)etwork or (Q)uit ? Probing pci nic ... [rtl8139] - ioaddr 0x1400, addr 00:0B:2B:03:D2:57 100Mbps full-duplex Searching for server (DHCP) ... I'd welcome any constructive suggestions .. the natives are restless. Adam Bogacki, [EMAIL PROTECTED] On Thu, Sep 08, 2005 at 09:43:19AM -0400 or thereabouts, Jim McQuillan wrote: Adam, I've missed the initial conversation of what's going on. If your client is saying 'Seeking server (DHCPD)' (btw, I think you need to reread what it says on the screen, because although I've seen something similar, I don't think that's exactly what it says). Anyway, if it says something like that, then it sounds like the client can't find the DHCP server. Any monkeying around with the 'next-server' parameter in dhcpd.conf won't have any effect on this, cuz the client hasn't even found the dhcp server. next-server is for the next step AFTER the dhcp reply. Watch in your log files. Depends on the distro, but look in /var/log/daemon.log, or /var/log/messages or /var/log/syslog for info, as the client is searching for the dhcp server. Also, try using tcpdump to watch the packets, and see if you are seeing any DHCP packets. The syntax would be: tcpdump -i eth1 port 67 or 68 Adjust your 'eth1' as appropriate for your server. Once tcpdump is running, then turn on the client, and see what you get. If you don't see anything, then your clients dhcp requests aren't getting to the server. Check cables and switches. If you do see DHCP requests, then the packets are getting to the server, so now you need to figure out if the server is actually paying attention to them. Is dhcpd actually listening? netstat -anp | grep :67 Should tell you. If you get no output from that command, then you need to figure out why dhcpd isn't listening. Hope that helps, Jim McQuillan [EMAIL PROTECTED] On Thu, 8 Sep 2005, Adam Bogacki wrote: On Tue, Sep 06, 2005 at 06:03:41PM +0200 or thereabouts, Dave Cotton wrote: On Tue, 2005-09-06 at 21:01 +1200, Adam Bogacki wrote: On Tue, Sep 06, 2005 at 08:47:23AM +0200 or thereabouts, Dave Cotton wrote: On Tue, 2005-09-06 at 18:40 +1200, Adam Bogacki wrote: It seems I have the same problem but having looked at 'ltspcfg' I can find no 'next-server' entry. Could you be more specific where it may be found ? It isn't in ltspcfg (yet, Jim? :)) just edit dhcpd.conf directly. I now have:-
Re: [Ltsp-discuss] Dhcp problems
On Tue, Sep 06, 2005 at 06:03:41PM +0200 or thereabouts, Dave Cotton wrote: On Tue, 2005-09-06 at 21:01 +1200, Adam Bogacki wrote: On Tue, Sep 06, 2005 at 08:47:23AM +0200 or thereabouts, Dave Cotton wrote: On Tue, 2005-09-06 at 18:40 +1200, Adam Bogacki wrote: It seems I have the same problem but having looked at 'ltspcfg' I can find no 'next-server' entry. Could you be more specific where it may be found ? It isn't in ltspcfg (yet, Jim? :)) just edit dhcpd.conf directly. I now have:- next-server [ip-of-original-server]; Seems also to give a speed boost to finding the server. -- Dave Cotton [EMAIL PROTECTED] Thanks .. but it still hangs at Searching for server [DHCPD] ... Is this what you had in mind ? Adam. [1] dhcpd.conf option domain-name-servers 203.96.152.4, 203.96.152.12; option routers 192.168.0.1; option subnet-mask 255.255.255.0; default-lease-time 21600; max-lease-time 21600; next-server 203.79.110.81; No, surely this is your external address. If this is running on 192.168.0.1, strange as it may seem, 192.168.0.1 is the next-server address. Hmm .. thanks, but it still hangs at 'seeking server (DHCPD)'. What else am I missing here ? Adam Bogacki. Anyone who believes that exponential growth can go on forever in a finite world is either a madman or an economist. -- Kenneth E. Boulding -- Dave Cotton [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: [Ltsp-discuss] Dhcp problems
Adam, I've missed the initial conversation of what's going on. If your client is saying 'Seeking server (DHCPD)' (btw, I think you need to reread what it says on the screen, because although I've seen something similar, I don't think that's exactly what it says). Anyway, if it says something like that, then it sounds like the client can't find the DHCP server. Any monkeying around with the 'next-server' parameter in dhcpd.conf won't have any effect on this, cuz the client hasn't even found the dhcp server. next-server is for the next step AFTER the dhcp reply. Watch in your log files. Depends on the distro, but look in /var/log/daemon.log, or /var/log/messages or /var/log/syslog for info, as the client is searching for the dhcp server. Also, try using tcpdump to watch the packets, and see if you are seeing any DHCP packets. The syntax would be: tcpdump -i eth1 port 67 or 68 Adjust your 'eth1' as appropriate for your server. Once tcpdump is running, then turn on the client, and see what you get. If you don't see anything, then your clients dhcp requests aren't getting to the server. Check cables and switches. If you do see DHCP requests, then the packets are getting to the server, so now you need to figure out if the server is actually paying attention to them. Is dhcpd actually listening? netstat -anp | grep :67 Should tell you. If you get no output from that command, then you need to figure out why dhcpd isn't listening. Hope that helps, Jim McQuillan [EMAIL PROTECTED] On Thu, 8 Sep 2005, Adam Bogacki wrote: On Tue, Sep 06, 2005 at 06:03:41PM +0200 or thereabouts, Dave Cotton wrote: On Tue, 2005-09-06 at 21:01 +1200, Adam Bogacki wrote: On Tue, Sep 06, 2005 at 08:47:23AM +0200 or thereabouts, Dave Cotton wrote: On Tue, 2005-09-06 at 18:40 +1200, Adam Bogacki wrote: It seems I have the same problem but having looked at 'ltspcfg' I can find no 'next-server' entry. Could you be more specific where it may be found ? It isn't in ltspcfg (yet, Jim? :)) just edit dhcpd.conf directly. I now have:- next-server [ip-of-original-server]; Seems also to give a speed boost to finding the server. -- Dave Cotton [EMAIL PROTECTED] Thanks .. but it still hangs at Searching for server [DHCPD] ... Is this what you had in mind ? Adam. [1] dhcpd.conf option domain-name-servers 203.96.152.4, 203.96.152.12; option routers 192.168.0.1; option subnet-mask 255.255.255.0; default-lease-time 21600; max-lease-time 21600; next-server 203.79.110.81; No, surely this is your external address. If this is running on 192.168.0.1, strange as it may seem, 192.168.0.1 is the next-server address. Hmm .. thanks, but it still hangs at 'seeking server (DHCPD)'. What else am I missing here ? Adam Bogacki. Anyone who believes that exponential growth can go on forever in a finite world is either a madman or an economist. -- Kenneth E. Boulding -- Dave Cotton [EMAIL PROTECTED] --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] DHCP received no IP address
I have installed ltsp on debian. Everything is configured, I created a floppy boot disk using http://www.rom-o-matic.net/ I have an eepro100 [0x8086,0x1032] network card. The card was detected when it boots from the floppy, however, when it searched for DHCP, it receives no IP Address. I checked the logfile on my DHCP server, I can see logs for DHCPDISCOVER and DHCPOFFER but why no IP address was received by workstation?
Re: [Ltsp-discuss] DHCP received no IP address
phabs, do you have a 'filename' entry in your dhcpd.conf file? etherboot will ignore offers that don't include a filename to download. Also, what version of dhcpd are you using? We've just recently been seeing problems with the new ISC dhcpd version 3.0.3. It doesn't set the boot-server IP address in the OFFER, requiring you to add a 'next-server' entry in your dhcpd.conf, to work around it. Jim McQuillan [EMAIL PROTECTED] On Mon, 5 Sep 2005, phabs wrote: I have installed ltsp on debian. Everything is configured, I created a floppy boot disk using http://www.rom-o-matic.net/ I have an eepro100 [0x8086,0x1032] network card. The card was detected when it boots from the floppy, however, when it searched for DHCP, it receives no IP Address. I checked the logfile on my DHCP server, I can see logs for DHCPDISCOVER and DHCPOFFER but why no IP address was received by workstation? --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
