Re: dhcp ip addresses
On Sat, 28 Jul 2001, Eric Boo spake: Hi all, I'm using pump on SID. My ISP is a cable provider who do not issue static ips. Usually, when I use pump, I have the same ip address for months, unless I switch off the modem and someone else grabs it. When I reboot into windows on the same machine, I get another ip address, then when I go back to linux again, it's back to the same old ip address again (assuming no one grabbed it). If I use dhcpcd, it's another ip. Question: How are these ip address stored, if they are (under pump espcially), and how do I force pump to get another different ip if needed? Here's the deal: Your computer gets a lease from the dhcp server. The lease is for a specific period, for example, 3 days. Halfway through the lease period, your computer's dhcp client should automatically request that the least be renewed, so you get a new 3-day lease. _Typically_ if you never shut down, your TCP/IP address will never change. When you run Windows, you can see the lease details via WINIPCFG or IPCONFIG. The former is a gui utility built into Win95/98/Me. The latter should be run from the WinNT/2K cmd shell. (Try IPCONFIG /ALL). Both of these tools allow you to release or renew your lease manually. I'd love it if someone would reply and post the Linux equivalents, I behind on my RTFMing. Likely, your computer automatically tries to renew the lease each time the eth0 interface starts up (eg, every reboot or running ifup in Linux. The current OS _probably_ looks like a different computer to the DHCP server. If the other OS's lease hasn't expired, it'll naturally give you a different address because it thinks you're a different system. How are the addresses stored? That's up to the DHCP client, Windows and Linux probably do it differently. If they have a current lease, they'll keep using it. If the lease has expired while that OS wasn't running it should try to get a new lease as soon as it starts up, and it's going to take whatever the server gives it. The DHCP server controls the lease period and whether the server attempts to reserve expired leases. HTH, Paul
Re: dhcp ip addresses
Eric, I'm not sure if i can answer your question, but i may be able to clearify the cable-modem issue a little. My brother has the cable modem and uses Win2k - i did notice that getting the dynamic IP address all depended upon his computer name. It appears to me that ATT uses the host name to dish out IPs that have accounts with ATT. If my brother doesn't have the proper computer name in place, he wouldn't get an IP - and thus, could not surf. Hope this helps, Duane Curlee ([EMAIL PROTECTED]) Debian User (err... Attempter, anyway) On Sat, 28 Jul 2001, Eric Boo spake: Hi all, I'm using pump on SID. My ISP is a cable provider who do not issue static ips. Usually, when I use pump, I have the same ip address for months, unless I switch off the modem and someone else grabs it. When I reboot into windows on the same machine, I get another ip address, then when I go back to linux again, it's back to the same old ip address again (assuming no one grabbed it). If I use dhcpcd, it's another ip. Question: How are these ip address stored, if they are (under pump espcially), and how do I force pump to get another different ip if needed? Also, I can't seem to use pump on the command line after releasing it with pump -r. pump -R -i eth0 and simply pump both gave operation failed. Maybe I should go back to dhcpcd. Or is there an alternative? How's dh-client? Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp ip addresses
On Sat, Jul 28, 2001 at 10:02:49AM +0800, Eric Boo wrote: Question: How are these ip address stored, if they are (under pump espcially), and how do I force pump to get another different ip if needed? Also, I can't seem to use pump on the command line after releasing it with pump -r. pump -R -i eth0 and simply pump both gave operation failed. Maybe I should go back to dhcpcd. Or is there an alternative? How's dh-client? Try to see if the pump process is still alive. IIRC, if you start pump the first time, it will fork and run in the background. You can communicate with the running pump by starting anothter pump process, that will use a local socket to talk to the background pump. Sometimes the background pump becomes unresponsive, I've found, and you need to kill it and restart pump. YMMV. It is also possible that you setup firewalling rules and that somehow these interact badly with pump. You can debug this easily by prepending a rule to the input and output chain that logs any packets on any interface and has no jump target. Then start pump and watch the syslog. Remember to remove the logging rules when you have captured enough pump packets, or else it will make your logfiles explode. Cheers, Joost
Re: dhcp ip addresses
Hi, Thanks for your reply. However, my firewall has been showing many ips running the same exploits (port 53) against as well as pinging my machine. I'm thinking of grabbing a different ip from my dhcp-providing cable ISP. So far, dhclient and pump keeps giving me the same ip, even when I apt-get remove --purge and install the other. Only dhcpcd from stable gives me another ip. I'm using SID, so is there a way to use pump or dhclient to drop the current ip that they insist on giving me and force them to look for a different one? -- Eric Boo Sunday, July 29, 2001, 10:46 AM 26 minutes http://magicman.freeshell.org Its name is Public Opinion. It is held in reverence. It settles everything. Some think it is the voice of God. -- Mark Twain
dhcp ip addresses
Hi all, I'm using pump on SID. My ISP is a cable provider who do not issue static ips. Usually, when I use pump, I have the same ip address for months, unless I switch off the modem and someone else grabs it. When I reboot into windows on the same machine, I get another ip address, then when I go back to linux again, it's back to the same old ip address again (assuming no one grabbed it). If I use dhcpcd, it's another ip. Question: How are these ip address stored, if they are (under pump espcially), and how do I force pump to get another different ip if needed? Also, I can't seem to use pump on the command line after releasing it with pump -r. pump -R -i eth0 and simply pump both gave operation failed. Maybe I should go back to dhcpcd. Or is there an alternative? How's dh-client? Eric
