Basic Routing ?

[ABCDEFGH]

Hello,

I'm sure many of these questions have been asked before, however i just can't seem to grasp the principles. Must be the meds :)

I have a Procurve 3400cl and am attempting something very simple. I want to connect a computer to the Internet. I have a Sonicwall plugged into port 1 and the computer in port 2. The Sonicwall interface has an IP of 192.168.0.1 and the both ports on the switch are on VLAN 99. This is a basis for a more complicated setup, however I can't get this to work.

Quick ?, when you create a static route is the gateway created at this point or do you have to specify it earlier?

My joke of a config is below:

Running configuration:

; J4905A Configuration Editor; Created on release #M.10.99

hostname "ProCurve Switch 3400cl-24G" 
web-management ssl 
ip default-gateway 172.16.99.1 
ip routing 
snmp-server community "public" Unrestricted 
vlan 1 
   name "DEFAULT_VLAN" 
   untagged 6,8-24 
   no ip address 
   no untagged 1-5,7 
   exit 
vlan 10 
   name "Servers" 
   untagged 3 
   ip address 172.16.10.1 255.255.255.248 
   exit 
vlan 20 
   name "ServerVMs" 
   untagged 4-5 
   ip address 172.16.20.1 255.255.255.240 
   exit 
vlan 99 
   name "Switch2SW" 
   untagged 1-2,7 
   ip address 172.16.99.2 255.255.255.248 
   exit 
fault-finder bad-driver sensitivity high 
fault-finder bad-transceiver sensitivity high 
fault-finder bad-cable sensitivity high 
fault-finder too-long-cable sensitivity high 
fault-finder over-bandwidth sensitivity high 
fault-finder broadcast-storm sensitivity high 
fault-finder loss-of-link sensitivity high 
fault-finder duplex-mismatch-HDx sensitivity high 
fault-finder duplex-mismatch-FDx sensitivity high 
ip route 192.168.0.0 255.255.255.248 172.16.99.1 
no stack 
primary-vlan 99 
password manager
password operator

Any advice is greatly appreciated!

[Chrisd131313]

Hi ABCDEFGH,

You have correctly enabled ip routing, but the firewall port isn't a memeber of a VLAN with a correct gateway IP.

All connected subnets will route automatically when ip routing is enabled so I would suggest that you plug your firewall in to a port which is a member of a VLAN with the same subnet as the firewall (192.168.0.2/24 as an example). This will then tell the switch where it needs to route traffic to reach 192.168.0.1.

So a device on 172.16.20.2 will have 172.16.20.1 as it's DG the swirch will then have a default route of 0.0.0.0 0.0.0.0 192.168.0.1 set, this will then tell teh switch to send all traffic destined for anything that is not in its routing table, or directly connected to send it on to the firewall @ 192.168.0.1

So for you to get things working, remove the static route you entered, add in the default route as shown above (the default gateway you added is only for switch management access, not for ip routing) and then move the firewall over to its own port in a new VLAN with a corresponding IP address.

That should get you up and running.

HTH