OK, so airport lounge has free wifi, as it should.
Only trick is that they seem to be lacking a DHCP server at the moment!
A quick tcpdump shows a lot of NETBIOS packets from 169.254.x.x and lots of unanswered bootp requests. Ho hum. A lot of puzzled faces curing at their laptops too.
Thankfully it was pretty obvious what network was in use (192.168.0/224) and gateway (192.168.0.1), and the hotel's DNS servers still in my config worked as well. So I have wifi!
How hard can it be to get things like this right FFS.
Subscribe to:
Post Comments (Atom)
More with E-paper
My previous code allowed a number of settings to be stacked up to suit all sorts of needs - a clock, day of week, sunrise/sunset, and even b...
-
Broadband services are a wonderful innovation of our time, using multiple frequency bands (hence the name) to carry signals over wires (us...
-
For many years I used a small stand-alone air-conditioning unit in my study (the box room in the house) and I even had a hole in the wall fo...
-
Drivers should be aware what road signs mean. And so they need to be clear and unambiguous. But some are a tad more challenging than others,...
This is not an uncommon event in Airports - I had the same twice while travelling last year.
ReplyDeleteRun your own DHCP server whilst you're there :p
ReplyDeleteTony, I did that at Bristol UWE in one of the halls of residence - then watched the traffic. It was amazing how many people had spyware :(
ReplyDelete