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

Pages: [1]
1
Configuration / Re: Traffic Policies
« on: April 03, 2014, 04:08:55 PM »
Working - thanks!

2
Configuration / Re: Traffic Policies
« on: April 03, 2014, 03:02:08 PM »
After using the devices in a lab, I wanted to test in production.  I placed the Edge Device at my colo space last night.  All seems fine - no changes whatsoever.

This morning when I inserted the Core device between my LAN and my router, I lost all traffic to the Internet except those specifically bypassed (I could ping for example, but not browse).  I ended up pulling the device until I could figure out what I was doing wrong.  I really only need to use the devices going from 192.168.2.0/24 and 192.168.100.0/24.  No other traffic needs caching at all.

I started with the base set of rules - couldn't pass traffic.  I then added rules to bypass traffic originating from 192.168.2.0/24 going to 0.0.0.0/0 on TCP and then another on UDP - no change.  Here is what is currently failing:



3

/wanos -> /mnt/sda2/wanos/

OK - So it seems like it's good then!  Thank you so much.

Michael

4
Installation / Changing the DataStore Location on a Physical Device
« on: March 27, 2014, 02:30:17 PM »
This post demonstrates my lack of Linux skill more than anything -

I wrote the base image to a 120GB SATA disk and it works fine, but I would like to use the remaining capacity for caching as well.  So my disk had a single partition of 4~GB labeled /dev/sda1.  I created a second primary partition, /dev/sda2 using the remaining space.

I used this command to create a path: "sudo mkdir /mnt/sda2"
I then mounted the partition using: mount "sudo /dev/sda2 /mnt/sda2/"
I then created a subdirectory on this newly mounted drive using this command: "sudo mkdir -p /mnt/sda2/wanos/ds0"
I then edited the bootlocal.sh script using the command: "sudo vi /opt/bootlocal.sh"
  I have added the line: "mount /dev/sda2 /mnt/sda2"
  I have added the line: "ln -s /mnt/sda2/wanos /wanos"
  I have commented out the line: "ln -s /mnt/sda1/wanos /wanos"

I thought this would do the trick, and the system boots fine, but when I go into the interface, I am shown that the Datastore Disk is still /dev/sda1 and I was thinking it should be /dev/sda2.

Michael



5
Installation / Re: Hardware Compatibility
« on: March 26, 2014, 08:15:17 PM »

My initial binary FTP file from the core side to the edge side took 1251 seconds.  Deleted the file and repeated the exact same file and it took 544 seconds!

I hadn't throttled the port to 1Mbps yet though.  Is doing that just so you are positive that the difference is 100% attributable to the devices and not random other bottlenecks such as disk I/O at either end?

AND.. as a second question.. should I see as much optimization from the Edge end going towards the core?





6
Installation / Re: Hardware Compatibility
« on: March 26, 2014, 05:11:35 PM »
Our "Lab" is now up and running.  Our config is:

Me > Switch > WanOS-Core > Switch < WanOS-Edge < Switch < Rest of our LAN

Our WanOS boxes are both:

HP PC's
Core2 Duo Processors @ 1.86Ghtz;
4GB RAM
120GB SATA Solid State Drives at 3Gbps

I am still running the default image at this time, so not using the full disk yet, but hope to figure this out soon.  My Linux skills are less than stellar but growing.

Michael


7
Installation / Re: Hardware Compatibility
« on: March 25, 2014, 04:07:31 PM »
All is well. 

I totally isolated the wanOS box and had no trouble getting in.  I then re-IP'd it to our normal LAN subnet and reconnected it to the LAN and can get in fine.

Your software is fine, apparently something on my LAN is not - kudos to you and thank you for the assistance.  Hopefully I can return the favor sometime.

Michael



8
Installation / Re: Hardware Compatibility
« on: March 25, 2014, 02:38:39 PM »
I don't think the switches I am using are sophisticated enough to do so.

If I have both NICs in the box but only the lan0 cabled to a cheap unmanaged switch, and then connect my laptop to that switch (to isolate the wanOS box from my production LAN, it should still boot fine - correct?


9
Installation / Re: Hardware Compatibility
« on: March 25, 2014, 02:02:23 PM »
I ran the clean.sh script - upon reboot, I can ifconfig each interface and see them.  The tun0 interface does in fact have the 192.168.1.200 address.  I was able to ping that interface - and it replied, but only once, then never again.

C:\Users\mac>ping 192.168.1.200

Pinging 192.168.1.200 with 32 bytes of data:
Reply from 192.168.1.200: bytes=32 time=1ms TTL=64
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.200:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms

Very strange.

10
Installation / Hardware Compatibility
« on: March 24, 2014, 10:19:58 PM »

I have an HP workstation that boots the OS correctly - the two NICs that I have are Linux compatible - one for sure seems detected.  I can't seem to get to the web interface though no matter what I try.

If both NICs are the same, I assume then that driver is compatible.

Thoughts?


Pages: [1]