Wan Optimization Support
Technical => Troubleshooting => : tipsmark May 28, 2015, 08:02:33 PM
-
tried this, just cant get it working... when I configure for example wan0 with wanos-cfg and set the ip to 192.168.0.254 then edit /tce/etc/wanos/wanos.conf and set lan0 to 192.168.0.250/24 I am only able to ping 192.168.0.254.
-
Ping the virtual lan0 from the network side.
The virtual lan0 is not pingable "locally" ... yet.
-
not sure what you mean? wanos has a single nic and is on same subnet as the host that can ping the ip configured with wanos-cfg but unable to ping the ip address set via vi /tce/etc/wanos/wanos.conf.
how do I verify the wanos is in routing mode?
-
Ping the virtual lan0 ip address from the network e.g. the server or router in the same address range. The virtual lan0 address is not reachable from the linux command line.
-
thats what I did, not reachable from the network in the same range either. Tried this multiple times deploying new templates, tried in vmware, virtual box etc.
-
Oh ok, enable promiscuous mode.
-
ok that and forged transmit (spoofing) worked. enough to do it on port level too, no required for entire portgroup. thx now I can move on with testing.
http://i.imgur.com/piJ923L.png
where would I put my wanos applicances with this topology?
-
To make testing easy:
Bridge mode at the remote site between ISP FW and L2 Switch.
Main site router mode in Vlan 5.
Test sever default route = wanos-lan0
ASA FW static host route 10.0.5.10/32 = wanos-wan0
Note: some route/ip stacks will just hand off from the FW directly to the server and ignore the /32 route when the destination address is in the same range as the interface.