Can I set up my network so I can talk to ANY IP address on the wiredswitch?

I have a FIOS router followed by an unmanaged switch.
The network runs at 192.168.1.x and life is good.

BUT

When I get a new IP toy, like a surveillance camera,
it has a default configuration address outside
my IP range:
192.168.0.253
10.0.0.x
etc.

I have to unplug the computer from the switch and into
the toy. Then reconfigure the computer IP address to
configure the toy to 192.168.1.x
Then reverse all the configurations.
Conceptually easy, but takes 5 minutes or more for the
network to reconfigure itself twice...and crawling
around under the desk to unplug stuff.
And if I screwed up the toy configuration, I can't access
it, it gets reset and the process starts over.

Is there a configuration or a utility that will let me
talk to 192.168.0.253 or 10.0.0.x or ANY local address
to access the toy's web configuration interface
without losing my internet gateway
on 192.168.1.1?
Doesn't have to be high performance.

I'm unwilling to mess with the existing router because I
also have a wireless bridge running thru it.

I also have an additional router that serves DHCP on 192.168.0.x
and double-NATs it thru 192.168.1.1, but that doesn't seem
to help my situation.

I have routers with tomato and DDWRT, but have no idea if that
will help. I don't think I can do a static route, because I don't
know what it might be until I do it. Reconfiguring the routes
would take as much time as what I'm doing now.

I just put a gigabit card into my test computer, so the onboard
ethernet is available if it would help. I have no experience
trying to access two subnets off the same computer.

Would a browser proxy do anything useful here?

Ideas?

On Mon, 26 Oct 2015 07:58:29 -0700, mike wrote:

I have a FIOS router followed by an unmanaged switch.
The network runs at 192.168.1.x and life is good.

BUT

When I get a new IP toy, like a surveillance camera,
it has a default configuration address outside
my IP range:
192.168.0.253
10.0.0.x
etc.

If your main PC gets its IP address via DHCP, consider changing to a static
IP that's outside of the configured DHCP scope. Once you change to a static
IP, you then have the capability to 'stack' additional IP addresses on your
existing NIC. Add IP addresses for the networks that you think you'll need.

You'll obviously need to add an IP address in the 192.168.1.0/24 network
because that's your main LAN, but you could then add an address in the
10.0.0.0/8 subnet and the 192.168.0.0/16 subnet. Note that the latter is a
superset of 192.168.1.0/24, but I don't see a problem with that. The former
covers everything that starts with 10.x.x.x.

To stack IP's on a NIC, open Network and Sharing Center. On the left, click
on Change Adapter Settings. Find your adapter, right click on it and select
Properties. Highlight Internet Protocol Version 4 and select Properties.
Click on Advanced. On the next screen, the first section is IP Addresses.
Add an IP address for each desired network, along with the appropriate
network mask. OK your way out. No need to reboot.

Why it works: When you try to access any IP address, your network stack
compares the destination against each of your configured IPs, using your
network mask as the basis for comparison. If there's no match, it sends the
request in care of your gateway IP. The gateway accepts the traffic and
sends it on its way. However, if there is a match, then your PC sends the
request directly to the other PC, using ARP to determine the hardware
address.


--

Char Jackson

On Mon, 26 Oct 2015 07:58:29 -0700, mike wrote:

I have a FIOS router followed by an unmanaged switch.
The network runs at 192.168.1.x and life is good.

BUT

When I get a new IP toy, like a surveillance camera,
it has a default configuration address outside
my IP range:
192.168.0.253
10.0.0.x
etc.

You should be able to access the camera setup by entering
192.168.0.252 into a web browser.

--
Wildman GNU/Linux user #557453
The cow died so I don't need your bull!

On Mon, 26 Oct 2015 13:40:25 -0500, Wildman wrote:

On Mon, 26 Oct 2015 07:58:29 -0700, mike wrote:

I have a FIOS router followed by an unmanaged switch.
The network runs at 192.168.1.x and life is good.

BUT

When I get a new IP toy, like a surveillance camera,
it has a default configuration address outside
my IP range:
192.168.0.253
10.0.0.x
etc.

You should be able to access the camera setup by entering
192.168.0.252 into a web browser.

His router is quite likely handing out a 192.168.1.0/24 address, so
192.168.0.x will be out of range. He can *change* his local IP, which he
said he'd rather not do, or he can *add* an IP in the new subnet. I provided
info previously on how he can do that.

--

Char Jackson

On 10/26/2015 9:10 AM, Char Jackson wrote:
On Mon, 26 Oct 2015 07:58:29 -0700, mike wrote:

I have a FIOS router followed by an unmanaged switch.
The network runs at 192.168.1.x and life is good.

BUT

