Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - peter

Pages: 1 2 [3]
31
As dynamic IP within a  period is fixed,   I can use google to find my two dynamic IPs ( two offices) and start networking such as ftp, ssh and etc.

But I do not know how to setup the wanos.

For example I have a ftp server on one side as follows,

office1_network --- switch --- wanos --- isp_router1 --- WAN --- isp_router2 ---wanos --- switch --- office2_network (including ftp_server, samba_server, and other servers, and each server with a dedicated computer)

Pls help.

32
Troubleshooting / Re: wanos throughput on kvm
« on: September 18, 2014, 06:53:19 AM »
Eventually, I caught the break.  The issue with low throughput is because of  NIC
 hardware.  I was using Silicom cards with company provided  drivers for testing.
When I switched to pure Intel NIC cards, the throughput on KVM is good. 
                           
Testing result with wanos on KVM virtual machine

a) 100Mbits network environment;
b) vsftpd for ftp testing run
 
1) with both core and edge bypass (no optimization)
2) with only core bypass
3) with only edge bypass

all above three test cases gave around 10-12MB throughput which is very reasonable.

Thanks again.

33
Troubleshooting / Re: wanos throughput on kvm
« on: September 12, 2014, 06:38:19 AM »
Step for setup on KVM
Many  kudoes to Silverpeak kvm virtual machine setup guide.

Base system:

Ubuntu server 10.04 (LTS) (ubuntu-10.04.4-server-amd64.iso)
with 3 nics as follows:
nic wan and lan interfaces for virtual machine bridging
nic mgmt ip 192.168.2.100

Step1 : basic package install
Pls do apt-get update first

apt-get install qemu-kvm  (virtual machine kernel module)
apt-get install bridge-utils (virtual networking)
apt-get install vncviewer
(virtual machine console connection, as Ubuntu server does not have X, qemu
console simulation will not work.)

Ubuntu network config file for bridging to work (/etc/network/interface)
Mapping network interface name, config goes to file /etc/udev/rules.d/70-persistent-net.rules
***************************************
auto lo
iface lo inet loopback


auto mgmt
iface mgmt inet static
      address 192.168.2.100
      network 192.168.2.0
      netmask 255.255.255.0
      gateway 192.168.2.1

auto wbr
iface wbr inet manual
        bridge_ports wan
        bridge_stp off
        bridge_fd 0
        bridge_maxwait 0

auto lbr
iface lbr inet manual
        bridge_ports lan
        bridge_stp off
        bridge_fd 0
***************************************
Step 2:  Creating Ubuntu server virtual machine for dding wanos disk image
1) creating a Ubuntu server virtual diska (20G);
   qemu-img create -f raw  diska 20G
2) creating a Wanos virtual diskb (70G)
   qemu-img create -f raw  diskb 70G

(Silverpeak emphasizes that virtual disk needs to be on raw format)

Step 3:
1) Install virtual Ubuntu server on diska
   sudo qemu-system-x86_64   -device virtio-net-pci,netdev=net1,mac=DE:AD:BE:EF:35:52 -netdev tap,id=net1,script=qemu-ifup-wan -device virtio-net-pci,netdev=net0,mac=DE:AD:BE:EF:35:51 -netdev tap,id=net0,script=qemu-ifup-lan -vnc :1 -drive file=./diska,if=virtio -m 2048 -boot d -cdrom ./ubuntu-10.04.4-server-amd64.iso

   vncviewer 192.168.2.100 :1
   to connect console for system installation.
qemu-ifup-lan file
#!/bin/sh
nic=$1
ifconfig $nic 0.0.0.0 up
brctl addif lbr $nic

qemu-ifup-wan file
#!/bin/sh
nic=$1
ifconfig $nic 0.0.0.0 up
brctl addif wbr $nic

2) boot after completing server installation
   sudo qemu-system-x86_64   -device virtio-net-pci,netdev=net1,mac=DE:AD:BE:EF:35:52 -netdev tap,id=net1,script=qemu-ifup-wan -device virtio-net-pci,netdev=net0,mac=DE:AD:BE:EF:35:51 -netdev tap,id=net0,script=qemu-ifup-lan -vnc :1 -drive file=./diska,if=virtio,boot=on -drive file=./diskb,if=virtio -m 2048

3) Upload Wanos image and dding to diskb
   kvm calls diska as /dev/vda and diskb as /dev/vdb

4) dump diska and boot virtual machine on diskb
   sudo qemu-system-x86_64   -device virtio-net-pci,netdev=net1,mac=DE:AD:BE:EF:35:52 -netdev tap,id=net1,script=qemu-ifup-wan -device virtio-net-pci,netdev=net0,mac=DE:AD:BE:EF:35:51 -netdev tap,id=net0,script=qemu-ifup-lan -vnc :1 -drive file=./diskb,if=virtio,boot=on  -m 2048


