• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Note to self - don't bring up a workgroup bridge

packet loop! Years ago I had some one who would always bridge his wireless to the ethernet port on his laptop because "that is how it is supposed to work 'stupid IT guy'" (This is a classic small/medium office, not willing to pay for real gear nor willing to force policies / have a second network (vlans etc) for the AP's to avoid this issue etc) He would then dock his laptop and his wireless card would auto connect to the AP. DHCP request sent looped through the AP's and in 5-10 minutes the DHCP server would be full of "BAD_ADDRESS" IPs. Then his laptop would act as the conduit for the ensuring packet storm until the AP crashed.

I never want to go back to that level. Businesses with 80+ people should never be running on what is basically home network gear.
 
imagoon wins. Technically it is a bridge loop (layer2). Frames will just build up, loop around forever, and within seconds the network is completely done, unusable. In this case the switches were running bpduguard (the switch port shuts down if it receives a BPDU) so no bridge loop occurred, without it there would be.

So what really happened is the WGB associated with an ap, that APs port was shut down. Then it moved to another AP, that port shut down, etc.
 
I had something similar to that, a guy brought his own network switch into his office at my old job and saw an ethernet cable just lying around ended up plugging both sides of the cable into the switch, then left for the day. Within just a few minutes the network crashed. That was fun.
 
Originally posted by: kevnich2
I had something similar to that, a guy brought his own network switch into his office at my old job and saw an ethernet cable just lying around ended up plugging both sides of the cable into the switch, then left for the day. Within just a few minutes the network crashed. That was fun.
Click to expand...

If somebody plugs something in that isn't approved then it needs to be smashed into small bits in front of them and everybody else. Plugging in any active network device gets double punishment and pain.
 
Originally posted by: kevnich2
I had something similar to that, a guy brought his own network switch into his office at my old job and saw an ethernet cable just lying around ended up plugging both sides of the cable into the switch, then left for the day. Within just a few minutes the network crashed. That was fun.
Click to expand...

WOW. Take the loop that he formed and choke him with it. Even idiots know that 1 wire going from and back to a device is pointless.
 
At least you have the proper gear installed to only take the AP's out due to that. I hated having to fix the issue I listed above because the end user felt he was smarter than all IT staff. It was always an argument to get on the PC to disable the bridge. At the time I was a contractor so it automatically put me at a disadvantage trying to truly fix it. DHCP would fail due to full tables, all other computers that booted after this would get a DHCP NAK and then would fall offline because the scope was "full." Clear out dns and then have to tell people to reboot the PC's. All so we could do it again later that week when the guy bridged the connection again.
 
"At least you have the proper gear installed to only take the AP's out due to that. I hated having to fix the issue I listed above because the end user felt he was smarter than all IT staff. It was always an argument to get on the PC to disable the bridge. At the time I was a contractor so it automatically put me at a disadvantage trying to truly fix it. DHCP would fail due to full tables, all other computers that booted after this would get a DHCP NAK and then would fall offline because the scope was "full." Clear out dns and then have to tell people to reboot the PC's. All so we could do it again later that week when the guy bridged the connection again."

Fix by banning his MAC at the switch level, or disabling the port. When the user complains smash his laptop.
 
Originally posted by: spidey07
Originally posted by: bobdole369
YaY packet storm!!!!

No managed switches with this network I take it?
Click to expand...

Read the thread. You also get a cookie. 🙂

:cookie:

Double cookie for smashing dumb shit.
:cookie::cookie:
Click to expand...

Last year I got a call that ended up being a storm. I could get into the gateway/proxy server, but nobody could get out. Turns out the physical security at this private school is not too keen, and somebody had looped the two dell switches not twice, but three times🙂
 
Some consumer bridges will actually detect this condition on bootup and change to AP mode, however if you just plug it to the AP that it's wirelessly bridged to without re-booting, then you'd have the same problem.
 
If you want some fun set your wireless nic's IP the same as the gateway IP of a wireless network near you.

Instant entire network down. It's scary actually.
 
Originally posted by: RedSquirrel
If you want some fun set your wireless nic's IP the same as the gateway IP of a wireless network near you.

Instant entire network down. It's scary actually.
Click to expand...

ARP battle. As long as you answer first you can then transparently proxy all their connections and do a nice man in the middle to get all their stuffs. Sending out gratuitous ARPs also helps to convice everybody that you are indeed the gateway. Works on any network.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top