IP address question

Sakebomb

Ive got a cable modem and a belkin router.
If im running a network within the 192.168.0.0 range, would it be possible for someone to connect with an address on a 10.0.0.0 range?

Or the 172.16.0.0 range?

brandotheninjamaster

Sakebomb wrote: »

Ive got a cable modem and a belkin router.
If im running a network within the 192.168.0.0 range, would it be possible for someone to connect with an address on a 10.0.0.0 range?

Or the 172.16.0.0 range?

are these static addresses or DHCP assigned?

Sakebomb

dhcp

mrbernz

No. Not without the use of a VPN or some other routing protocol. A subnet mask tells a device how to work with an IP address. A typical subnet is 255.255.255.0 This subnet says the first three octets are the network address and the fourth is unique for devices. So devices on this network would only be able to talk to other devices with the same network address being 192.168.0 your case. 10.0.0.0 isn't the same network.

Sakebomb

Awesome. Thanks guys.

PirateJon

Yes, you can, and you're probably doing it now. Any router will do NAT and can be configured for forwarding. This is how you can get on the internet or use xbox live when you have a router.

Host1 (10.1.0.1) <--> Router1 IP (12.34.56.78) <----> INTERNETS <----> Router2 IP (34.56.78.90) <--> Host2 (192.168.1.101)

So host1 would have a destination of router2.

mrbernz

PirateJon wrote: »

Yes, you can, and you're probably doing it now. Any router will do NAT and can be configured for forwarding. This is how you can get on the internet or use xbox live when you have a router.

Host1 (10.1.0.1) <--> Router1 IP (12.34.56.78) <----> INTERNETS <----> Router2 IP (34.56.78.90) <--> Host2 (192.168.1.101)

So host1 would have a destination of router2.

That wouldn't work. I am assuming Router1's LAN IP is going to be on the 10. network otherwise Host1 wouldn't be able to talk to it, same goes for Host2. The thing you're missing is ports. Your XBOX live works because of using port 80 which is open by default, network sharing by default is not open. In my original answer I said No, it wouldn't work unless routing was setup.

PirateJon

Routing has to be setup dude, he's on the internet. Port forwarding is trivial.


PROTIP: Routers have at least one IP address per attached network segment. Your home router has (default) two active IP's - the public address assigned by your ISP (12.34.56.78) and the LAN gateway address (192.168.0.1).

Sakebomb

mrbernz wrote: »

PirateJon wrote: »

Yes, you can, and you're probably doing it now. Any router will do NAT and can be configured for forwarding. This is how you can get on the internet or use xbox live when you have a router.

Host1 (10.1.0.1) <--> Router1 IP (12.34.56.78) <----> INTERNETS <----> Router2 IP (34.56.78.90) <--> Host2 (192.168.1.101)

So host1 would have a destination of router2.

That wouldn't work. I am assuming Router1's LAN IP is going to be on the 10. network otherwise Host1 wouldn't be able to talk to it, same goes for Host2. The thing you're missing is ports. Your XBOX live works because of using port 80 which is open by default, network sharing by default is not open. In my original answer I said No, it wouldn't work unless routing was setup.

Ouch...headache...

Uh...so basically that would only work if I had multiple routers on my network?

rfalias

What exactly are you trying to do? Might help

Sakebomb

Ok, so I caught my neighbor leeching my WiFi. After I enabled MAC address filtering on my router, I didnt see him on my DHCP client table anymore, but I was concerned he might be spoofing his MAC, since my network was still laggy.

So I got this program called AngryIP scanner, and had it ping every IP on the network from a range of 192.168.0.0 to 192.168.255.255 (which took a couple of hours). Everything came back all clear.
But im wondering if need to scan the 10.0.0.0 and 172.16.0.0 ranges as well.....

PirateJon

No, no you don't have to.

rfalias

Sakebomb wrote: »

Ok, so I caught my neighbor leeching my WiFi. After I enabled MAC address filtering on my router, I didnt see him on my DHCP client table anymore, but I was concerned he might be spoofing his MAC, since my network was still laggy.

So I got this program called AngryIP scanner, and had it ping every IP on the network from a range of 192.168.0.0 to 192.168.255.255 (which took a couple of hours). Everything came back all clear.
But im wondering if need to scan the 10.0.0.0 and 172.16.0.0 ranges as well.....

Use WPA and call it a day.
That belkin router won't have multiple ranges of private IP's, and anything connected to that router will be what ever range you have dictated. If you have a set amount of devices you can limit the number of IP's it assigns, and just set it to static addressing.

Also, your router should allow you to choose MAC filtering in the sense that it allows only those MAC addresses. If he isn't on your client table, it is unlikely he is connected. But really, take the simple route and just use WPA.

Erandus

Even if he spoofed a MAC address (he would have to know yours or one of another device that connects to your router), your router would still only give him a DCHP assigned address in the 192.168.0.X range that it's configured to assign. Anyone setting their own IP address outside that range would recieve no useful connectivity through your router.

Short answer is: Mac filtering + no strange IP's scanned in AngryIP (great program) = you're in the clear.

If your network is still laggy, reboot your cable modem and your router (unplug and plug them back in) and try installing a program on your PC called NetLimiter. NetLimiter will show you every single proccess and program that's using even a tiny trickle of your bandwidth. If you have any spyware processes or viruses that are sneaking packets in and out, they'll show up in NetLimiter. You can also choose to throttle back any given application or service to only use a set amount of your bandwidth, but you probably don't need to bother with that functionality.

Sakebomb

Erandus wrote: »

Even if he spoofed a MAC address (he would have to know yours or one of another device that connects to your router), your router would still only give him a DCHP assigned address in the 192.168.0.X range that it's configured to assign. Anyone setting their own IP address outside that range would recieve no useful connectivity through your router.

Short answer is: Mac filtering + no strange IP's scanned in AngryIP (great program) = you're in the clear.

If your network is still laggy, reboot your cable modem and your router (unplug and plug them back in) and try installing a program on your PC called NetLimiter. NetLimiter will show you every single proccess and program that's using even a tiny trickle of your bandwidth. If you have any spyware processes or viruses that are sneaking packets in and out, they'll show up in NetLimiter. You can also choose to throttle back any given application or service to only use a set amount of your bandwidth, but you probably don't need to bother with that functionality.

fuckin a!
Muchas gracias