Bug #7081

No networking in VirtualBox

Added by tailserror 2014-04-13 21:24:27 . Updated 2015-01-03 00:49:15 .

Status:
Duplicate
Priority:
Elevated
Assignee:
tailserror
Category:
Virtualization
Target version:
Start date:
2014-04-13
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

Using the image from 0.23 doesnt work well in virtualbox. I am using the same configuration as with the working image 0.22.
If starting the browser a message pops up “Tor is not ready. Start Tor Browser anyway?”

host: debian sid, latest virtualbox 4.3.10-dfsg-1

Subtasks

Related issues

Is duplicate of Tails - Bug #7695: No network with VirtualBox, Bridged Mode, and MAC Spoofing Rejected 2014-07-31

History

#1 Updated by sajolida 2014-04-14 06:39:45

  • Type of work changed from Audit to Research

I’m using a very similar setup and Tails 0.23 works fine in VirtualBox. A problem I have, and I think more people already reported, is that the network doesn’t work if Mac spoofing is enabled. Can you tell us what happens if you disable Mac spoofing. See https://tails.boum.org/doc/first_steps/startup_options/mac_spoofing/.

Can you also tell us which network configuration you are using in VirtualBox.

If this is the same issue as the one I face, then it is a regression and the priority “High” is deserved.

#2 Updated by tailserror 2014-04-14 18:39:53

I tried it with the flag on the greeter set and unset, both give the same result.
The setup in Virtualbox is IntelPro/1000 Desktop - Hostonly Adapter, vboxnet0, promiscmode deny, cable connected - exactly the same as in the working setup, the routing to the internet is done by iptables masquerading and forwarding, I even used the same virtual machine once for both, just started it with different images, which leads to booting and connecting to the internet in the old version, and booting and giving the errormsg when opening the browser in the new one. And in case it matters: the ip is assigned automaticly, the default route I set via ‘route add default gw $hostip’ myself. works for old version, but not for the new one.

(thought ‘high’ is the right priority for issues that render core features unuseable … and assumed connecting to the web counts as a core feature ;) )

#3 Updated by sajolida 2014-04-15 08:18:44

> I tried it with the flag on the greeter set and unset, both give the
> same result.

Ok, then please start without MAC spoofing and report your problem using
WhisperBack so we can have more technical details from the logs:

https://tails.boum.org/doc/first_steps/bug_reporting/

#4 Updated by intrigeri 2014-04-15 09:51:24

  • Priority changed from High to Elevated

We usually set priority = elevated for regressions, more even so when they only affect a small subset of users. If we set High priority for those, then we would have no way to sort them apart of e.g. critical security issues that affect everybody.

#5 Updated by BitingBird 2014-05-12 11:50:51

  • Subject changed from Tails 0.23 won|t start browser if running in virtualbox to Tails 0.23 won't start browser if running in virtualbox
  • Category set to 176

#6 Updated by intrigeri 2014-05-12 14:17:15

  • Subject changed from Tails 0.23 won't start browser if running in virtualbox to No networking in VirtualBox
  • Assignee set to tailserror
  • QA Check set to Info Needed

tailserror: ping?

#7 Updated by intrigeri 2014-06-20 13:31:00

  • Category changed from 176 to Hardware support
  • Status changed from New to Rejected

Unreproducible, additional info requested 2 months ago was not provided => closing.

#8 Updated by emmapeel 2014-08-10 17:56:24

  • is duplicate of Bug #7695: No network with VirtualBox, Bridged Mode, and MAC Spoofing added

#9 Updated by sajolida 2014-11-16 11:20:39

  • Category changed from Hardware support to Virtualization

#10 Updated by BitingBird 2015-01-03 00:49:15

  • Status changed from Rejected to Duplicate