On Thu, Aug 30, 2012 at 11:16 AM, Fernando Cassia <[email protected]> wrote: > On Thu, Aug 30, 2012 at 4:39 AM, Alexey Eromenko <[email protected]> wrote: >> "tun2socks" is a big question. VBox does NOT create TUN interfaces, >> but can access TAP interfaces. > > I don´t even know what a TUN interface is... I just thought the > "tun2socks" name was to indicate "TUNNEL to SOCKS" > > If, as the project description says, it creates a new ´fake´ (virtual) > ethernet device, and I bridge VBox to that NIC, what would be the > problem?.
TUN interface are a virtual layer 3 interfaces. TAP interfaces are virtual layer 2 interfaces. They are related to the same developers, and is commonly called TUN/TAP. VirtualBox does support TAP, but not TUN. The clean way to fix this issue is to develop a new networking mode "socks proxy" for VirtualBox itself, based on current NAT code. But you can try some other ways for a "dirty fix". -- -Alexey Eromenko "Technologov" ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:[email protected]?subject=unsubscribe
