Tales from the Mortgage Monster: automating logins
-
It's on channel 1--most of the other people on the neighborhood are on 6 or 11. I was wondering if 3/4 or 8/9 would help at all.
My understanding is that 1, 6 and 11 are the only channels that reliably don't bleed into each other. But it's been a while since I set up the WiFi at work to use the same SSID for multiple APs in different locations.
-
My understanding is that 1, 6 and 11 are the only channels that reliably don't bleed into each other.
Channel overlap is pretty much gone for any pair of channels more than 5 apart, and in the US you only have 11 channels to play with. So if you need three mutually non-interfering channels, then 1 + 6 + 11 is pretty much the only choice.
If you're trying for good coverage over a multi-WAP campus, you can sometimes end up with less overall interference by designing a four-channel layout with some channel overlap deliberately built in, relying on physical placement to minimize inter-WAP interference.
Channel 6 is often the default on WAPs as shipped, which is kind of a pain because if that's what your interference is on, you're pretty much stuck with a three-channel layout.
-
Give your home LAN an unusual private IP address range (mine is 192.168.119.0/24) and make sure you have plenty of DHCP leases in the pool
I haven't tried changing the address range yet, but the router is using 192.168.0.2 through 254.
-
the router is using 192.168.0.2 through 254
Yeah, and that's a very common range so it's quite likely that your phone has at some point been handed an address within that range by some other router's DHCP server. Then you bring your phone home and, Android networking having been thrown together by idiots, it starts using a 192.168.0.0/24 address that somebody else gave it on some other LAN as soon as it wakes up. At which point it starts fighting with some other device on your LAN that acquired that same address legitimately from your DHCP server.
-
Yeah, and that's a very common range so it's quite likely that your phone has at some point been handed an address within that range by some other router's DHCP server. Then you bring your phone home and, Android networking having been thrown together by idiots, it starts using a 192.168.0.0/24 address that <em>somebody else gave it on some other LAN</em> as soon as it wakes up. At which point it starts fighting with some other device on <em>your</em> LAN that acquired that same address legitimately from <em>your</em> DHCP server.
and this is why my network is 10.42.42.0/24
i challenge you to find a non geek that has that network! :-P
-
I can see a dozen networks from my apartment, and not all of them have default names, although nobody's come up with a really clever one.
-
oh, if we're comparing SSIDs...
Visible from my home we have:
- KOS-MOS (mine)
- Adventurous[Name] (Name's)
- Adventurous[Name]-guest (Not Name's different neighbor)
- Belkin3419
- Linksys (unsecured, but also no internet access)
- [Name of local highschool ~3mi away] (with surprisingly good signal strength)
-
Around here is even less exciting for the most part.
- One of them (the one I am on) is actually the name of a weather satellite because my stepdad is a satellite geek
- two TALKTALK-(6 hex digit identifiers)
- one SKY(5 hex digit identifer)
- Other Network (yes someone actually named their network 'Other Network' and it asked me for a password when I tried to join it, it's not Windows messing about or anything)
-
yes someone actually named their network 'Other Network' and it asked me for a password when I tried to join it, it's not Windows messing about or anything
I used to give everyphone I owned the Bluetoooth name of "No devices found"
-
- TELETRAN1
- Lots of defaults.
- Rocknrolla_Network
- RedFlamingo
-
-
There was a KINGSLANDING and KINGSLANDING_Guest at my apartment complex but I think they're gone now. All the rest are "Joneses_wireless" or default names, except mine, which is named after an old dog of my wife's, and used to be "volcanos" because the cable guy asked me for a name and I couldn't think up anything better on the spot.
-
Mine at home is some collection of seemingly random letters and numbers and isn't broadcast publicly.
I never thought I was witty enough for a fun SSID though; I certainly never came up with anything witty.
Sadly because it's a router for family use and stuff, all the family members now use the SSID/password on it because I wasn't smart enough to set up anything more useful at the time so if I change anything I also have to deal with the joy of reconfiguring everyone's devices. Bah. BAH I SAY.
-
i probably need to change my wifi password soon. too many people know it.
of course i gotta hope i still have the SSH key i need to get into the router to turn on the http admin interface (because it no longer autostarts for some reason) to change the password (or do a 30-30-30 on it and enter in all that DHCP info again) ..... BAH! i'll just buy a new shiny rounter *slap*
NO! BAD! BAD @ACCALIA! NO BUY NEW WHEN OLD STILL WORKS! RECONFIGURE NOT BUY NEW!
-
NO BUY NEW WHEN OLD STILL WORKS!
A hammer will fix that objection.
A PHP hammer would even work.
-
- i own the router
- it's an expensive router
- i'[m a little broke rignt now
- NO! BAD @FrostCat! nO COOKIE FOR YOU!
-
A hammer will fix that objection.
A PHP hammer would even work.
How sure are you about that last part?
-
How sure are you about that last part?
Even a PHP hammer, held sideways, will function as a club for the purpose of breaking Accalia's router.
-
That's just what they want you to think.
-
-
Yes, that is indeed the PHP hammer. The point under contention is whether you could beat electronics into submission by using it as a club. My contention is that you could try but most people would simply fail to achieve it, and some of them would fail spectacularly, like ending up smacking themselves in the face with it.
-
check out the image URL
-
Yes, I know Jeff has abused my beloved language before now.
-
The point under contention is whether you could beat electronics into submission by using it as a club.
No, the point was that you could destroy them. I suggested Accalia break her router, not practice kuvaldometriya.
-
Yes, yes... with the PHP hammer this might work if you do it right,
mysql_real_smash_router()
etc. But it probably won't unless you hold it juuuuuuust right.
-
Remember to parameterize your destruction.
-
mysql_real_escape_destruction()
?
-
Ironically, that method is idempotent.
-
-
Both, technically.
-
Well, when I was FTFY I actually first changed it to impotent but that somehow didn't seem to quite fit.
-
Mine at home is some collection of seemingly random letters and numbers and isn't broadcast publicly.
I think that's the wrong way to set up a wifi network. In my experience, all obfuscating your SSID does is cause trouble for legitimate users (MAC filtering likewise). All my wifi networks broadcast names based on the site address, making it obvious who you need to talk to if they're interfering with you.
If your WPA2 key is good and WPS PIN mode is turned off, you have no wifi hijacking problem; if not, you might. Attending to those issues should be all you need to do when setting up a wifi router. Security-by-attempted-obscurity is not defense in depth.
-
i own the router
it's an expensive router
i'[m a little broke rignt nowBefore I knew anything about home networking, I picked a fairly expensive all-in-one ADSL2+, wifi + VoIP router because I couldn't see the sense in paying extra for separate components.
Two years later the VoIP got crackly and flaky. So I added a second-hand Linksys SPA3102 ATA my neighbor was throwing out after deciding to go cellular mobile only, which still works fine.
A few months after that, the wifi started to drop clients and/or reboot the router if more than a handful of clients connected. So I turned off the all-in-one's wifi and added the cheapest Chinese WAP I could find, which still works fine.
Then I found out that could stop the occasional router hangs and reboots I'd been training myself to put up with for months simply by reducing the number of BitTorrent peers allowed to connect at any time. So I added a BeagleBone Black running Debian, along with a VLAN-capable desktop switch to overcome the fact that the BBB only has the one Ethernet port, turned off the all-in-one's router brain and moved my PPPoE endpoint into the BBB. With a 1GHz ARM and 512MiB of RAM, the BBB will handle any routing job I throw at it without breaking a sweat. Tens of thousands of simultaneous NAT sessions? No problem.
And then the mysterious ADSL dropouts I'd been experiencing in wet weather completely stopped when I replaced the all-in-one with the cheapest Chinese ADSL modem I could find. Which still works fine.
So now I've ended up with a little clutch of devices on my phone side-table instead of the one black box, but no single device on that table will cost me anywhere near $100 to replace, and apart from the BeagleBone they're all within a very few clicks of default configuration. The BeagleBone is of course backed up, and because it's just acting as a headless Debian box it won't be tough to replace either.
-
With a 1GHz ARM and 512MiB of RAM
Shouldn't that be gibihertz?
Also, your own link disagrees with you: "The Rev C still has a blistering 1GHz processor and 512MB onboard DDR3 RAM."
You should write a strongly-worded letter to her.
-
Shouldn't that be gibihertz?
What makes you think so?
Also, the board does have the claimed amount of RAM (and more besides). I'm not going to give grief to equipment manufacturers who spec their capacities conservatively.
-
What makes you think so?
Well, assuming a ~2% tolerance, it could actually be 1024MHz .
-
assuming a ~2% tolerance, it could actually be 1024MHz
1GiHz is 1074MHz, not 1024MHz.
-
-
1024 MiHz, yes?
-
Quite so.
-
-