Messages

1

Deployment / Re: wanos + ESXi with pfSense NAT

« on: December 26, 2014, 10:02:42 PM »

WanOS behind pfsense by UDPENCAP=Enable didn't work for me.  Is it possible for you to create a similar setup at your side and verify?

To continue with my tests I switched to following setup;
ISP Cable connects to WanOS wan0
WanOS Lan0 connects to PFSense wan
PFSense lan connects to lan switch
Desktops connect to lan switch

So far peers are up and I see graph data under Wan Tx Reduction columns.
I am using this tool to generate traffic http://www.roadkil.net/program.php/P5/CommTest for testing
Can you verify my traffic policies are correct? I just want optimization between 10.10.9.150 and 10.10.8.137.

The only thing with this setup is, assigning public ip to WanOS for management.
I tried Wanos Out of band management as mentioned at link http://wanos.co/forum/index.php?topic=49.0 but it did not work.
Added third nic in WanOS appliance connecting to LAN.  sudo vi /opt/bootlocal.sh to add
ifconfig eth2 192.168.210.99 netmask 255.255.255.0 broadcast 192.168.210.255 up
question - Do I still need to assign another ip e.g. 192.168.210.200 using wanos-cfg ?
Can you assist here?
SiteA :- Wan IP - 10.10.9.150/22  Lan network- 192.168.210.0/24 GW - 192.168.210.1
SiteB :- Wan IP - 10.10.8.137/22  Lan network- 192.168.220.0/24 GW - 192.168.220.1

I'll further continue to test vpn traffic between these two sites.

Thanks

2

Deployment / Re: wanos + ESXi with pfSense NAT

« on: December 24, 2014, 08:47:14 PM »

Interface status shows correct data for Receive and Transmit on wan0 and lan0 with Errors and Dropped : 0
Optimization and Interface Graps do report some activity but under "Sessions" all have 0% reduction
wanos-show bypass0.active  reports "true"

Ports are not reversed for sure, because when I reversed it, I lost access to environment

I will perform clean.sh action on both wanos appliance and start all over.

3

Deployment / Re: wanos + ESXi with pfSense NAT

« on: December 24, 2014, 07:32:17 PM »

On production wan it's still not working. Following is my config
HOLD=600
UPDENCAP=Enable
UDPPEERRATE=0.1

After connecting to machine at SiteA over RDP, openvpn client is started to access remote machine at SiteB.
Openvpn configuration changed to TCP from UCP and no compression.
Transferred 10GB files over vpn connection, still all columns under peer status page are blank.

4

Deployment / Re: wanos + ESXi with pfSense NAT

« on: December 24, 2014, 05:37:42 PM »

setting timeout to 180 did the job. 
Will continue testing by transferring files and then switch back to production wan setup that includes pfsense

5

Deployment / Re: wanos + ESXi with pfSense NAT

« on: December 24, 2014, 04:49:52 PM »

did another quick test by replicating http://wanos.co/wan-optimization/virtual-wan-optimization-esxi-lab-guide.
Created a new switch (no adapters) and added vms. Created traffic by copying files between vms.

Still the peer status is "down" but some data for Reduction. Please refer the attached images.

6

Deployment / Re: wanos + ESXi with pfSense NAT

« on: December 24, 2014, 03:22:32 PM »

Hello ahenning,

I deployed same setup on our production wan. UDPENCAP is enabled.
Established openvpn client connection form Site A to Site B and transferred 1GB of data. Peer status displays nothing, even Local Status is blank.

Also, In my local test environment peer status displays nothing, even Local Status is blank.

Kindly suggest.

7

Deployment / Re: wanos + ESXi with pfSense NAT

« on: December 23, 2014, 07:31:15 PM »

so peer status will still be down when UDPENCAP is enable ?

My idea of deployment it to optimize vpn traffic in production.
e.g. - client from Site A will establish vpn over Pfsense's internal OpenVPN to DC. (both sides have wanos)

If all looks good, I'll go ahead and implement the same over production network (over actual WAN) and see how it goes.

In case I run into problems, shall I continue on same post or start a new one?

Many thanks for your instant assistance and support 

8

Deployment / Re: wanos + ESXi with pfSense NAT

« on: December 23, 2014, 07:17:14 PM »

Following entries are in log

Site A
Tue Dec 23 17:48:00 UTC 2014  : Info : Cleared Statistics and Logs
Tue Dec 23 17:48:15 UTC 2014  : Info : Clearing the datastore
Tue Dec 23 17:48:15 UTC 2014  : Info : Reboot Requested
Tue Dec 23 17:48:27 UTC 2014  : Routine : Initializing Startup Scripts
Tue Dec 23 17:48:27 UTC 2014  : Routine : Set Interface Roles
Tue Dec 23 17:48:27 UTC 2014  : Routine : Setting Optional Interface driver flags if supported
Cannot set device flag settings: Operation not supported
Cannot set device flag settings: Operation not supported
Tue Dec 23 17:48:27 UTC 2014  : Routine : Check Configs
Tue Dec 23 17:48:27 UTC 2014  : Routine : Updating Configuration
Tue Dec 23 17:48:27 UTC 2014  : Routine : Initializing Wanos Click
wanos.click:11: While initializing 'wan0 :: FromDevice':
  warning: wan0: no IPv4 address assigned
