Re: Port 18593 attacks
bbales <[email protected]> Tue, 3 Aug 2004 12:57:33 -0500
| Newsgroups | gmane.org.user-groups.aclug.linux-help |
|---|---|
| Message-ID | <[email protected]> |
On Monday 02 August 2004 17:58, you wrote: > Powering it off will release the IP; But ONLY when the lease expires > and it does not get renewed. Bruce said that, and I have experienced > it. > > Usually a lease gets renewed some (specified) time before it expires, s= o > the modem will need to be powered off for at least the lease period in > order to force the issuance of a new IP. > > On Fedora Core 2, pump has been removed and dhcp client is serviced by > dhclient. Old lease info is kept in the dhclient.leases file. Removing > or emptying that file may force assignment of a new lease without > waiting for the lease to expire. I am unable to test because I do not > use dhcp, but info dhclient has lots of information (including how to > explicitly release a lease). > > Also look at dhclient.conf file. The 12 hour power off didn't work. Cox told me the lease was up at 5:50 = so I=20 pulled the plug from 5:00 PM until 10:30 this morning. Same IP address. = For=20 two minutes I got hits on other ports - then the hits were all (or 96%) t= o=20 18593. Got 514 in 90 minutes. The owner of the lease is a Frazierwall box with a very limited Linux sys= tem,=20 so I doubt if it has dhclient. I'm still investigating. John and Adam suggest releasing the lease and dropping another ethernet b= oard=20 in. I could do that if I knew how to release the lease. The box has dhc= pcd,=20 but no man page. As far as I can tell, this isn't hurting anything. If Frazierwall didn't= send=20 in a list of blocked connections I wouldn't have known it was happening. = But=20 I'd still like to get it stopped. bruce -- This is the [email protected] list. To unsubscribe, visit http://www.complete.org/cgi-bin/listargate-aclug.cgi