Thanks for the other notes here too. I allready know the provider. I did an nslookup
and got the name associated with the IP and it was all too familiar. The IP was also
very close. . .it is another DSL user with my provider. I intend to contact them
about the problem, but I was hoping to avoid that since they are known to be non-linux
friendly and the explanation of the problem leads to my use thereof.
Thanks anyway.
-DRW
On Fri, 20 Oct 2000 22:20:51 -0400, you wrote:
> On Fri, Oct 20, 2000 at 08:48:01PM -0400, Michael Burger wrote:
> > On Fri, 20 Oct 2000 19:44:43 -0400, Darren R. Weber wrote:
>
> > >Is there a way to force pump to get a different address? Here is the reason I
>ask.
>
> > >I know I can tell it to release, and then restart it but it just gets the same
>address again. I am on DSL and some idiot in Miami has apparently set up my IP as a
>nameserver. I have ipchains running and denying almost everything so there is no
>immediate problem, but I also log some packets and this stuff is filling my log with
>garbage every two seconds. I have tried to stop this several times in various ways,
>even to the extent of crashing the box on the other end. (It's a windows box. .
>.did a little digging on it :-) ) That worked but only temporarily and if I
>continue to do that I'm going to get myself into trouble. So I figured the easy
>thing to do would be to try to get a different IP.
>
> > >Is the only way to release my current IP and wait until the server has had time
>to give out the old one?
>
> > Pretty much. The thing about DHCP is that the server maintains a
> > database...that database keeps track of the IP address and the MAC
> > address to which it was last assigned. It keeps that information
> > until the lease runs out.
>
> Well... I can't say so much about pump, but dhcpcd has a release
> option that specifically issues a RELEASE back to the server releasing the
> lease and returning the address back to the pool. Now... That just puts
> you back to where you started from and that's at the mercy of the dhcp
> server. Next time you request a new lease, it may give you the old
> address or it may give you a new address. You also have to make sure
> that you blow away anything you have cached on the client side (which
> the release option for dhcpcd does).
>
> > The other thing to consider is whether or not your DSL provider has
> > hardcoded your system for that IP.
>
> That would be a problem.
>
> > The other possibility is that you could call your provider and ask
> > them to reassign your IP address.
>
> I would do a whois on the address of the annoyance and track
> down his ISP. Send letters of complaint to the ISP, the POC for the
> address, and several postmasters at the ISP site. Raise enough hell
> with the administrators responsible for the network he's on and the
> word will eventually rain down on him. If you don't do this, you may
> get the address released, but that just passes the problem onto the
> next guy who gets it.
>
> Mike
> --
> Michael H. Warfield | (770) 985-6132 | [EMAIL PROTECTED]
> (The Mad Wizard) | (678) 463-0932 | http://www.wittsend.com/mhw/
> NIC whois: MHW9 | An optimist believes we live in the best of all
> PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Darren R. Weber
[EMAIL PROTECTED]
AIM: TuxUser
ICQ#: 2849193
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
