Re my previous message, it appears the need for frequent re-activation of the connection is due to just losing the DNS information. I can stay connected while using ssh or telnet. But anything requiring names instead of ip's stops after a few minutes.
Rick B.
On 5/1/06, RICHARD rab@nauticom.net wrote:
Re my previous message, it appears the need for frequent re-activation of the connection is due to just losing the DNS information. I can stay connected while using ssh or telnet. But anything requiring names instead of ip's stops after a few minutes.
If the hotel doesn't block udp port 53 you should be able to run your own dns server. if its installed
service named start
should get it running. you could test it with
dig google.com @127.0.0.1
if it doesn't time out you should be able to configure your network to use that as its DNS and you would be away.
RICHARD wrote:
Re my previous message, it appears the need for frequent re-activation of the connection is due to just losing the DNS information. I can stay connected while using ssh or telnet. But anything requiring names instead of ip's stops after a few minutes.
Rick B.
Do the entries in /etc/resolv.conf change, or do the name servers stop responding? It could be part of the validation process by the hotel's Internet setup. If you don't visit a specific web page and agree to the terms, then ether the dhcp server sends a new set of name servers when the lease renews, or firewalls your IP from the name servers. Dropping the connection, and restarting it resets the timer. But I am just speculating here...
Mikkel
you might take a look at what they're handing you via dhcp, if it's bogus, and the lease time is really short (like 5 minutes). then your laptop is re-dchping when the lease expires.... it sounds really like the hotels dhcp server is propbably misconfigured.
joelja
Mon, 1 May 2006, RICHARD wrote:
Re my previous message, it appears the need for frequent re-activation of the connection is due to just losing the DNS information. I can stay connected while using ssh or telnet. But anything requiring names instead of ip's stops after a few minutes.
Rick B.