Networking :: DHCP Lease Under SuSE Is Not Working., Limited At 10 Minutes?
Jun 22, 2011
I got a strange issue here: We are using ISC DHCP v4 which is default in Open SuSE 11.4. These two options 'default-lease-time' and 'max-lease-time' are set in all subnets, with values between 43200 (12 hours) to 518400 (144 hours). See partial dhcpd.conf below please.Now the lease time from Windows client's ipconfig output is only 10 minutes. Why? (dhcpd on servers restarted many times. ipconfig /release, ipconfig /renew on client run many times)
I am puzzled with trying to configure a linux (openSUSE) client to dhcp to eBox DHCP server. I am using dhclient to lease an IP address with dhclient eth0 -s 10.45.48.108 and get a response
openSUSE11232CL1 dhclient: DHCPDISCOVER on eth0 to 10.45.48.108 port 67 interval 4 openSUSE11232CL1 dhclient: DHCPOFFER from 10.45.48.108 openSUSE11232CL1 dhclient: DHCPREQUEST on eth0 to 10.45.48.108 port 67 openSUSE11232CL1 dhclient: send_packet: Network is unreachable openSUSE11232CL1 dhclient: send_packet: please consult README file regarding broadcast address.
The server reports eBox141 dhcpd: DHCPDISCOVER from 00:0c:29:3e:57:a3 (openSUSE11232CL1.domain.net) via eth0 eBox141 dhcpd: DHCPOFFER on 10.45.200.2 to 00:0c:29:3e:57:a3 (openSUSE11232CL1.domain.net) via eth0
I interpret this as the server receives the request and the client accepting it but the lease does not last long and the connection breaks. what this could be and why the connection breaks? Or my undestanding is totally wrong on how it works and should work? And BTW, where is that README file that's referenced in the message I receive on the client?
I have a home WiFi network that has been working fine for ages, which currently supports two Windows-based laptops and a WM5 smartphone. They all connect to the WiFi router (Linksys WRT54G) which in turn connects to the ADSL modem (Huawei MT882). The router is configured with a WEP key, the SSID is not being broadcast, and all MAC addresses must be whitelisted. I try to follow good wireless network security practice. I also have NAT running between the router and the modem.
Everything is working fine for the Windows clients, and now I am trying to add my Linux box to the mix. I am setting up an older HP Pavilion 510a desktop with Ubuntu v8.04LTS, using a Realtek RTL8185 WLAN card. The machine has an onboard RTL8139 LAN adaptor also, which works fine when I plug it in directly to an ethernet port on the wireless router. The WLAN, however, does not seem to be getting a DHCP packet, and keeps on autoconfiguring with a 169.254.x.x address. When I try giving it a static IP address it doesn't connect either.
As you can see from the screenshots below, the WLAN is working fine. I have it installed using the ndiswrapper and Windows drivers. I've been through the Comprehensive ndiswrapper troubleshooting guide but that did not resolve my problem.
I configured the network myself, and it works perfectly for my Windows machines. It is just my lack of experience with Linux which is preventing me from getting the wireless to work under Linux. I can get a HDCP packet in Linux when I am connected to the LAN using the RTL8139 adaptor, but not on the WLAN using the RTL8185 adaptor.
Is there any way to get an async notification (perhaps through something like a Linux message queue or Unix socket) when a DHCP client is either unable to renew its lease, or the address obtained changes from the previous value? I've got the ISC client and will dig into it to determine if it supports such a feature, but thought I'd ask here in parallel. (I'm trying to find out if there are any DHCP clients out there which already support this capability.)
If you're curious: We have an application where we're doing auto-registration of an IP camera to an external server. If the camera's dynamically assigned address changes, we need to restart the auto-reg state machine. I've seen implementations where a socket is opened and a SIOCGIFADDR ioctl used to fetch the IP addr, but I'd sure like to avoid polling like this if possible.
We have 20+ Redhat servers on our network and every so often our DHCP server goes down. When it comes back up we have to go around to all of our RedHat servers and restart networking manually. Other OS's (Ubuntu, Windows, etc..) will continually try to get a DHCP lease so that when our DHCP does come back up it requires no work from us for them to get back on the network. But it seems that Redhat only tries once and if it fails it never tries again. Have to go around to 20 different servers (some of them are at remote locations) is less then ideal when this happens. how we can get Redhat to continually try to get a DHCP lease like other OS's?
The system I am working on is a xdsl board running Linux kernel 2.6 and receiving dhcp address from a Microsoft XP PC. when looking through the dhclient.leases file I can see there's something wrong with renew time and stuff.strange calculation. as far as you know is this normal? You may find below the dhclient.lease file.
first: PXE flawless bind to dhcp address but put next binding state to free second: when installer calls init script to reinit ethernet driver (e1000 (vmware)) binding fails 11.2 opensuse fail to reinit dhcp with log entry "no free leases" third: when manual set network install works how to preserve dhcp lease on reinit of driver?
I have a Zotac Ionitx A-U. I can't get it to establish an internet connection with the wired ethernet within Ubuntu. The chip is detected, but trying to bring up the connection stalls out at trying to obtain a DHCP lease, like this:
DHCP DISCOVER ... DHCP DISCOVER ... No DHCPOFFERS received Specs: Ionitx A-U Ubuntu 10.04 x64 kernel 2.6.32-22 (also didn't work in 9.10)
I'm running an up-to-date Fedora 12 machine with the Gnome desktop (meaning with Network Manager). My network connection is a wired ethernet to a switch which then connects to a Netgear router. For some reason, this machine can't renew its leases with DHCP, so NetworkManager deactivates eth0, taking my machine off the network. I have to click Network Manager and enable eth0, which seems to work every time.
How can I fix it? Here are the relevant bits from /var/log/messages showing a failed DHCP request and then the successful renewal.
Code: Aug 1 04:00:08 ironton dhclient[12452]: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Aug 1 04:00:08 ironton dhclient[12452]: DHCPNAK from 192.168.1.1 Aug 1 04:00:08 ironton NetworkManager[1261]: <info> (eth0): DHCPv4 state changed reboot -> expire Aug 1 04:00:08 ironton NetworkManager[1261]: <info> (eth0): device state change: 8 -> 9 (reason 6) Aug 1 04:00:08 ironton NetworkManager[1261]: <info> Marking connection 'System eth0' invalid because IP configuration expired.
I've set up a permanent DHCP lease for my MAC address. I did this hoping to resolve the fact that I share my Internet ADSL connection with my wife and my daughter (the latter a great bandwidth hog)!
I would like to be able to schedule a limit for an IP connection for my kid's computers/iPods. Since I know the MAC addresses of their various hardware items, is there a way to shut down their connectivity at a particular time via the DHCP server or perhaps a firewall rule?
Running Ubuntu 10.04 and Shorewall is being used for the firewall.
Looking at var/log/messages below, it looks like I'm not being offered a lease on this particular network. I can successfully connect to the network because iwconfig wlan0 reveals my network ssid and the access point I'm connected to. But pinging google.com gives me nothing..
Code:
root@darkstar:/# tail -f var/log/messages | grep dhcpcd Mar 28 15:45:42 darkstar dhcpcd[5329]: wlan0: adding IP address 169.254.76.182/16 Mar 28 15:46:13 darkstar dhcpcd[5329]: wlan0: adding IP address 169.254.76.182/16 Mar 28 15:46:44 darkstar dhcpcd[5329]: wlan0: adding IP address 169.254.76.182/16
I'm having some problems bringing up my wireless card at boot time on my Red Hat Linux 9.0 box. After some investigation with the boot scripts, I noticed that it was having problems with the DHCP negotiations when the ifup wlan0 command is issued.I then tested the command outside of the booting process and everytime the command is issued the first time, the dhclient fails to get any DHCP offers and returns with the message Unable to obtain a lease on first try. Exiting. and then exits.
If I then issue the same ifup command again a second time, it successfully receives a DHCP offer from the router and receives the needed IP address, and after this, the Internet connection on the box works fine. It is consistently doing this everytime. Why is it failing to obtain a lease the first time?
I have a disturbing problem with my monitor which goes to sleep (or ??) after few minutes if my comp is not used and most of the time I have to restart my comp.I disabled everything in Powersave , but nothing. I did have that problem in previous versions of SUSE, but somehow, I solved that. I cant remember what I did then.
Why trying to avoid ranting about my Linksys router, I'll try and keep things short. I have a Linksys router in which the default firmware was terrible and would not correctly renew its DHCP lease. After getting feed up with that I flashed dd-wrt on the router and now it works better but randomly DNS queries would stop being resolved. To rule out the chances that it is my ISPs DNS servers I switched my DNS to openDNS, same problem happens (although I have to admit openDNS is a lot better than what my ISP has).
Anyways I'm about feed up with it and about an inch away from drop kicking the thing out my window. To avoid that I figured I will give it one more change and instead of using my Linksys as my network gateway I'll move all of that to my home server, and make the Linksys just an wireless AP. Besides setting up DHCP, DNS, and iptables on the server is there anything else I will need to know and setup on the server to make this work?
Side note anyone using openSUSE for DHCP know if setting up reserved IPs for certain MAC address is possible?
I have a openSUSE10.2(X86-64) Linux DHCP Server in my environment. It has a lot of VM's and Desktop systems which get added continuously. Also, it has a lots of Static-IP entries.Part-IIssue:The DHCP Server stopped leasing the IP's somehow.Workaround:1. Stopped the dhcpd service. (service dhcpd stop)2. Navigated to /var/lib/dhcp/db folder.3. Deleted the "dhcpd.leases" and "dhcpd.leases~" files.4. Recreated the "dhcpd.leases" file. (touch dhcpd.leases)5. Started the dhcpd service. (service dhcpd stop)
I have a strange problem for internet. My clients (winxp - S2) can't get internet.Let me explain my scenerios. Fedora 10 with lan (eth0) having direct internet from dsl model, client (XP service pack 2) can use samba shares using dhcp (wlan0) installed in Fedora 10 box. client can ping my linux box.Now problem is: client (dosbox) can ping the google ip address (i.e ping 74.125.39.106) but can't use 'ping www.google.com'. That means ping with ip works for internet from my client. My linux box can. I can use internet from FC10 but can't use iexplorer from my client to have internet. I have enable ipmasquarding in Firewall and dhcpd is running on wlan0 for dynamic ip address of my clients.Can someone suggest me what kind of problem having I? What should i do to success iexplorer for internet? what possibly am i missing?
My network interaces stop working after 5-10 minutes of operation. I have 2 network cards, one static IP and the other dhcp. Sometimes I can ping my router, other times I can't.
I buy a new usb network adapter (Through DX), when I try to use it in ubuntu or BackTrack4 Final it is working, and connecting networks even with WPA encryption. But after few minuts it stops working totally. It is showing that I'm connected to the AP but web sites do not respond.
Notes: - I have another PCI Wireless adapter which works fine.
- The problematic adapter works great on windows.
- A driver CD came with it, including a linux driver which I wasn't succesfully installed.
- A BackTrack3 Disc came with it, claming by the instructions that the adapter will work with it. I didn't try it because i have backtrack 4 final.
It took me dozens of surfing the web hours, and too many restarts,
After a fresh install of Ubuntu 11.04 (from 10.04) and spending several hours trying to figure out why the ad-hoc connection between my two computers (Fedora14 <-> Ubuntu 11.04) no longer worked - it had worked fine for almost 2 years with 10.04 - I've finally concluded it was a DHCP problem. This realisation (which was slow in coming!) dawned on me when I reversed my setup and configured the Fedora box as the DHCP server and everything was suddenly working perfectly! A quick internet search threw up an installation file called "isc-dhcp-server" which other Ubuntu 11.04 - related forums are also complaining about. My problem is that this file, although available in the repository, is not even installed!!!
It seems unlikely that the developers forgot to include DHCP support, so I hope someone can point me in the right direction.
I have a fresh install of SuSE 11.2. I have installed Communigate Pro (Email server) and Webmin. From my workstation (on the same LAN), I can access the web interfaces for both CGP and Webmin right after the server boots up. But after about 10 minutes or so, I can no longer access either web interface. The server itself still functions normally. I can get on the internet with the server, and I can control Webmin via localhost:10000.
The only thing that allows me to connect to it from my workstation again is to either restart the server, or go into "Network > Linux Firewall" and click "Apply Configuration". What's going on that makes my remote access stop working?
I've been trying to figure out a strange DHCP problem my girlfriend's having: She can only get (or renew) a DHCP lease once; Subsequent tries timeout. I tried switching from network-manager (which uses dhclient) to wicd (dhcpcd), and noticed a key difference: With wicd, restarting helps (again, works once, then another restart is required). With network-manager, I haven't been able to get another lease, period.
Exploring the dhcpcd case further, I found that suspend/hibernate do not correct the issue; a full restart is required. Neither does `/etc/init.d/wicd restart` help. I don't remember if I tried killing dhcpcd; I'll have to test that. The current workaround is to restart the computer after each disconnect. It's pretty annoying, though, so I'd like to try to collect enough specifics to file accurate bug reports for each dhcpcd and dhclient. Is anyone familiar with these projects? Are these known issues? Any ideas how to hone in a bit? My gut tells me there's some state somewhere that needs to get flushed.
I'm having a bizarre problem where my network connection stops working randomly. At first I thought it was a DNS issue since Firefox simply chilled out on "Looking up [hostname]" until it timed out, but after further investigation (pinging IP's, "host" and "dig" being unable to reach servers) it became apparent that I couldn't even access the DNS servers i.e. the Wicked Connection of the East was most sincerely dead.
There are two strange things about this: one, there are no errors except "timeout". The network manager is happy, Firefox is happy until the lookup fails... Two, the failures only start *after* DHCP configuration. DHCP configuration never has any trouble sending or receiving packets. I'm going to try static IP and whatnot to see if that helps, more information later.
I've been trying to install OpenSuse 11.0 on my ten-year-old Gateway desktop. It has been showing this screen for approximately thirty minutes. In case you can't read it, it says 'Decompressing Linux... done. Booting the Kernel.' I booted from the CD, and the OpenSuse screen came up, and I selected 'Installation' from the menu. And here we are.
Back in April I set up a Ubuntu DHCP server and a multiple VLAN network [URL] to migrate our various servers, workstations, etc off the 192.168.1.1 /24 network that everything was on because we where running out of address space. I built out the new network and everything worked great except our AD server would never get an IP address from the DHCP server (static reservation) and even if I set the IP statically on the AD server it couldn't ping the gateway and noone could log in. After several attempts to resolve this, including bringing in outside help, we where never able to figure out what the problem was.
Now 6 months later I have time to revisit the issue without effecting the live network. I used Acronis and imaged the AD server last Friday, cloned it on to another box with the same hardware, and put it up on the new network that's been sitting unused for the last 6 months. Today when I statically set the IP on the AD server (which is what I want) it connects and I can ping it's gateway 192.168.1.1 and all the way across vlans to a test sales agent workstation at 192.168.8.xxx on vlan 800 but only if I statically assign the agents station an IP address. When I try to get an IP address via DHCP it fails as destination unreachable. Nothing has changed in the last 6 months on the DHCP server but now it for some reason can't ping its default gateway 192.168.1.1. All of the config files are the same as they where left from the post linked above aside from the vlan id's used where changed from 1's to 100's (i.e. vlan 3 is now vlan 300) /etc/network/interfaces
Code:
auto lo iface lo inet loopback auto vlan100 iface vlan100 inet static
[code]....
why it can't reach the gateway, when I do a tcpdump I can see the DHCP requests come in on eth0 but the server never responds and I'm pretty sure its because it isn't "seeing" them since it thinks there isn't a network connection but I don't know how to trouble shoot to find out where the problem lies.
Back in April I set up a Ubuntu DHCP server and a multiple VLAN network [URL] to migrate our various servers, workstations, etc off the 192.168.1.1 /24 network that everything was on because we where running out of address space. I built out the new network and everything worked great except our AD server would never get an IP address from the DHCP server (static reservation) and even if I set the IP statically on the AD server it couldn't ping the gateway and noone could log in. After several attempts to resolve this, including bringing in outside help, we where never able to figure out what the problem was.
Now 6 months later I have time to revisit the issue without effecting the live network. I used Acronis and imaged the AD server last Friday, cloned it on to another box with the same hardware, and put it up on the new network that's been sitting unused for the last 6 months. Today when I statically set the IP on the AD server (which is what I want) it connects and I can ping it's gateway 192.168.1.1 and all the way across vlans to a test sales agent workstation at 192.168.8.xxx on vlan 800 but only if I statically assign the agents station an IP address.
When I try to get an IP address via DHCP it fails as destination unreachable. Nothing has changed in the last 6 months on the DHCP server but now it for some reason can't ping its default gateway 192.168.1.1. All of the config files are the same as they where left from the post linked above aside from the vlan id's used where changed from 1's to 100's (i.e. vlan 3 is now vlan 300) /etc/network/interfaces
Code:
auto lo iface lo inet loopback auto vlan100
[code]....
why it can't reach the gateway, when I do a tcpdump I can see the DHCP requests come in on eth0 but the server never responds and I'm pretty sure its because it isn't "seeing" them since it thinks there isn't a network connection but I don't know how to trouble shoot to find out where the problem lies.
I'm running Suse 11.3 fresh install, works fineBut I'm trying to make work a wusb54gv2, ndiswrapper -i works fineI'm using lastest ndiswrapper versionit seems tha options -m -ma -e maybe others don't workwhen doing ndiswrpper -l
goldf-fish:/ # ndiswrapper -l WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release. wusb54gv2 : driver installed
Currently I have my eth0 interface getting a DHCP address but at times the DHCP server will not be reachable. Sooo what I would like my server to do is if it cannot find a DHCP server assign a static address to eth0. Then start the DHCP service so it can then dish out some addresses.How can I do this? Surely it is possible
I have setup a dhcp server on eth0, & i have static Internet connection on eth1. now clients are getting ip automatically, they are able to trace root upto eth0 & eth1. but i am not able to access Internet from client machines. i am using open suse11 as a server. i am not able to do telnet & ftp also from client. i am able to access Internet from server. so please help me to configure my server so that i can access Internet from client machines also.
