Thanks, I'll give that a go if I get time, I have been stuffing about with this for a couple of days now though and may just stick with the only one that runs without recompiling the whole thing from the ground up.Quote:
Originally Posted by Arthur
Printable View
Thanks, I'll give that a go if I get time, I have been stuffing about with this for a couple of days now though and may just stick with the only one that runs without recompiling the whole thing from the ground up.Quote:
Originally Posted by Arthur
@FN_GM Would you still like to know how to add a route on your switch?
Please Ric
Is it this? - ip route 172.20.2.0 255.255.255.0 <ip of destination>
Thanks
@FN-GM To help, we need to know the subnets of each VLAN (including the subnet that the smoothie is on). IP addresses might help too.
Have you seen the attached image on post 1?
You mean the one that doesn't say whether the two IPs are for the clients or the switch and it has no subnet/IPs for the network the Smoothie is on?Quote:
Originally Posted by FN-GM
Oh so it doesnt. Smoothie is on 192.168.0.1 255.255.255.0 the siwtch itself doesnt have an IP yet.
The switch will need to be on a vlan with an ip in the 192.168.0.0/24 subnet.
and
ip route 0.0.0.0 0.0.0.0 192.168.0.1
The smoothwall will need routes for the other vlans with a GW set as the IP of the switch.
Yes but that does every VLAN. I only need it on certain onesQuote:
Originally Posted by twin--turbo
I think it is worth pointing out that nobody has given you the full config... we all seem to be giving you enough information to have a bash (maybe we are evil or maybe we are trying to help you learn).
The thinking is...
You need a route to VLAN A on the switch
You need a route to VLAN B on the switch
You need a default route on the switch
You then set the switch as your gateway on the clients and maybe add static routes on your Smoothie.
But you set the default gateway on the clients as the vlan interface? According to Cisco anyway.
If i do this and add the below static routes it should work?
ip route 172.20.1.0 255.255.255.0 192.168.0.1
ip route 172.20.2.0 255.255.255.0 192.168.0.1
You only need one explicit route on the cisco and that is the default one.
Each client has a DG which is the IP of the VLAN interface IP for it's subnet.
Rob
I know you only need one but i dont want that. I am going to have another VLAN pointing to a different firewall. I want to specify the firewall for each vlan.
So will what i posted above work with that?
To do what?Quote:
Originally Posted by FN-GM
That would tell the cisco that those two networks are routed by the smoothie to somewhere else.
in brief.....
Cisco
------
vlan 1
name smoothwall_network
vlan 2
name twenty_one_network
vlan3
name twenty_two_network
interface vlan 1
description connection-to-smoothwall
ip address 192.168.0.2 255.255.255.0
ip helper-address (ip of dhcp server (must be on one of the vlans)
no shut
interface vlan 2
description twenty-one-network
ip address 172.20.1.1 255.255.255.0
ip helper-address (ip of dhcp server (must be on one of the vlans)
no shut
interface vlan 3
description twenty-two-network
ip address 172.20.2.1 255.255.255.0
ip helper-address (ip of dhcp server (must be on one of the vlans)
no shut
int range g0/1-10
description smoothwall vlan
switchport mode access
switchport access vlan 1
no shut
int range g0/11-20
description 20-1 vlan
switchport mode access
switchport access vlan 2
no shut
int range g0/11-30
description 20-2 vlan
switchport mode access
switchport access vlan 3
no shut
ip routing
ip route 0.0.0.0 0.0.0.0 192.168.0.1
point each client's dhcp default GW to the respective vlan interface IP.
Point smoothwall routing for 172.20.2.0/24 to 192.168.0.2
Point smoothwall routing for 172.20.1.0/24 to 192.168.0.2
Smoothwall should already be aware of 192.168.0.1
Rob