Step 4:
by vncviewer, logging on wanos and doing clean.sh script to restart wanos.

34
Troubleshooting / Re: wanos throughput on kvm
« on: September 02, 2014, 08:21:31 AM »
Good news is wanos seems to work on KVM, but I will keep testing to make sure it
 is.

But both test commands did not seem to work on both core and edge nodes within 10 minutes testing period.

Test 1 (PCAP) on both core and edge only gave following output:

config:1: While initializing 'FromDevice@1 :: FromDevice':
   warning: lan0: no IPv4 address assigned

config:1: While initializing 'FromDevice@4 :: FromDevice':
   warning: lan0: no IPv4 address assigned

Test 2 (LINUX) on both core and edge nodes gave nothing output.

Thanks

35
Troubleshooting / Re: wanos on kvm
« on: August 18, 2014, 05:29:26 AM »
hi,
     I am still trying to put wanos on kvm virtual machine.  As my test on the first post was not promising, I tried to rule out degrading effect from kvm platform this time.

 Steps are as follows, 

1)  I put a Ubuntu server on kvm virtual machine with two nic interfaces.
2)  Bridge two nics and let network traffic through.  As switch is 100M, I got 10-12mbytes which is very reasonable.
3)  With exactly above setting(virtio nic and virtio disk drivers loaded ), dd 1.2.1 to kvm virtual disk and got wanos running.  But, throughput rate went down dramatically to 17k.

As regular linux distribution did not degrade on kvm, my guess is that wanos internal design does not fit on kvm platform.  However, I am still not going to give it up on KVM and would like to ask you guys to give a test,please.

Thanks

36
Configuration / Re: By-pass rules required on Edge and Core?
« on: July 08, 2014, 09:16:26 AM »
core device 192.168.4.0/24

37
Configuration / Re: By-pass rules required on Edge and Core?
« on: July 08, 2014, 09:15:20 AM »
edge device 192.168.3.0/24

38
Configuration / Re: By-pass rules required on Edge and Core?
« on: July 08, 2014, 09:10:29 AM »
by-pass rules seem not work or I could be wrong, pls help

test version 1.2.1 with ftp

network setup

client --- wanos(edge) --- router --- wanos(core) --- server

 192.168.3.0/24(client)            192.168.4.0/24(server)

tc network simulation running on router

step 1
no wanos devices for acceleration
client --- router --- server

ftp output bandwidth is around 280k

step 2

with wanos devices for acceleration

client --- wanos(edge) --- router --- wanos(core) --- server
ftp output bandwidth improves to 680k which is great


step 3

with step 2 setup, by adding  by-pass rule for network 192.168.3.0/24
pls see separate attachments enabled on both core and edge

ftp output bandwidth still improves to 1300, guessing because of 2nd transferring.  But, it is suppose to get step 1 output bandwidth.
Please help and thanks.
(attachment follows)


39
General Discussion / Re: 1.2.1 Release
« on: July 06, 2014, 11:12:10 PM »
Great job and thanks.

One thing I would like to be cleared:
Edge to Edge, Edge to Core and Core to Edge, optimization is working.
Core to Core, optimization is not yet.
If there is a core and a lot of edges, optimization is working.
Please show what network topology is when core to core optimization needed?  Would be optimization between the networks such as following:

headoffice1(core) ---- branch11(edge) ( optimization  ok)
headoffice2 (core) --- branch21(edge) ( optimization  ok )
headoffice1(core) --- headoffice2 (core) ( no optimization)

chance of work around ( would it be optimization )
put a dummy headoffice and rest of them into edge mode.
dummyhead (core) --- headoffice1(edge)
                            --- headoffice2 (edge)
                            --- branch11 (edge)
                            --- branch12 (edge)

40
Hi,
It is actualan old question which was leave one wanos ( here was the core ) on inpath broke whole network.
reproduce
looking for
client --- wanos(edge) --- route --- wanos(core) --- server

1. build network
client --- route --- server
everthing works : client can http ftp cifs server

2. put wanos (core) into network
client --- route --- wanos(core) --- server
nothing works: client can not http ftp cifs server

3. put wanos (edge) into network
everything works again.

As my understanding, step 2 should be working with no optimization. My test environment is vmware workstaion 10 with dedicate wan0 and lan0 interfaces. 
Or, I am missing something over here. Otherwise, in reality, there is no way you can put core and edge device up at the same time.

edit: subject description

41
Troubleshooting / wanos throughput on kvm
« on: June 12, 2014, 06:13:11 AM »
Hi,
First, I need to put wanos on VMware is very good.
After, I tried to put wanos(1.8) on kvm virtual machine by dd HDD image since KVM is only pure free open source virtual platform and with commands to manage VM.
But, the optimization did not work at all and even slower than no optimisation.  So,  I have to wonder if I do something wrong with the setup.  Please shed light on it.  Thanks. 

Pages: 1 2 [3]