When I get a new IP toy, like a surveillance camera,
it has a default configuration address outside
my IP range:
192.168.0.253
10.0.0.x
etc.

If your main PC gets its IP address via DHCP, consider changing to a static
IP that's outside of the configured DHCP scope.

Can you clarify the above?
If my router is serving DHCP from 192.168.1.2 to 192.168.1.50,
is 192.168.1.69 "outside the scope"? Or do I use something like
192.168.3.3? And a subnet mask other than 255.255.255.0?
I don't really understand the relationship between "scope" and
"subnet" in this context.

Sounds like this address a "placeholder" that enables the stacking?

Once you change to a static
IP, you then have the capability to 'stack' additional IP addresses on your
existing NIC. Add IP addresses for the networks that you think you'll need.

You'll obviously need to add an IP address in the 192.168.1.0/24 network
because that's your main LAN, but you could then add an address in the
10.0.0.0/8 subnet and the 192.168.0.0/16 subnet. Note that the latter is a
superset of 192.168.1.0/24, but I don't see a problem with that. The former
covers everything that starts with 10.x.x.x.

I'll have to look up the relationship between 192.168.0.0/16 and the actual
subnet mask, but I think I have that saved somewhere.

To stack IP's on a NIC, open Network and Sharing Center. On the left, click
on Change Adapter Settings. Find your adapter, right click on it and select
Properties. Highlight Internet Protocol Version 4 and select Properties.
Click on Advanced. On the next screen, the first section is IP Addresses.
Add an IP address for each desired network, along with the appropriate
network mask. OK your way out. No need to reboot.

Why it works: When you try to access any IP address, your network stack
compares the destination against each of your configured IPs, using your
network mask as the basis for comparison. If there's no match, it sends the
request in care of your gateway IP. The gateway accepts the traffic and
sends it on its way. However, if there is a match, then your PC sends the
request directly to the other PC, using ARP to determine the hardware
address.


thanks,
At first read, that looks like exactly what I want.
The step by step instructions are appreciated.
The devil is in the details...I'll come back if I get lost.

I have a vague notion on what happens
in simple situations, but don't know what search keywords
to use for more complex stuff. I googled my ass off and got
nowhere.
Is there an overview that explains, in simple terms,
how routing works...with enough useful keywords to
get started with google?

If your cam and main router or secondary router have WPS then
Go into the router and enable WPS (temporarily)

Push the router WPS button and the cam WPS button and they should talk
to each other and agree on an IP address.

Then go back to the router and turnoff WPS if you do not trust it like
some here feel.

I have a load of IP cams, main router, switches and second WiFi router
with Dynamic Host Configuration Protocol (DHCP) off that all now play
together very well. Either router will WPS to any of my WiFi cams.

Main router is 2.4GHz WiFi
Second router is 2.4GHz and 5GHz.
Secondary router is used as a CAT5 switch and WiFi interface.
So some devices are hardwired CAT5 and some are via WiFi.
That is for both routers.

I previously posted info on my setup so others might benefit.

Hope this helps.

--

--
No signature

--- news://freenews.netfront.net/ - complaints: ---

On Mon, 26 Oct 2015 14:28:56 -0700, mike wrote:

On 10/26/2015 9:10 AM, Char Jackson wrote:
On Mon, 26 Oct 2015 07:58:29 -0700, mike wrote:

I have a FIOS router followed by an unmanaged switch.
The network runs at 192.168.1.x and life is good.

BUT

When I get a new IP toy, like a surveillance camera,
it has a default configuration address outside
my IP range:
192.168.0.253
10.0.0.x
etc.

If your main PC gets its IP address via DHCP, consider changing to a static
IP that's outside of the configured DHCP scope.

Can you clarify the above?
If my router is serving DHCP from 192.168.1.2 to 192.168.1.50,
is 192.168.1.69 "outside the scope"?

Yes, so that would be perfect. Your subnet almost certainly has a mask of
/24, (if in doubt, check your router) which can also be written as
255.255.255.0, which means that the network is described by the first three
octets, or groups, of numbers: "192.168.1". So your network is 192.168.1.0,
(.0 refers to the network itself, and isn't generally usable for anything
else), with usable addresses from 192.168.1.1 to 192.168.1.254. You're using
192.168.1.1 for the router and you've reserved the range from 192.168.1.2 to
192.168.1.50 for DHCP address assignments, which leaves the entire range
from 192.168.1.51 to 192.168.1.254 available for your use.

Tip: try to ping an IP address first before you manually assign it. The
pings should time out. If one or more responses are received, it means
another PC or network device is already using that address and you'll need
to choose another.

Note that when you assign an IP address yourself, you become responsible for
making sure you don't assign the same IP anywhere else. DHCP takes care of
that for you, but DHCP won't allow you to do what I suggested, thus the
manual IP assignment that I suggested.


