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 - Treeeman

Pages: [1]
1
I will talk to him. We will see.  ;)

2
Ok. Thank you. Now everything is clear. Nice Product.

3
General Discussion / Re: Configuraton backup
« on: March 17, 2015, 02:40:13 PM »
How i am able to restore my wanos with the backup i created with "show tech"?
Is there a Guide?
Thanks!

4
Ok, fine.
What do you mean with the default Bypass Rule?
Screenshot of my current Traffice Rules attached.

Do you mean i should delete my existing Rules for Destination Networks 192.168.51x, 192.168.52.x and 192.168.53.x or should i create a new rule like No. 99 and give it a lower priority?

How i am able to restore my wanos with the backup i created with "show tech"?

Thank you.

5
General Discussion / Re: Version 2.0.3
« on: March 17, 2015, 02:28:12 PM »
Ok. Thanks.

6
Hi,

thanks for your Reply.
Yes. I tried the Update twice in my lab without any issue.

I have some Questions:
- How am i able to backup my config of my wanos hardware appliance before updating?
- Is it a Problem if i Update one site to 2.0.4 and the other site is meanwhile still on 2.0.1?
- Because i want to disturb the Traffic as less as possible, i whould like to disconnect my wanos during update and connect my L3 Switch and Firewall directly together. So there are just two Connections Breaks for my Customer. Disconnect before Update and Connect back after Update. Also i am able to do my Update and check if everything looks nice before getting productive again. Is this a good idea or whould you leave the wanos in productive while updating?

Thanks.
Kind Regards
Marco

7
Hi,

i've read your post for the new Version 2.0.4 and did a update in my lab.

I have a customer with a wanos appliance version 2.0.1 at the main office and one wanos appliance at the site office. My Main Office has a 10Mbit/s Up- and Download. The Remote Site has 5Mbit/s Download and about 0.75Mbit/s Upload. I am just optimizing traffic between this sites. So the new Up- and Download Restriction of Version 2.0.4 should not be a problem.

My Question:
What is the Best Practice to Update this to Version 2.0.4?

Thanks.
Kind Regards
Marco

8
General Discussion / Configuraton backup
« on: March 17, 2015, 12:49:13 PM »
Hi,

how i am able to backup my configuration in case of a desaster recovery situation?
In case my Hardware Wanos Appliance Harddrive crashes, i whould like to be able to change the faulty drive, install a fresh installation of wanos and recover my previous settings.

How i am able to do this?

Thanks.
Kind Regards
Marco

9
General Discussion / Re: Version 2.0.3
« on: March 17, 2015, 12:46:35 PM »
Hi,

"Single Ethernet Deployment" is a new Feature of 2.0.3.
What does this mean. Is there a writte Guide for me?

Thanks!
Kind Regards
Marco

10
Deployment / Re: VMware Deployment Question
« on: January 19, 2015, 01:18:01 PM »
Hello,

meanwhile i am doing a Installation on my customers site and have some Problems where i need your help please.

System Overview (before implementing WANOS):
- 3x ESXi 5.5 Server in a VMware HA-Cluster
- a L3 HP Procurve 5412zl Core Switch with 9x VLANs (VLAN 1 - 10) for internal Communication and 1 VLAN (50) for Firewall Communication.
- IP Core Switch VLAN 50: 10.50.0.254 with Default IP Route to Firewall
- IP Firewall VLAN 50: 10.50.0.250

What i have done to implenent WANOS:
- Created a new VLAN 51 and named it "WANOS-WAN" on the Core Switch
- Enabled "RSTP" on my HP Procurve Switch
- VLAN 50 was named "WANOS-LAN"
- Tagged VLAN 50 and 51 in my virtual Environment
- Create on a existing vSwitch two new VM Networks named "WANOS-WAN" and "WANOS-LAN" with the specific VLAN Tagging. Promiscuous Mode is enabled on each of the new VM Networks.
- Import WANOS Appliance and connected NIC 1 to "WANOS-WAN" and NIC 2 to "WANOS-LAN"
- Power Up WANOS
- Changed IP of my WANOS Appliance to 10.50.0.200 to access it for management
- Physically disconnected my Firewall from a Port with untagged Membership VLAN 50 and connected it to a Switch Port with untagged Membership VLAN 51

My Problem:
After the WANOS Appliance was powered up i was able to ping my Core Switch, my Firewall and the WANOS. After connecting my Firewall from VLAN 50 to VLAN 51 i was still able to ping my Core Switch and my WANOS. Firewall was down. After connecting my Firewall back to my VLAN 50 Port i was again able to reach my Firewall and my Core Switch. My WANOS was not reachable any more.

My Questions:
- Is there a mistake within my Configuration?
- I read i have to enable PVST. Because there is no PVST on ProCurve, maybe there is a Problem in my Spanning Tree Configuration

Many Thanks!
Kind Regards
Marco

11
Deployment / Re: VMware Deployment Question
« on: January 14, 2015, 10:01:25 AM »
Hi,

thanks for your quick reply.

Kind Regards
Marco

12
Deployment / VMware Deployment Question
« on: January 14, 2015, 09:46:25 AM »
Hi,

i have a Deploment Question for wanos.
I have multible VLANs (ID: 1-10) which are routed by a Layer 3 Core Switch. Additionally there is a "Transfer"-VLAN (ID 11) where my Core Switch and my Firewall are untagged Members. The Default Gateway of my Core-Switch is the Firewall.

Now i want to deploy an wanos VM.
I dont want to change any Routing, IPs or Default Gateways.
How i am able to deploy wanos? I think i should work with two different VLANs between my Core-Switch and my Firewall to place the wanos between them. Right?

Thanks!
Marco




13
Deployment / Deploqment Question over Cisco VPN Tunnel
« on: December 11, 2014, 02:13:08 PM »
Hello,

i have a deployment question.
There are two Sites (A and B). The Sites are connected over a VPN Tunnel (Cisco). The Headquarter is on Site A. Remote Office on Site B.

If my understanding is correct, the Deployment should look like this:
Site A - L3 Routing Switch - Wanos Core - Cisco FW ===L3 VPN-TUNNEL=== Cisco FW - Wanos Edge - L3 Routing Switch - Site B

My Main Question is how the tho Wanos Appliances can see each other? I installed a ESXi Lab Environment like described on your Page. Because the WAN Interface is on the same L2 Netzwork they connect each other automatically. But there is no way i found to give my Wanos Core the information which IP my Wanos Edge has (and vice versa). Because i have a Layer 3 Tunnel i am a little confused now.

Maybe someone has a simple answer to this.
Thanks a lot.

Best Regards
Marco

Pages: [1]