Wan Optimization Support
Technical => Troubleshooting => : Artecal March 11, 2015, 02:16:42 PM
-
I have a problem with the interface web on Wanos 2.0.1 I can't access to it
But with Wanos 1.4.1 I can access to it
I really don't know why I can't acces to it, if you have a idea, that will be nice ;)
-
On Hyper-V?
-
Yes on Hyper-V
-
Ok, I see a trend.
Easiest would be to upgrade from v1.4.1 to v2.0.3
Rest of the update process:
UPDATED: Software Update (http://wanos.co/docs/docs/wanos-admin-guide/configuration/software-update/)
-
Ok, thanks I have a other question about Wanos.
I'm a Intern who work in the firm Artecal, they are interested to use Wanos.
And I must check the efficient compression with Wanos.
So I have 2VM (windows7) and Wamos, I do the configuration and Wamos can ping the 2PC and the 2switches .
1PC for 1 Switch and 1 Switch for the others.
The 2PC's have access to the web interface.
The 2PC's can ping the 2 switches but the PC can't ping the others...
Vamos have 2 network cards and the PC1 have 1 network card, the PC2 have 1 other
If I can ping the pc to the other I can test after the efficient compressiona nd after try other test.
If you need screenshots say it, I hope that you understand what I want to do. It's very simple but just 1 thing didn't work...
I try to give vamos a gateway with the command "route add default gw 192.168.1.2 dev tmp0" and "route add default gw 192.168.2.2 dev tmp1"
I send screnshot to explain what a configure in Wanos.
And I put myself in a virtual network for being isolated from the real network of the firm.
I try a loot of things, I search on the web but no forum speak about Wanos. And I found no helpfull tutorial in french or in english for the configuration of Wanos.
If you can help me, that will be nice :)
Have a good day and best regards
-
Ok, stop :) There are some major issues here. In this lab scenario you don't have to configure anything on Wanos to start testing. It is just plug & play if the networks are right.
First the tmp0 and tmp1 is not correct. Possibly when a VM or Image was migrated to another machine. Run /etc/wanos/clean.sh to reset to defaults and start again.
The default mode is bridging. MAC Spoofing is required on Hyper-V. There are no IP addresses on lan0 and wan0. They are like ports on a switch. The default management ip address is 192.168.1.200. Change one side to 192.168.1.201 to see the stats and logs that side. The PC's can be e.g. 192.168.1.10 and 192.168.1.20.
Since your lab does not have a router, all devices can be on the 192.168.1.0/24 range. No routing required. Just make sure the switches are configured correctly so that traffic flows through Wanos. Test this by checking that if either Wanos is off, they should not be able to ping each other. The networks is the hardest part.
In Hyper-V use three virtual private lans:
virtual_lan1 for PC-1 and Wanos-1
virtual_wan for both wan0 interfaces
virtual_lan2 for PC-2 and Wanos-2
e.g.:
PC-1 -- Wanos-1 -- Wanos-2 -- PC-2
If you have any doubts, reference the ESXi lab guide:
ESXi lab guide (http://wanos.co/docs/esxi-lab-guide/)
-
Ok thanks, it's simple yet to understand :)
I will test it yet.
Have a good day,
-
Hello,
I try the test for have this solution :
PC-1 -- Wanos-1 -- Wanos-2 -- PC-2
But my PC1 can't ping my PC-2 >:(
PC-1: 192.168.1.10
PC-2: 192.168.1.20
Wanos-1: 192.168.1.200
Wanos-2: 192.168.1.201
I give a virtual network card for PC-1 and Wanos-1
A other for wanos-1 and wanos-2
And I give a gateway for PC-1 & PC-2 "192.168.1.1"
And a last for Wanos-2 and PC-2
My PC-2 don't have access to the interface web when I change the ip of Wanos-2 to "192.168.1.201" I just have access when I reset the default ip in "192.168.1.200"
They have all the same netmask "255.255.255.0"
I try to work on a isolalted network. On Hyper-V
I'm sure that Wanos-1 and Wanos-2 need a router, because the PC-1 can't communicate with PC-2 whitout no ?
At last I add 2 Network Traffic Policies like in your guide http://wanos.co/wan-optimization/pass-traffic-policy-4/
Well I hope that you can know why I can't ping PC1 to PC2
Have a good day :)
-
I'm sure that Wanos-1 and Wanos-2 need a router, because the PC-1 can't communicate with PC-2
No router or any wanos config required. Just plug and play. Its just a bridge/switch between PC-1 and PC-2.
Do you have MAC Spoofing enabled in Hyper-V for all the Wanos interfaces?
-
Yes I actived the MAC Spoofing in Hyper-V.
Other question, it's normal when I put out wanos and restart it I loose all the configuration ?
Do I have create a save of the configuration ?
-
No, its not normal. How are you changing the configs and which version are you running?
-
I would recommend to start completely over. It should take no more than 10-20 minutes to set up your lab.
1) Get a working lab by deploying the 1.4.1 vhd
2) Connect the virtual networks. Double check MAC spoofing.
3) ping from PC-1 to PC-2
All that before you even look at Wanos configuration.
-
Wanos 1.4.1
I just want to change the ip configuration for test something.
-
the command from the terminal is:
wanos-cfg
-
Oh thanks i search this so long :) :) :) :) :)
-
My friend, its in the link I sent you ;)
Ok, making it bold text.
-
It's work yet but it's not really what I want.
I want that the pc 1 have a address like : 172.168.x.x
And pc 2 have : 10.0.x.x.
It's a example I try to connect 2 devices without the same "address" "network"
Don't know if you understand what I mean.
The test work when the 2 PC have the same network like 192.168.1.10 and 192.168.1.20
-
Yes, got it. In that case you need a Router on the WAN network.
-
Ok and the wan router is on the web interface ?
"Or where can we config the router ?"
-
No, you need a Router or a vRouter to do the routing between your subnets. Perhaps pfSense, VyOS or Mikrotik.
The test work when the 2 PC have the same network like 192.168.1.10 and 192.168.1.20
That's as far as I can help with the lab test. Creating more advanced WAN simulations is out of scope.