Mindflayer wrote:The latest SANS suggestion is actually to broadcast your SSID. Just lock it down using WPA/WPA2. If you want to be even more paranoid, use WPA2 and MAC filtering.
Indeed...also the DHKY must be synchronized with the TGMB...otherwise your rig will suffer PPR...
No more catchy slogans for me...I am simply fed up...4...four...4...2+2...
Taggure wrote:I know it is a pain but from a security point you need to not broadcast your SSID (you should already know it and your password) and lock your network down by authorized MAC address. I know this latter point can be a pain but you will be happy once you know what is on your network. Then you take away the Freeloading Neighbor possibility.
My guess on your problem is very colse the Gunderwoods suggestions so I will not repeat them, but I do recommend that you lock your system down. I agree that a Bios update may be needed.
I really doubt my neighbors are stealing the WiFi. I have WPA enabled but beyond that it just becomes to much of a hassle. Disabling the SSID is more or less a false sense of security, a free sniffer can find it easy. But it's definitely a laptop issue. It happened a couple days ago so I power cycled the laptop only and it came back up with WiFi normal. I'll check out the power setting.
“Socialism is a philosophy of failure, the creed of ignorance, and the gospel of envy, its inherent virtue is the equal sharing of misery.”
-Winston Churchill
Taggure wrote:I know it is a pain but from a security point you need to not broadcast your SSID (you should already know it and your password) and lock your network down by authorized MAC address. I know this latter point can be a pain but you will be happy once you know what is on your network. Then you take away the Freeloading Neighbor possibility.
My guess on your problem is very colse the Gunderwoods suggestions so I will not repeat them, but I do recommend that you lock your system down. I agree that a Bios update may be needed.
Mindflayer wrote:The latest SANS suggestion is actually to broadcast your SSID. Just lock it down using WPA/WPA2. If you want to be even more paranoid, use WPA2 and MAC filtering.
Ya, your SSID is broadcast unencrypted in the packet anyways. Turning it off doesn't do anything for security. Same with MAC address. Likely anyone who has the tools to break your WiFi, SSID and MAC won't do much if anything. I still lock mine down that way out of habit.
Use WPA2 with a good (random password is best...your devices are going to remember it so you won't need too until its time to add another device. I just use that as an opertunity to rekey everything); a lot of the WPA implementations aren't so great. IIRC there are all kinds of side channel/information leakage attacks on WPA. At this point, WEP is practically pointless.
sudo modprobe commonsense
FATAL: Module commonsense not found.
Besides making sure your router is secure so no one is mooching off your bandwidth you may want to change the channel you broadcast on. If there are several routers in the area broadcasting on the same channel I have seen that cause problems. There are some freeware scanners for iPhone, Mac and windows that can search out and identify near routers and their channels. Change your channel to one not being used or being used least.
Jakeiscrazy wrote:But it's definitely a laptop issue. It happened a couple days ago so I power cycled the laptop only and it came back up with WiFi normal. I'll check out the power setting.
Check all your configs, but it sounded like you had already done that in the OP? Also, the fact that a reboot doesn't fix it, but a complete removal of power does indicates it is not a simple OS config issue. A typical reboot should reset something like that and you indicated it doesn't. The only thing that doesn't get completely reset upon a reboot, but does upon a complete power removal is some hardware/firmware.
sudo modprobe commonsense
FATAL: Module commonsense not found.
Jakeiscrazy wrote:But it's definitely a laptop issue. It happened a couple days ago so I power cycled the laptop only and it came back up with WiFi normal. I'll check out the power setting.
Check all your configs, but it sounded like you had already done that in the OP? Also, the fact that a reboot doesn't fix it, but a complete removal of power does indicates it is not a simple OS config issue. A typical reboot should reset something like that and you indicated it doesn't. The only thing that doesn't get completely reset upon a reboot, but does upon a complete power removal is some hardware/firmware.
Wouldn't the fact I tried a USB adapter WiFi rule that out? Or does that use my network card as well?
“Socialism is a philosophy of failure, the creed of ignorance, and the gospel of envy, its inherent virtue is the equal sharing of misery.”
-Winston Churchill
Jakeiscrazy wrote:But it's definitely a laptop issue. It happened a couple days ago so I power cycled the laptop only and it came back up with WiFi normal. I'll check out the power setting.
Check all your configs, but it sounded like you had already done that in the OP? Also, the fact that a reboot doesn't fix it, but a complete removal of power does indicates it is not a simple OS config issue. A typical reboot should reset something like that and you indicated it doesn't. The only thing that doesn't get completely reset upon a reboot, but does upon a complete power removal is some hardware/firmware.
Wouldn't the fact I tried a USB adapter WiFi rule that out? Or does that use my network card as well?
No, it doesn't use your network card, but the answer is maybe. Most of those functions are really handled by the chipset, which is really a small I/O processor. IIRC, there was a BlackHat presentation a year or two ago which talked about basically rooting the BIOS and executing your code on the microprocessor which resides in the chipset. Once done, in theory its not possible for your OS to detect because it completely trusts the hardware/firmware subsystem.
Long story short, that doesn't rule it out. That is a 780/SB700, which IIRC has the ethernet coupled to it through PCI-E. The whole MB is run by the firmware which is read in and processed on the the SB.
sudo modprobe commonsense
FATAL: Module commonsense not found.