Or do I use something like 192.168.3.3?

With a subnet mask of /24 (255.255.255.0) that address would be in an
entirely different network.


And a subnet mask other than 255.255.255.0?

For your primary LAN address, I would stay with 255.255.255.0 (same as /24).


I don't really understand the relationship between "scope" and
"subnet" in this context.

"DHCP scope" just refers to the range of possible DHCP-assigned addresses.
In your case, that's the range from 192.168.1.2 to 192.168.1.50.

Subnet, or network, refers to a group of IP addresses that are bounded by a
logical OR between the IP address and the subnet mask, AKA netmask, AKA
mask. Put another way, you could say that the network is 'described' by its
subnet mask.


Sounds like this address a "placeholder" that enables the stacking?

In a way, yes, but it primarily becomes your actual LAN IP address. It
happens to enable IP stacking as a bonus. If you set the NIC to request its
address via DHCP then you're limited to a single IP address. However, if you
manually assign your IP address, then you can assign multiple IP addresses.
You're no longer limited to just one.

I didn't mention it before, but for the additional IP's that you enter, you
only need to enter a netmask for each. Don't try to enter gateway IP's for
those. You want just one gateway - your existing router at 192.168.1.1.


Once you change to a static
IP, you then have the capability to 'stack' additional IP addresses on your
existing NIC. Add IP addresses for the networks that you think you'll need.

You'll obviously need to add an IP address in the 192.168.1.0/24 network
because that's your main LAN, but you could then add an address in the
10.0.0.0/8 subnet and the 192.168.0.0/16 subnet. Note that the latter is a
superset of 192.168.1.0/24, but I don't see a problem with that. The former
covers everything that starts with 10.x.x.x.

I'll have to look up the relationship between 192.168.0.0/16 and the actual
subnet mask, but I think I have that saved somewhere.

Given 192.168.0.0 and a subnet mask of 255.255.0.0, every IP address that
starts with "192.168" would be considered local. Attempts to reach any of
those addresses would result in an ARP request (broadcast) rather than a
packet addressed to your gateway. That's actually OK, since 192.168.x.x
addresses aren't routable on the Internet anyway.


I have a vague notion on what happens
in simple situations, but don't know what search keywords
to use for more complex stuff. I googled my ass off and got
nowhere.
Is there an overview that explains, in simple terms,
how routing works...with enough useful keywords to
get started with google?

I think the problem is that there is so much info available that it's hard
to find exactly what you're probably looking for. One of the keywords in
your case might be "dual-homed" or "multi-homed", although a lot of those
article will incorrectly assume that you have multiple NICs. You're
essentially multi-homing your PC with a single NIC.

--

Char Jackson

On 10/26/2015 5:12 PM, Char Jackson wrote:
On Mon, 26 Oct 2015 14:28:56 -0700, mike wrote:

On 10/26/2015 9:10 AM, Char Jackson wrote:
On Mon, 26 Oct 2015 07:58:29 -0700, mike wrote:

I have a FIOS router followed by an unmanaged switch.
The network runs at 192.168.1.x and life is good.

BUT

When I get a new IP toy, like a surveillance camera,
it has a default configuration address outside
my IP range:
192.168.0.253
10.0.0.x
etc.

If your main PC gets its IP address via DHCP, consider changing to a static
IP that's outside of the configured DHCP scope.

Can you clarify the above?
If my router is serving DHCP from 192.168.1.2 to 192.168.1.50,
is 192.168.1.69 "outside the scope"?

Yes, so that would be perfect. Your subnet almost certainly has a mask of
/24, (if in doubt, check your router) which can also be written as
255.255.255.0, which means that the network is described by the first three
octets, or groups, of numbers: "192.168.1". So your network is 192.168.1.0,
(.0 refers to the network itself, and isn't generally usable for anything
else), with usable addresses from 192.168.1.1 to 192.168.1.254. You're using
192.168.1.1 for the router and you've reserved the range from 192.168.1.2 to
192.168.1.50 for DHCP address assignments, which leaves the entire range
from 192.168.1.51 to 192.168.1.254 available for your use.

Tip: try to ping an IP address first before you manually assign it. The
pings should time out. If one or more responses are received, it means
another PC or network device is already using that address and you'll need
to choose another.

Note that when you assign an IP address yourself, you become responsible for
making sure you don't assign the same IP anywhere else. DHCP takes care of
that for you, but DHCP won't allow you to do what I suggested, thus the
manual IP assignment that I suggested.


Or do I use something like 192.168.3.3?

With a subnet mask of /24 (255.255.255.0) that address would be in an
entirely different network.


And a subnet mask other than 255.255.255.0?

