[H-GEN] RH 7.2 PCMCIA Boot and Dynamic IP address renewal

[David Jericho]

[ Humbug *General* list - semi-serious discussions about Humbug and  ]
[ Unix-related topics.  Please observe the list's charter.           ]
[ Worthwhile understanding: http://www.humbug.org.au/netiquette.html ]

On Fri, Mar 08, 2002 at 09:11:02AM +1000, Hilton Travis wrote:

> I noticed a second "//" immediately after the ip address of the web
> server, and I *think* this is the issue.  When I installed from the
> network boot disks (not the PCMCIA boot disks) onto another machine,
> from the exact same web server, it worked fine.
> 
> Any ideas, because I am really stuck on this one.

The // and the //./ make no difference to the url fetching. It's all
path relative stuff. / = // = //./

Being a laptop, and PCMCIA in particular, I'd make sure you can
actually ping the laptop from another machine on the network, just to
verify that infact the network is active and sending and receiving
traffic. I've seen this problem a few times before with some cards.

> 2. In Windows, I can type "ipconfig /release" and "ipconfig /renew" to
> release and renew the IP address that has been dynamically assigned to
> the NIC.  I have tried searching for a way to do this on Linux, but have
> so far been unsuccessful.  It seems neither dhcpcd nor ifconfig support
> this functionality, and I thought that dhcpcd would be the obvious
> choice.  Does anyone know of a way to release/renew the IP without
> rebooting the machine?

Through the use of a purely irrational thought process, much akin to your 
average #linuxaus debian fan's basis for their choice of distribution, I
prefer to use pump over dhcpcd. 

>From the pump man page, 
        -R       --renew               Force immediate lease renewal
        -r       --release             Release interface

>From the dhcpcd man page,
        -n     Sends  SIGALRM  signal  to the dhcpcd process that is currently 
               running which forces dhcpcd to try to renew the lease. If dhcpcd 
               is not running, the flag is ignored and dhcpcd follows  the 
               normal startup procedure.
        -k     Sends SIGHUP signal to the dhcpcd process that is currently running. 
               If dhcpcd receives SIGHUP it will send DCHP_RELEASE message to the 
               server and destroy dhcpcd cache.  In  a  case  dhcpcd receives  
               SIGTERM  which is normally used by shutdown(8) when rebooting the 
               system dhcpcd will not send DHCP_RELEASE and will not destroy cache. 
               When system boots dhcpcd will use cache  to request the same IP 
               address from DHCP server which was assigned before the system went down.

-- 
David Jericho

--
* This is list (humbug) general handled by majordomo at lists.humbug.org.au .
* Postings to this list are only accepted from subscribed addresses of
* lists 'general' or 'general-post'.