hidden at xmission
Jun 22, 2012, 3:59 PM
Post #2 of 3
For basic testing, I would get rid of static host-based routes and use a
Re: Quick question regarding routing between vlans on Ti24
[In reply to]
default route pointed at the TI24. If that works, then the problem is with
the machines, not the TI.
From: foundry-nsp-bounces [at] puck
[mailto:foundry-nsp-bounces [at] puck] On Behalf Of Drew Weaver
Sent: Friday, June 22, 2012 12:43 PM
To: foundry-nsp [at] puck
Subject: [f-nsp] Quick question regarding routing between vlans on Ti24
I have a Turboiron 24x configured as such:
vlan 101 by port
tagged ethe 7
router-interface ve 101
vlan 998 by port
tagged ethe 19
router-interface ve 2
interface ve 2
ip address 192.168.227.1 255.255.255.248
interface ve 101
ip address 192.168.0.1 255.255.255.248
The hosts (192.168.227.2) and (192.168.0.2) can both ping their respective
VEs, but they cannot ping one another.
I have static routes nailed up on the hosts:
192.168.0.0 192.168.227.1 255.255.224.0 UG 0 0 0 eth1
192.168.227.0 192.168.0.1 255.255.255.0 UG 0 0 0 em2
Anyone know what I need to do to tell it to go ahead and route ?
p.s. the reason the subnets configured on the hosts are larger than what is
configured on the TI is because I intend on having multiple subnets
reachable in both directions.