Welcome, Guest. Please login or register.
Did you miss your activation email?
Wednesday 11 December 2019, 03:32:10 am

Login with username, password and session length

Visit the Official Endian Bug tracker  HERE
13964 Posts in 4252 Topics by 6023 Members
Latest Member: krunal
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  VPN Support
| | |-+  Endian migration to Hyper-V and OpenVPN issues
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Endian migration to Hyper-V and OpenVPN issues  (Read 3461 times)
gsandorx
Jr. Member
*
Offline Offline

Posts: 3


« on: Saturday 13 June 2015, 02:36:09 pm »

Hi,

We are working on a migration from ESXi to Hyper-V. We've already compiled a kernel (3.12.43 -- longterm kernel branch) with the Hyper-V modules, etc. and it runs flawlessly, as far as we can tell.

There's a VM though, that's giving us some grief. It's running Endian 2.5.1, still on VMware ESXi. We've tried creating a new VM with Endian 3.0.0dev on Hyper-V with our custom kernel and restoring a backup (we've also followed the recommendation of deleting /etc/businfotab, etc. to get back eth0, eth1, due to the new MAC addresses). When doing this, the tap0 interface goes away (i.e. no longer present in the ifconfig output) although in the GUI everything seems to be fine. Even loading the new VM with the original Endian kernel wouldn't bring up the tap0 interface.

We've tried installing our custom kernel on the existing machine and converting it to Hyper-V. After doing this, the tap0 shows up in ifconfig and we can connect to the tunnel. However, the firewall DHCP server is now handing 2 IP addresses to the client VPN, instead of just one. We can ping from the remote client the firewall interfaces, but nothing else within our LAN segment. I also noticed some Connection Refused (error code=11) in the OpenVPN logs.

Any help will be much appreciated.

Thanks

Logged
gsandorx
Jr. Member
*
Offline Offline

Posts: 3


« Reply #1 on: Saturday 13 June 2015, 02:40:36 pm »

ERRATA: The OpenVPN log message reads:

openvpn[4231]: read UDPv4 [CMSG=8|ECONNREFUSED]: Connection refused (code=111)

Logged
gsandorx
Jr. Member
*
Offline Offline

Posts: 3


« Reply #2 on: Saturday 13 June 2015, 02:46:52 pm »

ERRATA2: Sorry guys, just noticed that the VPN connection to the original VM (the one on VMware) also hands 2 IP addresses to the VPN client (at least on my Mac using the TunnelBlick VPN client), and yet the VPN works fine.

But there's definitively something going on with the tap0 interface.
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.031 seconds with 18 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com