Live data from Hacker News

A Shark on the Network

blog.nodenexus.com

51–54 of 54 posts

Re: A Shark on the Network

#51
post #49

Earlier quoted context omitted.

People forget this. You can make your wireless AP as secure as you want, but if we're plugged into the same node with our cable modems, you can just run a regular packet sniffer with ARP poisoning and see all the traffic to your neighbors. Not sure if that works with DSL connections or not.

Mostly not possible. DSL has multiple deployment modes PPP (over Ethernet or ATM), Bridged, and routed-bridge encapsulation (RBE). The upstream router at the ISP is usually connected to an ATM or Frame Relay link, where they create virtual circuits to the DSLAM for each customer/modem (DSLAM is the last "network" device between your DSL modem and the telco -- it's the thing doing the Analog/Digital conversion from AT…

Sadly a bunch of modems have the admin panel accesible from the WAN side, probably with the factory password or something the ISP sets to all same devices.

You still need to known your neighbors' public ip address, but the problem may be significantly reduced: "hey want to check my cool app?" Boom!

Re: A Shark on the Network

#52
post #49

Earlier quoted context omitted.

People forget this. You can make your wireless AP as secure as you want, but if we're plugged into the same node with our cable modems, you can just run a regular packet sniffer with ARP poisoning and see all the traffic to your neighbors. Not sure if that works with DSL connections or not.

Mostly not possible. DSL has multiple deployment modes PPP (over Ethernet or ATM), Bridged, and routed-bridge encapsulation (RBE). The upstream router at the ISP is usually connected to an ATM or Frame Relay link, where they create virtual circuits to the DSLAM for each customer/modem (DSLAM is the last "network" device between your DSL modem and the telco -- it's the thing doing the Analog/Digital conversion from AT…

[deleted]

Re: A Shark on the Network

#53
post #24

Can somebody explain all the brown on that HostShark circle gif? Looks like >90% of the requests are going to xo.net, an ISP. http://blog.nodenexus.com/assets/img/hostshark.gif

DNS?

Maybe that's part of it, but it's My best guess is VPN. Maybe that's how they link Princeton campuses together or something.
Post reply on HN