wanos.click:12: While initializing 'lan0 :: FromDevice':
  warning: lan0: no IPv4 address assigned
Debug : Building datastore: 0
Debug : Prepare Ready: 0
Debug : Probe On
DropBroadcasts: dropped a packet
Tue Dec 23 18:43:40 UTC 2014  : Routine : Initializing Startup Scripts
Tue Dec 23 18:43:40 UTC 2014  : Routine : Set Interface Roles
Tue Dec 23 18:43:40 UTC 2014  : Routine : Setting Optional Interface driver flags if supported
Cannot set device flag settings: Operation not supported
Cannot set device flag settings: Operation not supported
Tue Dec 23 18:43:40 UTC 2014  : Routine : Check Configs
Tue Dec 23 18:43:40 UTC 2014  : Routine : Updating Configuration
Tue Dec 23 18:43:40 UTC 2014  : Routine : Initializing Wanos Click
wanos.click:12: While initializing 'lan0 :: FromDevice':
  warning: lan0: no IPv4 address assigned
wanos.click:11: While initializing 'wan0 :: FromDevice':
  warning: wan0: no IPv4 address assigned
Debug : Building datastore: 0
Debug : Prepare Ready: 0
Debug : Probe On
DropBroadcasts: dropped a packet


Site B
Tue Dec 23 17:47:58 UTC 2014  : Info : Cleared Statistics and Logs
Tue Dec 23 17:48:14 UTC 2014  : Info : Clearing the datastore
Tue Dec 23 17:48:14 UTC 2014  : Info : Reboot Requested
Tue Dec 23 17:48:25 UTC 2014  : Routine : Initializing Startup Scripts
Tue Dec 23 17:48:25 UTC 2014  : Routine : Set Interface Roles
Tue Dec 23 17:48:25 UTC 2014  : Routine : Setting Optional Interface driver flags if supported
Cannot set device flag settings: Operation not supported
Cannot set device flag settings: Operation not supported
Tue Dec 23 17:48:25 UTC 2014  : Routine : Check Configs
Tue Dec 23 17:48:25 UTC 2014  : Routine : Updating Configuration
Tue Dec 23 17:48:25 UTC 2014  : Routine : Initializing Wanos Click
wanos.click:11: While initializing 'wan0 :: FromDevice':
  warning: wan0: no IPv4 address assigned
wanos.click:12: While initializing 'lan0 :: FromDevice':
  warning: lan0: no IPv4 address assigned
Debug : Building datastore: 0
Debug : Prepare Ready: 0
Debug : Probe On
DropBroadcasts: dropped a packet
Tue Dec 23 18:43:29 UTC 2014  : Routine : Initializing Startup Scripts
Tue Dec 23 18:43:29 UTC 2014  : Routine : Set Interface Roles
Tue Dec 23 18:43:29 UTC 2014  : Routine : Setting Optional Interface driver flags if supported
Cannot set device flag settings: Operation not supported
Cannot set device flag settings: Operation not supported
Tue Dec 23 18:43:29 UTC 2014  : Routine : Check Configs
Tue Dec 23 18:43:29 UTC 2014  : Routine : Updating Configuration
Tue Dec 23 18:43:29 UTC 2014  : Routine : Initializing Wanos Click
wanos.click:12: While initializing 'lan0 :: FromDevice':
  warning: lan0: no IPv4 address assigned
wanos.click:11: While initializing 'wan0 :: FromDevice':
  warning: wan0: no IPv4 address assigned
Debug : Building datastore: 0
Debug : Prepare Ready: 0
Debug : Probe On
DropBroadcasts: dropped a packet

9

Deployment / Re: wanos + ESXi with pfSense NAT

« on: December 23, 2014, 07:13:49 PM »

Rebooted WanOS as well as PFSense after enabling UDPENCAP.

10

Deployment / Re: wanos + ESXi with pfSense NAT

« on: December 23, 2014, 06:45:31 PM »

vmnic0 = WAN. Has it's own physical nic connecting to office network (treating as WAN uplink)
vmnic3 = LAN. Has it's own physical nic connecting to a seperate switch
No adapters(Main) = bridging between PFsense_Lan and WanOS_WAN.

Lan = Site A (vlan0). This has Win7 and wanos
Lan_010 = Site b (vlan10). This has win7_010 and wanos_010

seems UDPENCAP=Enable in /tce/etc/wanos/wanos.conf did not help.

I am afraid as I can't disable nat nor enable 1:1 nat.

 

11

Deployment / wanos + ESXi with pfSense NAT

« on: December 23, 2014, 04:05:18 PM »

I have a similar setup on pfsense (simulating two sites on one esxi host), but I guess it's not working because local status is READY but Peer Status is Down
Traffic policies are default.
I have verified port connections are correct by matching mac addresses
Promiscuous Mode enabled on ports Lan, Lan_010, Main, Main_010

The setup as shown in attachment is as follows;
Pfsense, WanOs, Win7 (default ports)
Pfsense_010, WanOS_010, Win7_010 (Vlan10)
vSwitch2 is acting as a bridge between Pfsense & WanOs

On Win7, there is a website hosted and it can be accessed locally i.e. http://localhost.
If the website is accessed from Win7_010 (pfsense has nat rule for publishing http), site won't load and
internet & access to pfsense web gui stops for couple of minutes from both desktops.

Please suggest.