HOSTING AT HOME

[zz at rockstone.com]

> > Arrogant tone is often an indicator of ignorance or stupidness.  
> > The trick is to make the dhcp always keep the same leased ip address the
> > client machine. That means client machine has to stop dhcp re-negotiation
> > request to the server once an initial lease is obtained.  If you keep the
> > traffic activity, the dhcp server will have to treat that leased ip is
> > already occupied on the LAN, if the dhcp server is configured properly
> > for avoiding ip conflicts. Thus the ip is not to assign to another machine.   
> > thus effectively not expire the original ip lease. 
> > Netbios name is equivalent to host name under a domain.
> 
> Not every machine speaks NetBios.

  Correct, but every machine has a host name.
 
> There is official no way to keep an IP it it expires. The're scripts /
> dhcpcd hacks that will keep trying until it receives the wanted IP.

  you can try to 'hi-jack' the ip by doing this trick, you may need
  an extra machine if the lease is less than 1 min (time needed to
  reconfigure your machine to static and stop dhcp on client):

  1. use a machine running client dhcp and start it up, examine what
     ip address obtained, and write it down. If the ip lease is over
     5min, you have sufficient time to reconfigure your machine to
     static ip using this ip address. Immediately restart net service
     and you are now static. @home DHCP server won't re-assign this 
     ip address to any other machine.  
 
  2. If the lease obtained from the server is less than 1min, (most
     servers offer much longer lease time), you can do this:
     Prepare to machines, one is dhcp client, and other one static,
     put the dhcp client machine on-line first, once obtained a ip
     from the dhcp server, immediately put this ip address to the
     other standby machine and disconnect the dhcp client machine,
     then connect the static machine. boom, you have hi-jacked the
     ip and you are online static. The server has no way to change
     or stop your using that ip.
  
> Stopping DHCP nogotiation doesn't stop the provider from reassigning the
> IP. At least not with this one. I tried that, and I ended up with no
> IP. The client has nothing to say in many cases. The only thing I do is
> refuse to accept the domain name DHCP gives me. It confuses services on
> this machine, so that stays the same.
> 
> The reason why this ISP is brutally changing IP's (yes, you're right that
> it isn't suppose to change IP's when traffic occurs) is the major amount
> of ubuse.
> 
> > >     The issue in this case was that he wants to buy an IP that doesn't
> > >     belong to his ISP. No way that works. 
> > 
> > why buy an useless, meaningless, ip address while his ISP will likely
> > refuse route it, when he can achieve his goal in a more simple effective
> > way?
> 
> My point. No way the ISP will route ip.
> 
> My reaction wasn't suppose to come over as arrogant. I apologise for that. 
> 
> 
> 
> 	Igmar
>