I think I'd be tempted to look at dhclient instead. I've had similar problems with pump on the Shaw network. It may even be related to the 3c509 NIC's I have, but in previous LEAF versions (eiger, eigerstein) things worked properly (with the newer version of dhclient).
My symptom was that 3 times out of 4 (or so) I couldn't get a lease on boot. After boot I could run pump and get the lease, although not always. I did have an occasion when I couldn't get one for a couple of days after some initial success. I changed to another 3c509 and haven't had this happen since. Looking back at it, out of 3 3c509's, all have managed to obtain leases. One was unlikely to get one at boot but could when pump was run manually after. Another worked for a few days, then refused to get a lease by any method. The third has run flawlessly. The questionable NIC's have found homes in other projects and have worked just fine (where no Shaw dhcp is required!), so they appear to be sound. So, while I have trouble believing the characteristics of the particular NIC can be the problem, I'm starting to wonder... Until I installed the last NIC I was convinced I'd be going to dhclient. If you do try it, let me know if this solved the problem - I'm curious now! I may go to dhclient just for peace of mind... Brock > Date: Thu, 23 May 2002 13:49:49 -0500 > To: J <[EMAIL PROTECTED]>,[EMAIL PROTECTED] > From: JamesSturdevant <[EMAIL PROTECTED]> > Subject: Re: [leaf-user] PUMP > > Are you trying to use pump on eth1? I recently discovered > that it is not reliable except on eth0. For instance, I have > one unit with three 3c509 cards. In that machine, it works on > eth1. I have another with a 3c509 for eth0 and an SMC Ultra > for eth1. Pump sends the request out on eth1 and listens for > the reply on eth0. I was able to determine this by plugging > both cards into the same hub and watching the lights and > watching the logs on my dhcp server. When I switched the > modules so the SMC loaded first and became eth0, it was able > to receive the address so I knew it wasn't the card. I did > some searching and found similar reports on the redhat site. > I don't know if dhclient has this problem or not. > > JamesS > At 11:29 AM 5/23/02 -0700, J wrote: > >Quick question/problem about pump. > > > >I had my Bering system setup working smoothly just > yesterday. Today I > >found that the internet gateway wasn't functioning. It seems that > >Bering (pump) was unable to renegotiate a DHCP lease with my cable > >provider. And now, it remains unable to do so, even after > reboot, etc. > > > >I can ping other hosts on the internal network, but nothing > gets out. I > >backed up all my settings, and had rebooted several times, > so it's not > >that. > > > >What confuses me is that WinXP is able to get a DHCP lease > whenever it > >wants, and pump isn't able to. What's the difference? Is my provider > >blocking access? I don't think Cogeco Cable forces the MAC > address to > >remain constant (in fact, it worked on this very same setup > >yesterday!). > > > >So what the heck is wrong? heh. > > > >Thanks, > >-- > >JCA _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
