Beginner's guide to adding an IP range

[paulgear]

Some minor points:

• The Sonicwall already has a route to 192.168.10.246 because it has address 192.168.10.254/24.  There is only one route that needs to be added: to 192.168.20.0/24 via 192.168.10.246.
• My guess is that your existing 192.168.10.0/24 hosts talk more to Internet hosts than they will to 192.168.20.0/24 hosts, so i would probably leave them with a default gateway to the Sonicwall.  Either way will work as long as the Sonicwall route above is added, and the ProCurve has a default route to the Sonicwall.
• The 192.168.10.0/24 hosts don't need a route to other 192.168.10.0/24 hosts - they already have it by virtue of being on the same subnet, and they don't need a route to 192.168.20.0/24 if the Sonicwall has the correct route.

So the way i would do it is:

• Add a route on 192.168.10.254 to 192.168.20.0/24 via 192.168.10.246.
• Add a new IP address 192.168.20.246/24 on the switch, add a default route to the Sonicwall (make sure you use "ip route" not "ip default-gateway"), and enable routing.
• Set default gateway for machines in new range to 192.168.20.246.  Leave default gateway on existing systems as-is.
• Plan to expand your managed switch environment ASAP so that you can put 192.168.10.0/24 and 192.168.20.0/24 on different VLANs (and probably add other VLANs as well).

[TheSecondCity]

Thanks again for your assistance, Paul.  While my implementation will be far from perfect, it will at least be usable.