this is rather odd actually and has never happened to be before.I recently installed slackware in a toshiba satellite m40 185 laptop and during boot it doesn't get an ip address from the server. the boot messages are of the sort:
dhcpcd: v5.2.2 started
dhcpcd: waiting for carrier
dhcpcd: timed out
[code]....
slackware-current kernel 2.6.35.10-smp for instance if i just want to connect to wep ap. i done
[code]...
it says waiting for carrier and it just time out, im wondering why i read somwhere that its not working good with slackware 13.1
I just realized that since I reinstalled slackware on my laptop, the machine is not obtaining an IP from my router during the startup proccess like it used to do before.
Now I see something like:
Code:
dhcpcd: eth0: waiting for carrier
dhcpcd: eth0: timed out
dhcpcd: eth0: waiting 8 sec
and it fails. After I login in KDE, I need to manually renew (or acquire) an IP. Issuing the command
[Code]...
For some reasons, dhcdpd wouldn't connect eth0 at startup and it takes 10 to 15 seconds of timeout. Since I don't really care because I use wifi, I would like to remove auto dhcpcd at startup but I can't fint it anywhere in /etc/rc.*.
View 3 Replies View RelatedI recently upgraded to a Intel i3 cpu and Intel H55 motherboard. This was from an old P4 machine that was running Slackware 13.0. The machine is a single connection to the internet through a cable modem. I moved the hard drives over, and found that dhcpcd would not work with this board in either Slackware 13.0 or 13.1 (after updating). I tried both the Gigabit onboard Lan, an old PCI ethernet card and installing the most recent version of dhcpcd. No luck. Dhcpcd would negotiate the lease with my cable modem, assign an IP address. But after that the process stalled. The internet was unreachable, and no nameservers were printed in /etc/resolv.conf. Manually killing dhcpcd and entering: "dhclient -4 eth0" got me on the internet without a problem. As this appears to be a lingering problem with dhcpcd, I am going to try to use dhclient permanently. Has anyone else moved over to using dhclient? If you have modified your startup scripts in /etc/rc.d to use dhclient.
View 3 Replies View RelatedI am on slackware 13.37 using broadcom-sta and wicd from /extra. Every so often, sometimes really often, my wireless resets it's connection. The only common thread I can see in the system log is at the same time I get 4 messages that "dhcpcd not running"
View 11 Replies View RelatedLooking 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
[code]...
we have a problem with dhcpcd at boot time on any openSUSE version from 11.0 to 11.3. It seems that a number of workstations never send out DHCPDISCOVER or DHCPREQUEST at boot time, we have verified this with packet dumps. The dhcp client progress bar is displayed on the console but eventually times out, goes into background and the system continues booting.This is a problem because the timeout takes a long time and users have to wait. Sometimes the display manager is even started but users cannot using LDAP authentication. Eventually these systems just continue to use their old lease and networking works.Curiously, when we do a network restart after boot, the clients send DHCPDISCOVER/-REQUEST normally, we only have this problem at boot time.
On the server side we're using ISC dhcpcd-1.3.22pl4-223.13 on SLES 10 SP2. I have read about others who had the same problem, they switched from dhcpcd to dhclient. I have also tried this, but for us dhclient is not an option for a number of other reasons. Another thing I have tried is setting DHCLIENT_SLEEP ("Some interfaces need time to initialize. Add the latency time in seconds")o two minutes to give the interface time to initialize.nfortunately this didn't change anything.
Recently I have installed Fedora 10. It comes with firefox 3.xx by default. Now I was wondering if there is any way through which i can update it to 3.5 version though yum. I have tried yum update firefox but it did not work and returns following messages Loaded plugins: refresh-packagekit Setting up Update Process No Packages marked for Update I know that one way to update is download the latest Tar package and use it, but I want to totally remove my previous installation and use solely one package i.e. firefox 3.5.
View 6 Replies View RelatedDoes jexec need to be modified? Not clear from the error messages which jexec is
involved.
Result of zypper update...
The following package is going to be upgraded:
dhcpcd
1 package to upgrade.
There are some running programs that use files deleted by recent upgrade. You may wish to restart some of them. Run 'zypper ps' to list these programs.
The following running processes use deleted files:
You may wish to restart these processes. See 'man zypper' for information about the meaning of values in the above table.
I manage to connect to my wifi using
Iwconfig wlan1 essid "mywlan" key 1234567890
Then iwconfig wlan1 gives me:
Im using a Alfa Awus036h wifi dongel under Arch disc install, only got wifi on other computer.
I tried to run dhcpcd but it says i need to install it and I need to enable a component called universe. How do I do that?
View 3 Replies View RelatedI know questions of the form "wireless not working on <blank>" abound, but here is another! I can't cut and paste since I don't have a connection on the computer I am having trouble with but I will paraphrase the best I can.
lspci output:
0c:00.0 Network controller: Intel ... PRO/wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
lsmod output (relavent line):
cfg80211 33680 3 iwlagn, iwlcore, mac80211
iwconfig shows wlan0 up and running, and iwlist scanning shows the router. I used to be able to just run dhcpcd wlan0 and connect, but now I get a
"timed out waiting for a valid DHCP server response"
Same deal running /etc/rc.d/rc.inet1.conf (which might be the new way Slack connects to things).
Not sure if it's important, but I have a little indicator light on my laptop that tells me if wireless is running. Before I try dhcpcd, the light is on. After it times out, the light goes out and I have to redo everything (ifconfig wlan0 up etc....) in order to get the light back on.
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.
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 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.
I've a question about how work dhcpd. I'm on CentOS 5.6. I has a dhcpd server on it. His configuration:
authoritative;
ddns-update-style none;
deny declines;
deny bootp;
option domain-name "mydomain.domain";
option domain-name-servers IP;
option routers IP;
option time-offset -18000;
#option ntp-servers IP;
subnet IP netmask MASK {
range IP START IP END ;
default-lease-time 86400;
max-lease-time 172800; }
And now in the /var/lib/dhcpd/dhcpd.lease file, there few entrie for the same IP. Sometime I've ten same entries for the same IP. Can I have only one entrie by IP? Is there any problems in my configuration of my dhcpd.conf file?
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?
View 1 Replies View Relatediam running dnsmasq on my target board , my dnsmasq.conf has following configurations
# cat /var/etc/dnsmasq.conf
strict-order
localise-queries
[code]....
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.
lease {
interface "tap0";
fixed-address 10.0.1.16;
filename "***";
medium "-link0 -link1 -link2";
[code]....
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)
Code:
lease-file-name "/etc/dhcpd.leases";
default-lease-time 43200; # 12 hours
[code]....
I have a dhcpd server running CentOS and Webmin. I noticed in my lists of expired leases some of the lease times are only a few hours even thought I have lease length set to 1 week. I want to keep a lease for a week even if the device requests that it be expired. Is there some way I can do this in dhcpd? I am attaching a screenshot of some of my lease times listed in Webmin.
View 4 Replies View RelatedSo I got slackware 13 from the website and created 4 partitions (primary) and left some (100GB) space as I planned to install windows 7 in that. After installing slack, when I booted from windows DVD (rtm) in partition section it said I already have 4 primary partition so windows cannot used the rest of space despite the fact that it was free (windows even grayed all options like new partition and format etc. for that space). So I thought I'd create 2-3 primary partition for linux (slackware) so that windows can use the free space and make it a primary partition.
So, Next I formatted with slack (3 partition, 2 Primary, 1 extended, total space for slack 50GB) and after its installation I worked my way with windows, but it just created one partition of 100Gb, won't let me create any saying all primary partitions are created. Anyway, I created that partition and installed windows 7. But it messed up my lilo (slack won't show in boot menu) neither can I create any new partition.
After all I reformatted again created 2 partitions for windows (that actually became 3 as windows 7 create 100Mb separate partition for system). Installed windows correctly. Then I booted with slack , which allowed only creating 1 partition as 3 were already there. So I created 1 extended partition, in which I created 4 partition 1 to mount for /boot (100M), 1 for /swap (3G), 1 for home (10G), 1 for / (35G) everything worked fine till I reached last point to install lilo. At that point it said cannot install Lilo (I tried all options simple, expert, install to MBR etc.) but it just won't install. Anyway, after that it said you can install it manually so I clicked OK. Then it said setup complete, remove disk and press alt+ctrl+del to reboot, which I did. But there is just windows 7, no slack ?
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 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)
[Code]...
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.
[Code]...
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)!
View 5 Replies View RelatedI try to install Slackware to my IDE hard drive and boot first from Slackware DVD. After I loaded huge.s kernel, and tried to partition the hard drive using fdisk by entering "fdisk /dev/hda", I found out that the partition size is max to 3 Gigs instead of 80 Gigs.
I think the kernel is looking at my boot disk, which is around 3 Gigs. How can I make so that it looks at my IDE drive instead at my boot drive? Is there any manual that shows me how to install Linux from scratch this means I want to wipe out all my hard disk and install Slackware Linux there?
I'm trying to install Puppy 525 on my Slackware 13.37 PC as a dual-boot using LILO. Puppy is living, all on it's own, in sda6, a 6 GiB partition. It got there by using the Puppy Universal Installer and selecting a 'Full' install, not a 'Frugal' install. I cannot find 'LILO' type instructions, only 'GRUB' type instructions.
Has anyone succeeded in doing a hard drive install of Puppy with the LILO boot loader?
Edit: I'll probably regret it, but I used Puppy's GRUB installer.
