Menu
▾
▴
devil-linux-discuss
|
From: Bobble H. <bob...@ho...> - 2006-03-21 16:19:01
|
I am using Devil-Linux 1.2.9-i586 and have configured it using the setup command as a basic two nic firewall. I am new to Linux so haven't modified any files manually. I have configured the Internet card to get an IP info from a DHCP server. I have configured the Local LAN card to act as a DHCP server for this subnet (192.168.1.254:255.255.255.0). The system boots and gets an IP address from the internet side but doesn't seem to give out IP addresses on the local LAN side. I have manually configured a client PC (WinXP) with a static IP address of 192.168.1.100:255.255.255.0 plus DNS server addressed and the router seems to work ok. However if I configure the client PC to get its IP address from the DHCP server then it fails to get an address when doing a ipconfig release and renew. Do I need to start the DHCP server and how can I check on the DHCP server status? You help in this matter is much apprieciated. Bobblehat. _________________________________________________________________ Are you using the latest version of MSN Messenger? Download MSN Messenger 7.5 today! http://messenger.msn.co.uk |
|
From: Chris H. <Chr...@ha...> - 2008-05-23 18:52:39
|
I am having problems with Devil Linux 1.2.14. I installed from devil-linux-1.2.14-i686-SMP-server.tar.bz2 download. I am not sure if it is a hardware problem or compatibility issue or just a simple setting I am missing. The only service I really need is DHCP for a small guest network and then SSH for management. I like the idea of using a small distro like this for this purpose but I am having problems getting it to work. If I boot up DevilLinux on the pc that as acting as a DHCP server and immediately have workstations power up they get a lease no problem. If DL is running for awhile and a workstation powers up or reboots they usually don't get a lease. The lease itself is for 10 days but the workstation will not have a valid address on the network if the DL pc is down. My /etc/dhcpd.conf reads as follows: authoritative; default-lease-time 864000; max-lease-time 864000; lease-file-name "/etc/dhcpd.leases"; get-lease-hostnames false; use-host-decl-names on; ddns-update-style none; option domain-name "guestdomain.com" option subnet-mask 255.255.255.0; subnet 192.168.0.0 netmask 255.255.255.0 { option domain-name-servers X.X.X.X; option routers Y.Y.Y.Y; option broadcast-address 192.168.0.255; range 192.168.0.100 192.168.0.1 } When I look for the lease file I see two in /etc/ dhcpd.leases and dhcpd.leases~ dhcpd.leases has -rw-r--r-- dhcpd.leases~ has -rwxrwxrwx I am running this on an older HP vectra. When I tried to install on a newer but still old HP e500 PC the install program couldn't find the module for the on board network card which it identified as an Intel 82801. Assuming I could find a driver can they be added to DL or am I better off buying a different nic in which case which one is the best to try for? Any help would be appreciated. Thanks in advance. -Chris. |
|
From: Dick M. <di...@fo...> - 2008-05-23 19:20:59
|
Chris HATCH wrote:
>
> If I boot up DevilLinux on the pc that as acting as a DHCP server and
> immediately have workstations power up they get a lease no problem. If
> DL is running for awhile and a workstation powers up or reboots they
> usually don't get a lease.
It's not obvious what's wrong but your range is misconfigured (or there's a typo
in your email):
> subnet 192.168.0.0 netmask 255.255.255.0 {
> option domain-name-servers X.X.X.X;
> option routers Y.Y.Y.Y;
> option broadcast-address 192.168.0.255;
> range 192.168.0.100 192.168.0.1
range [ dynamic-bootp ] low-address [ high-address];
It could also be there is another dhcp server appearing on the net and confusing
things. Does one of your workstations run dhcp perhaps?
The lease itself is for 10 days but the
> workstation will not have a valid address on the network if the DL pc is
> down.
If there is no dhcp server then what happens depends on the client. Some
clients allocate an address in the 169 range for example and some continue to
use the old address and some just don't ...
> When I look for the lease file I see two in /etc/ dhcpd.leases and
> dhcpd.leases~
> dhcpd.leases has -rw-r--r--
> dhcpd.leases~ has -rwxrwxrwx
I don't know why the permissions are different. What happens if you delete
dhcpd.leases~ ? It should get recreated.
Dick
|
|
From: Bruce S. <bw...@ar...> - 2006-03-21 16:34:24
|
> I am using Devil-Linux 1.2.9-i586 and have configured it using the setup > command as a basic two nic firewall. I am new to Linux so haven't modified > any files manually. > I have configured the Internet card to get an IP info from a DHCP server. > I have configured the Local LAN card to act as a DHCP server for this subnet > (192.168.1.254:255.255.255.0). > The system boots and gets an IP address from the internet side but doesn't > seem to give out IP addresses on the local LAN side. > I have manually configured a client PC (WinXP) with a static IP address of > 192.168.1.100:255.255.255.0 plus DNS server addressed and the router seems > to work ok. However if I configure the client PC to get its IP address from > the DHCP server then it fails to get an address when doing a ipconfig > release and renew. > Do I need to start the DHCP server and how can I check on the DHCP server > status? Under the network card setup for your local LAN, there is a setting that says "Act as a DHCP server for this subnet" (same screen where you set the IP address for that NIC). You need to turn this setting ON. (and save-config, and reboot). - BS |
|
From: Bobble H. <bob...@ho...> - 2006-03-21 19:19:25
|
>From: Bruce Smith <bw...@ar...> >Reply-To: dev...@li... >To: dev...@li... >Subject: Re: [Devil-Linux-discuss] DHCP problem >Date: Tue, 21 Mar 2006 11:34:13 -0500 > > > I am using Devil-Linux 1.2.9-i586 and have configured it using the setup > > command as a basic two nic firewall. I am new to Linux so haven't >modified > > any files manually. > > I have configured the Internet card to get an IP info from a DHCP >server. > > I have configured the Local LAN card to act as a DHCP server for this >subnet > > (192.168.1.254:255.255.255.0). > > The system boots and gets an IP address from the internet side but >doesn't > > seem to give out IP addresses on the local LAN side. > > I have manually configured a client PC (WinXP) with a static IP address >of > > 192.168.1.100:255.255.255.0 plus DNS server addressed and the router >seems > > to work ok. However if I configure the client PC to get its IP address >from > > the DHCP server then it fails to get an address when doing a ipconfig > > release and renew. > > Do I need to start the DHCP server and how can I check on the DHCP >server > > status? > >Under the network card setup for your local LAN, there is a setting that >says "Act as a DHCP server for this subnet" (same screen where you set >the IP address for that NIC). You need to turn this setting ON. (and >save-config, and reboot). > > - BS > > > > >------------------------------------------------------- >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=lnk&kid=110944&bid=241720&dat=121642 >_______________________________________________ >Devil-linux-discuss mailing list >Dev...@li... >https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss Thanks Bruce, but I did notice this setting and turned it on, saved and rebooted as you said. Any other suggestions. Is there anyway to get info the DHCP service? _________________________________________________________________ Are you using the latest version of MSN Messenger? Download MSN Messenger 7.5 today! http://join.msn.com/messenger/overview |
|
From: Bruce S. <bw...@ar...> - 2006-03-21 19:30:50
|
> >Under the network card setup for your local LAN, there is a setting that > >says "Act as a DHCP server for this subnet" (same screen where you set > >the IP address for that NIC). You need to turn this setting ON. (and > >save-config, and reboot). > > Thanks Bruce, but I did notice this setting and turned it on, saved and > rebooted as you said. Any other suggestions. Is there anyway to get info the > DHCP service? If it's not starting, you might have something mis-configured. It seems like the local IP defaults to a different subnet than the DHCP default range, which would cause the DHCP server NOT to start. (one is 192.168.0 and the other is 192.168.1?) I don't remember the details, but I'm pretty sure you have to tweak the defaults somewhere. I think you can start the DHCP server manually with the command: /etc/init.d/dhcpd start It still won't start until you fix whatever is preventing it from running, but it may provide useful error messages. If no errors are displayed, try this: sh -x /etc/init.d/dhcpd start - BS |
|
From: Bobble H. <bob...@ho...> - 2006-03-22 09:50:38
|
> > >Under the network card setup for your local LAN, there is a setting >that > > >says "Act as a DHCP server for this subnet" (same screen where you set > > >the IP address for that NIC). You need to turn this setting ON. (and > > >save-config, and reboot). > > > > Thanks Bruce, but I did notice this setting and turned it on, saved and > > rebooted as you said. Any other suggestions. Is there anyway to get info >the > > DHCP service? > >If it's not starting, you might have something mis-configured. > >It seems like the local IP defaults to a different subnet than the DHCP >default range, which would cause the DHCP server NOT to start. (one is >192.168.0 and the other is 192.168.1?) I don't remember the details, >but I'm pretty sure you have to tweak the defaults somewhere. > >I think you can start the DHCP server manually with the command: > > /etc/init.d/dhcpd start > >It still won't start until you fix whatever is preventing it from >running, but it may provide useful error messages. > >If no errors are displayed, try this: > > sh -x /etc/init.d/dhcpd start > > - BS > Thanks Bruce, it's obvious now, the default IP address for the Local LAN was 192.168.1.254 but the default address range for the DHCP server was 192.168.0.xx, different networks. I have changed the Local LANs IP to 192.168.0.254 and it is now working. Thanks for your help is it much appreciated. _________________________________________________________________ Are you using the latest version of MSN Messenger? Download MSN Messenger 7.5 today! http://join.msn.com/messenger/overview |
|
From: Bruce S. <bw...@ar...> - 2006-03-22 13:09:46
|
> Thanks Bruce, it's obvious now, the default IP address for the Local LAN was > 192.168.1.254 but the default address range for the DHCP server was > 192.168.0.xx, different networks. I have changed the Local LANs IP to > 192.168.0.254 and it is now working. > Thanks for your help is it much appreciated. This brings up a good point. We really should "fix" it so that the default values are in sync and work without these changes. Heiko: Are we still using CVS or did you switch us to subversion? (I just got back from a 2+ week vacation, and am still "out of it" :) - BS |
|
From: Bruce S. <bw...@ar...> - 2006-03-22 13:17:12
|
> Heiko: Are we still using CVS or did you switch us to subversion? Never mind, CVS seems to still work. It's "fixed" for future releases. - BS |
|
From: Heiko Z. <he...@zu...> - 2006-03-22 14:16:19
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Heiko: Are we still using CVS or did you switch us to subversion? > (I just got back from a 2+ week vacation, and am still "out of it" :) Still CVS as you saw. I don't think I have time to take care of this in the next couple weeks. - -- Regards Heiko Zuerker http://www.devil-linux.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iEYEARECAAYFAkQhXB4ACgkQUcytMSbs+YUefACeO2XEgBm5LJVQ2ZyUw5WfEahI kB0An0cWjZ0I+tY5c35k6x7wz0iHK98s =L1Ip -----END PGP SIGNATURE----- |
