Messages

1

Troubleshooting / Re: Peer Status down over IPSec VPN

« on: January 05, 2015, 04:19:07 PM »

Hello Ahenning,
I got everything working in the end I'm glad to say.
I removed all rules, double checked all the cabling and then accesses a file share, within a couple of seconds the peers came up.
I've done a bit of testing and so far so good, I'm beginning to think my boxes aren't quite quick enough for my 12mb & 18mb upload or I need to drop optimization to low and give the servers chance to reply.

My next steps are to remove VMware and buy 2 x 120GB SSD drives and deploy the appliance image directly onto them giving them the following spec:
◾Processor 1 x AMD Turion II Neo N54L / 2.2 GHz ( Dual-Core )
◾8GB RAM
◾120GB SSD

Would to estimate that the above spec would be fast enough for the uploads I've quoted?

One thing I was going to ask now I'm almost up and running fully, is there a way to set the correct time automatically? I can use the time command to do it but on reboot it defaults back. Ideally NTP would be very useful option.

2

Troubleshooting / Peer Status down over IPSec VPN

« on: November 12, 2014, 02:41:28 PM »

Afternoon,
I currently have two subnets I'm trying to implement WanOS over. They are 192.168.1.0/24 & 192.168.2.0/24

I have installed VMware ESXi 5.5 on two HP Microservers and installed a dual port network card into each of these, they are both running 6gb ram.

I've assigned LAN0 one network card and WAN0 a separate network card, the management kernel is on the third network card.
This is identical on both servers.

All Standard vSwitches have the promiscuous mode set.

Every time I attempt to view Peer Status it just says down.

I did notice last night after reading some of the forum posts that my MTU was set wrong, WanOS was set to 1500 and the max that my broadband supports is 1442, I am using PPPoE authentication for connecting to my broadband supplier so have dropped this to 1400 on both routers, this should account for the additional header that PPPoE requires.

I can ping the remote networks fine, when I tracer route from a client on the network I get the following:
192.168.1.108 - My PC
192.168.1.1 - My Router
* * * *
I get 14 of these
* * * *
192.168.2.1

My next step is to bring the remote server to my house and build a test network to see if I can get the peer status up.

Is there anything obvious that I'm missing??

Cheers

Rob