Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Am I missing the point here?' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Am I missing the point here?
Authored by: digitalone on Apr 10, '03 08:33:51PM

Some one needs to fill me in on the exact scheme that your DSL provider uses to get you on the network and not have the damn thing act like one big LAN. (Think multicast packets slamming hundreds of users at a time.) That is the purpose of using internal and external IP addresses like this. What you are attempting to do, from my understanding, is to remove that second fail-safe IP and expose yourself directly to the internet, skipping your DSL providers network (?).

I know from experience that a cable modem has 2 internal addresses, and your machine keeps the WAN IP address. For example, the upstream and downstream CTMS (Cable modem termination system) servers would have an IP address of 10.0.0.1, your modem's first internal address would be 10.0.0.2, its second internal address would be 10.0.1.1 and your WAN IP address would be 64.23.12.1 (dummy IP). Thus method uses your cable modem as a bridge, connecting it to the CTMS transparently, and allowing your to request routable IP addresses, like a 207.xxx.xxx.xxx address for example. This way
A) Internet cannot access certain internal LAN features that a client would activate by default because of the ethernet connection, i.e. multicast packets.
B) You would not be able to easily "see" traffic between others on the same upstream or downstream channels (broadband), and therefore not be able to easily gain access to those users. A real easy way to illustrate this is: windows users wont see the whole neighborhood in network neighborhood, and Mac users wont see the whole neighborhood in the connect to server window.

Every network is different in some way, as administrators segment and subnet as they see fit. Sometimes the schemas don't even really make sense, and numerical IPv4 manipulation (very similar to what I understand you are trying to do) is a savvy way to crack a network or administer it (often the same thing). M company blocks port 80, 8080, and several others by default, so what you are trying to do may not truly give you the results you are looking for. For example, you use this method and see your webpage just fine, someone else wouldn't get there at all.

Bottom line is, if your truly want to see what others would, to really verify connections, you would, IMHO, need to actually try to access your box off-network.





[ Reply to This | # ]