For your primary LAN address, I would stay with 255.255.255.0 (same as /24).


I don't really understand the relationship between "scope" and
"subnet" in this context.

"DHCP scope" just refers to the range of possible DHCP-assigned addresses.
In your case, that's the range from 192.168.1.2 to 192.168.1.50.

Subnet, or network, refers to a group of IP addresses that are bounded by a
logical OR between the IP address and the subnet mask, AKA netmask, AKA
mask. Put another way, you could say that the network is 'described' by its
subnet mask.


Sounds like this address a "placeholder" that enables the stacking?

In a way, yes, but it primarily becomes your actual LAN IP address. It
happens to enable IP stacking as a bonus. If you set the NIC to request its
address via DHCP then you're limited to a single IP address. However, if you
manually assign your IP address, then you can assign multiple IP addresses.
You're no longer limited to just one.

I didn't mention it before, but for the additional IP's that you enter, you
only need to enter a netmask for each. Don't try to enter gateway IP's for
those. You want just one gateway - your existing router at 192.168.1.1.


Once you change to a static
IP, you then have the capability to 'stack' additional IP addresses on your
existing NIC. Add IP addresses for the networks that you think you'll need.

You'll obviously need to add an IP address in the 192.168.1.0/24 network
because that's your main LAN, but you could then add an address in the
10.0.0.0/8 subnet and the 192.168.0.0/16 subnet. Note that the latter is a
superset of 192.168.1.0/24, but I don't see a problem with that. The former
covers everything that starts with 10.x.x.x.

I'll have to look up the relationship between 192.168.0.0/16 and the actual
subnet mask, but I think I have that saved somewhere.

Given 192.168.0.0 and a subnet mask of 255.255.0.0, every IP address that
starts with "192.168" would be considered local. Attempts to reach any of
those addresses would result in an ARP request (broadcast) rather than a
packet addressed to your gateway. That's actually OK, since 192.168.x.x
addresses aren't routable on the Internet anyway.


I have a vague notion on what happens
in simple situations, but don't know what search keywords
to use for more complex stuff. I googled my ass off and got
nowhere.
Is there an overview that explains, in simple terms,
how routing works...with enough useful keywords to
get started with google?

I think the problem is that there is so much info available that it's hard
to find exactly what you're probably looking for. One of the keywords in
your case might be "dual-homed" or "multi-homed", although a lot of those
article will incorrectly assume that you have multiple NICs. You're
essentially multi-homing your PC with a single NIC.

Thanks for the clarification.
I use DHCP on everything, then use address reservation in the router
to give me stable IP addresses by machine. I got into that habit so I
could move
a laptop from my network to a hotspot and have it all just work.
The numbers I used before were made-up to simplify.
I actually have the whole 192.168.1.x range served by DHCP.
the subject machine has address reservation for 192.168.1.10.

If I set the fixed IP address to 192.168.1.10, it won't ask for
DHCP and the router won't try to assign ...10 to any other MAC address.
That would make it easier...I have plugin drives with multiple
operating systems that always get the same IP and stuff
that depends on the address, like VNC
works the same on all.
If that won't work, I'll have to swizzle a few numbers multiple
places, but shouldn't be difficult.

Haven't tried any of this yet. Got sidetracked by rain gutter cleaning. ;-)
Thanks
mike

On 10/26/2015 5:12 PM, Char Jackson wrote:

I think the problem is that there is so much info available that it's hard
to find exactly what you're probably looking for. One of the keywords in
your case might be "dual-homed" or "multi-homed", although a lot of those
article will incorrectly assume that you have multiple NICs. You're
essentially multi-homing your PC with a single NIC.

Once I got my head around the different notations, it got really simple.
And it works!!!
Thanks very much.

What we need is a utility that scans the local network and lists
all the devices it finds. Put a check in the box for each one
you want to talk with and it magically fixes up whatever it takes
to make it happen.

mike

On Tue, 27 Oct 2015 04:07:52 -0700, mike wrote:

On 10/26/2015 5:12 PM, Char Jackson wrote:

I think the problem is that there is so much info available that it's hard
to find exactly what you're probably looking for. One of the keywords in
your case might be "dual-homed" or "multi-homed", although a lot of those
article will incorrectly assume that you have multiple NICs. You're
essentially multi-homing your PC with a single NIC.

Once I got my head around the different notations, it got really simple.
And it works!!!

I knew it would. :-) I've been doing it here since at least 2006.

Thanks very much.

You're welcome. Glad to help.

What we need is a utility that scans the local network and lists
all the devices it finds. Put a check in the box for each one
you want to talk with and it magically fixes up whatever it takes
to make it happen.

I don't know of a tool like that, but I don't see any reason why it wouldn't
work.

--

Char Jackson