VB won't bind to IPSec Virtual Adapter

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Buhlz_I
Posts: 4
Joined: 22. Aug 2014, 21:05

VB won't bind to IPSec Virtual Adapter

Post by Buhlz_I »

 Edit: 
 Edit: 
 Edit:  
 
 
Hi,
I have VB 4.3.12 installed on a Dell Laptop. The laptop is used to remote access to a corporate net. For reasons unknown, I can't get a CentOS 7 guest to bind to the Cisco Virtual Adapter created by the VPN client. The systems are that it won't obtain an IP address. I've tried using all the different network modes. NAT Bridged is the only network configuration which is able to detect the virtual adapter...but still the guest will not bind and obtain an IP.


Laptop network information
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : Home Lan
Link-local IPv6 Address . . . . . : fe80::29a3:73b6:769b:a9a7%18
IPv4 Address. . . . . . . . . . . : 192.168.x.x (scrubbed)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.x.x (scrubbed)

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . : Cisco IPsec Adapter
Link-local IPv6 Address . . . . . : fe80::d8d9:6cec:f5ae:2d25%16
IPv4 Address. . . . . . . . . . . : 192.168.x.x (scrubbed)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.x.x (scubbed)

Ethernet adapter VirtualBox Host-Only Network:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::2096:4a51:8c0c:9ee2%28
Autoconfiguration IPv4 Address. . : 169.254.158.226
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :


CentOS Guest:
Attached pic
Attachments
VB.PNG
VB.PNG (34.38 KiB) Viewed 1536 times
BillG
Volunteer
Posts: 5106
Joined: 19. Sep 2009, 04:44
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows 10,7 and earlier
Location: Sydney, Australia

Re: VB won't bind to IPSec Virtual Adapter

Post by BillG »

What exactly do you mean by "NAT bridged"? NAT and bridged are quite different networking modes.

I would not expect any network mode to do what you want. VPN connections are quite different from a normal network connection and are quite difficult to share.
Bill
Buhlz_I
Posts: 4
Joined: 22. Aug 2014, 21:05

Re: VB won't bind to IPSec Virtual Adapter

Post by Buhlz_I »

Hi Bill....It was my observation that NAT Bridged was the only network setting which enumerated the Cisco VPN adapter. The bigger issue is getting it to work. I'm hoping someone may have experience with this mode of operation.
Buhlz_I
Posts: 4
Joined: 22. Aug 2014, 21:05

Re: VB won't bind to IPSec Virtual Adapter

Post by Buhlz_I »

I've made some progress....I managed to get the VB guest to bind to the adapter of the laptop. The guest host has an RFC address 10.0.2.x as it should. Now about how to get the packets to route through the IPsec Adapter.
BillG
Volunteer
Posts: 5106
Joined: 19. Sep 2009, 04:44
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows 10,7 and earlier
Location: Sydney, Australia

Re: VB won't bind to IPSec Virtual Adapter

Post by BillG »

If you have a 10.0.2 IP you are using NAT. The guest will be sharing the host's connection - that is how NAT works. If it is going to work (which I doubt), you don't need to do anything.
Bill
Post Reply