iface mwlan0 inet dhcp
and replaced it with
iface mwlan0 inet static
which was obvious enough. After this I just added values for the static IP I wanted, the netmask, and the gateway, and everything was up and running as expected, excellent!
Well, not quite.
Somewhere along the line, I've no idea where, I'd picked up a new wireless network on the block: one with the exact same name as my current one, but in ad-hoc form. Puzzled, I instantly assumed the Gumstix was responsible; it is, after all, the newest system, and one with which I've no experience - perhaps I'd inadvertantly set up an ad-hoc network. Unplugging the Gumstix, however, did not seem to affect the network.
Next, my thoughts turned to dad's laptop. Perhaps, in his need to get online, he'd inadvertantly set up an ad-hoc network! This turned out to be a red herring too.
At this stage I was becoming rather annoyed: my minor success with the Gumstix was being tainted by a tough, unruly ad-hoc network that refused to die. Maybe someone outside was trying to trick us into connecting to this network instead of our own for some reason? It seems not; no unmarked vans parked across the street.
Turning off all computers in the house also failed to solve the problem...initially. Then, as quickly and mysteriously as the network had appeared, it was gone!
Numerous "iwlist mwlan0 scanning" calls on the Gumstix (every five-ten minutes for the past hour) turned up nothing except my own, trusty router.
Very odd, indeed, but probably something of my own doing.
So, after all of this drama, the Gumstix is up and running on my own router, with encryption and a static IP. I may attempt to cross-compile something tonight, as the buildroot seems to have completed successfully this time, but all this ad-hoc chasing has worn me out.
No comments:
Post a Comment