[oclug] dhcpcd problems
Well, I tried the ne2k driver for that soho card, and it wouldn't install, saying device or resource busy. So, I tried the tulip driver, which installed. On a reboot, eth0 was detected (woohoo!). Then, I installed dhcpcd, and gave it eth0 as the interface. It segfaulted. Now, when I boot, the boot process stops at sendmail. I can boot into single-user mode to play with it, but dhcpcd segfaults every time. I've attached my boot log, and the message from dhcpcd when it dies. Suggestions would be greatly appreciated. Does this mean I don't have network support in my kernel?? Mike -- Michael P. Soulier, 1Z22, SKY Tel: 613-765-4699 (ESN: 39-54699) Optical Networks, Nortel Networks, SDE Pegasus ...the word HACK is used as a verb to indicate a massive amount of nerd-like effort. -Harley Hahn, A Student's Guide to UNIX Nortel Linux User's Group Ottawa: (internal) http://nlug.ca.nortel.com:8080 ---BeginMessage--- Linux version 2.2.12 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #2 Thu Aug 26 11:46:26 PDT 1999 Detected 451033251 Hz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 450.56 BogoMIPS Memory: 62876k/65536k available (1244k kernel code, 416k reserved, 900k data, 100k init) CPU: Intel Pentium III (Katmai) stepping 03 Checking 386/387 coupling... OK, FPU using exception 16 error reporting. Checking 'hlt' instruction... OK. Checking for popad bug... OK. POSIX conformance testing by UNIFIX PCI: PCI BIOS revision 2.10 entry at 0xfb460 PCI: Using configuration type 1 PCI: Probing PCI hardware Linux NET4.0 for Linux 2.2 Based upon Swansea University Computer Society NET3.039 NET4: Unix domain sockets 1.0 for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP Starting kswapd v 1.5 Detected PS/2 Mouse Port. RAM disk driver initialized: 16 RAM disks of 4096K size loop: registered device at major 7 PIIX4: IDE controller on PCI bus 00 dev 39 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA hda: QUANTUM FIREBALLP KA13.6, ATA DISK drive hdd: ATAPI CD-ROM DRIVE 40X MAXIMUM, ATAPI CDROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: QUANTUM FIREBALLP KA13.6, 13216MB w/371kB Cache, CHS=1684/255/63 hdd: ATAPI 40X CD-ROM drive, 128kB Cache Uniform CDROM driver Revision: 2.55 Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8 NCR53c406a: no available ports found Failed initialization of WD-7000 SCSI card! megaraid: v1.04 (August 16, 1999) scsi : 0 hosts. scsi : detected total. Partition check: hda: hda1 hda2 hda5 hda6 hda7 hda8 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 100k freed Adding Swap: 200772k swap-space (priority -1) parport0: PC-style at 0x378 [SPP,PS2] lp0: using parport0 (polling). Serial driver version 4.27 with no serial options enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A CSLIP: code copyright 1989 Regents of the University of California PPP: version 2.3.7 (demand dialling) PPP line discipline registered. PPP BSD Compression module registered tulip.c:v0.89H 5/23/98 [EMAIL PROTECTED] eth0: Macronix 98715 PMAC at 0xe400, 00 80 c6 f1 68 fa, IRQ 10. eth0: EEPROM default media type 10baseT. Unable to handle kernel NULL point dereference at virtual address current-tss.cr3 = 03d63000, %cr3 = 03d63000 ---End Message---
Re: DHCPcd problems - No valid Server response
On Sat, Sep 11, 1999 at 06:43:08AM +, [EMAIL PROTECTED] wrote: Have you tried running dhcpcd-sv rather than dhcpcd? Bryan Hello, I'm at the end of my wit here... I can't get my Linux box (running slink) to communicate with the DHCP server at my office. Windows 95 no problem. Static IP under Linux used to be no problem. (I updated to kernel 2.2.10 and to the dhcpcd 1.3.x package) Sigh Renald Yup, I tried and tried and tried... Even compiled the latest versions of it, but it still didn't work. Until I turned on the kernel-compile option CONFIG_PACKET and CONFIG_IP_PNP. Then it worked -- although it takes now about 10 secs instead of .5 secs to configure the network... But at least its working now. Maybe the HOWTO should be a bit more specific... Or maybe I should have figured the hint about SOCKET_PACKET in the README is really about CONFIG_PACKET? Grt, Renald Buter
Re: DHCPcd problems - No valid Server response
Have you tried running dhcpcd-sv rather than dhcpcd? Bryan On 18-Aug-99 Buter wrote: Used wrong email-address. Please respond to [EMAIL PROTECTED] Renald Hello, I'm at the end of my wit here... I can't get my Linux box (running slink) to communicate with the DHCP server at my office. Windows 95 no problem. Static IP under Linux used to be no problem. (I updated to kernel 2.2.10 and to the dhcpcd 1.3.x package) Sigh Renald -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
DHCPcd problems - No valid Server response
Hello, I'm at the end of my wit here... I can't get my Linux box (running slink) to communicate with the DHCP server at my office. Windows 95 no problem. Static IP under Linux used to be no problem. (I updated to kernel 2.2.10 and to the dhcpcd 1.3.x package) Sigh Renald
Re: DHCPcd problems - No valid Server response
Used wrong email-address. Please respond to [EMAIL PROTECTED] Renald Hello, I'm at the end of my wit here... I can't get my Linux box (running slink) to communicate with the DHCP server at my office. Windows 95 no problem. Static IP under Linux used to be no problem. (I updated to kernel 2.2.10 and to the dhcpcd 1.3.x package) Sigh Renald
dhcpcd problems
Hi all: I got my cable modem installed today, and now I'm trying to get it running under Linux. The Cable-Modem Howto directed me to the DHCP Howto, and it instructed me to install the dhcpcd client. I downloaded dhcpcd_0.70-5.deb and when I installed it I got the followinf error message from dpkg: (Reading database ... 49927 files and directories currently installed.) Preparing to replace dhcpcd 1:0.70-5 (using dhcpcd_0.70-5.deb) ... Stopping DHCP client daemon: dhcpcd. Unpacking replacement dhcpcd ... Setting up dhcpcd (0.70-5) ... dpkg: error processing dhcpcd (--install): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: dhcpcd The line indicating that it is stopping the DHCP client suggests that I already had it installed(?). dpkg says that it's half-configured now. I tried getting it off a couple of the alternate sites with the same results. Anybody know what I need to do? Am I on the right track to begin with? TIA -- __ _ Mark Wagnon Debian GNU/ -o) / / (_)__ __ __ Chula Vista, CA /\\/ /__/ / _ \/ // /\ \/ / mailto:[EMAIL PROTECTED] _\_v/_/_//_/\_,_/ /_/\_\
Re: dhcpcd problems
Hi all: I got my cable modem installed today, and now I'm trying to get it running under Linux. The Cable-Modem Howto directed me to the DHCP Howto, and it instructed me to install the dhcpcd client. I downloaded dhcpcd_0.70-5.deb and when I installed it I got the followinf error message from dpkg: (Reading database ... 49927 files and directories currently installed.) Preparing to replace dhcpcd 1:0.70-5 (using dhcpcd_0.70-5.deb) ... Stopping DHCP client daemon: dhcpcd. Unpacking replacement dhcpcd ... Setting up dhcpcd (0.70-5) ... dpkg: error processing dhcpcd (--install): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: dhcpcd The line indicating that it is stopping the DHCP client suggests that I already had it installed(?). dpkg says that it's half-configured now. I tried getting it off a couple of the alternate sites with the same results. 1) this package fails in 2.2 kernels and late 2.1, so get dhcpcd-sv if you use them 2) the package dies if no /etc/resolv.conf exists and also on some other condition, mail the maintainer to let them know of your current situation.
dhcpcd problems...
I am having a problem with my dhcp client. Basically the machine taking extremely long time to obtain an IP address. The machine is sending a DHCPREQUEST allright, and this is being answered by the server with the DHCPOFFER. However the sends several more requests before it starts to work. Also every time I shut the machine off it releases the IP lease, which results in the lease only lasting for the period in which the machine is turned on. Why does it need to release the IP lease? Surely it should hold onto it so that it can use the same IP on the next boot (until the lease really expires). Can I (and should I?) stop it doing this? I would appreciate any information. Thanks all, Chris -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: dhcpcd problems...
When you look at the log do you see that your dhcp client is requesting an IP address that it isn't being granted? It's probably trying to get its old IP and the server won't give it. I haven't read the RFC but I'll bet that releasing the lease on shutdown is compliant behavior. What would be the point of having a pool of IP addresses which could be handed out to any host if each client insisted on holding on to its address? In a lan environment this might (but not if people sometimes bring in laptops, etc.) be ok but for a situation like an ISP it would be impossible. Chris wrote: I am having a problem with my dhcp client. Basically the machine taking extremely long time to obtain an IP address. The machine is sending a DHCPREQUEST allright, and this is being answered by the server with the DHCPOFFER. However the sends several more requests before it starts to work. Also every time I shut the machine off it releases the IP lease, which results in the lease only lasting for the period in which the machine is turned on. Why does it need to release the IP lease? Surely it should hold onto it so that it can use the same IP on the next boot (until the lease really expires). Can I (and should I?) stop it doing this? I would appreciate any information. Thanks all, Chris -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- Jens B. Jorgensen [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: dhcpcd problems...
Chris wrote: Also every time I shut the machine off it releases the IP lease, which results in the lease only lasting for the period in which the machine is turned on. Why does it need to release the IP lease? Surely it should hold onto it so that it can use the same IP on the next boot (until the lease really expires). Can I (and should I?) stop it doing this? This will happen if the network you are on is running low on ip addresses. Basically when you shutdown, I believe the server knows. Then, it will try to give out IP's that haven't been used before to new users or users who's ip was taken. Then it falls back to giving out any ip address that is free. When you boot up, you ask for the ip, and if it's available, you should get it. I'd suggest contacting the network admin (or service provider) and ask if they have enough ip's that you should have a stable ip address. Brandon - Brandon Mitchell [EMAIL PROTECTED] We all know linux is great... it PGP: finger -l [EMAIL PROTECTED] does infinite loops in 5 seconds Phone: (757) 221-4847 --Linus Torvalds -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
