NAT does't work with Backtrack
Posted: 24. Jan 2013, 20:48
Ehlo!
I have a backtrack 4s installed on VirtualBox on Windows. NAT doesn't work. It's just as simple as that. Ping response used for internet connection test. I'm connected in Windows but not connected in virtualized backtrack.
I didn't find a VBox.log to post here. Bridged network works but it emulates a cabled connection and I need my network adapter to be recognized by Backtrack (hence NAT needed!)
WICD doesn't show anything and gives this error:
"Could not connect to wicd's D-Bus interface"
I understand that this might be BackTrack's configuration and so I've posted to both forums.
Has anyone had previous experience with this?
I have a backtrack 4s installed on VirtualBox on Windows. NAT doesn't work. It's just as simple as that. Ping response used for internet connection test. I'm connected in Windows but not connected in virtualized backtrack.
I didn't find a VBox.log to post here. Bridged network works but it emulates a cabled connection and I need my network adapter to be recognized by Backtrack (hence NAT needed!)
WICD doesn't show anything and gives this error:
"Could not connect to wicd's D-Bus interface"
I understand that this might be BackTrack's configuration and so I've posted to both forums.
Has anyone had previous experience with this?