Cenk, sorry for the delay. As you suggested, I added a route to the trusted interface on the firewall (see attached), but the devices on the 192.168.2.0 network still cannot access the internet, but I believe it is DNS related.
If I put a PC on the ..2.0 network with the following static IP config, I can ping an external IP such as 69.63.187.19 (facebook), but can't resolve it by name.
IP address = 192.168.2.x
Mask = 255.255.255.0
Gateway = 192.168.1.254
DNS Server = 192.168.2.245
The DNS/DHCP server has two NICs. One NIC services the 1.0 requests (port 19 on switch), and the other services the 2.0 net requests (port 22 on switch)
What am I doing wrong? Below is the switch config again:
------ %< ---------
hostname "2610-24-PWR"
interface 19
name "VM Network"
speed-duplex 100-full
exit
interface 21
name "Firewall-GW"
exit
interface 22
name "DHCP-Voice"
speed-duplex 100-full
exit
ip default-gateway 192.168.1.254
ip routing
snmp-server community "public" Unrestricted
vlan 1
name "Default_Data"
untagged 1-21,25-28
ip address 192.168.1.253 255.255.255.0
no untagged 22-24
exit
vlan 2
name "Voice"
untagged 22-24
ip address 192.168.2.253 255.255.255.0
ip helper-address 192.168.2.245
tagged 1-21
voice
exit
ip route 0.0.0.0 0.0.0.0 192.168.1.254
power pre-std-detect
password manager