VM apt-get install - a rede está inacessível

2

Eu tenho um Ubuntu VM suportado pelo Vagrant, no qual estou tentando fazer alguns testes de desempenho. Para fazer isso, estou tentando instalar o gdb

Quando executo o apt-get install, vejo o seguinte:

vagrant@ubuntu-1204:~$ sudo apt-get install gdb
sudo: /etc/sudoers.d/vagrant is mode 0644, should be 0440
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  libpython2.7 python2.7 python2.7-minimal
Suggested packages:
  gdb-doc gdbserver python2.7-doc binfmt-support
The following NEW packages will be installed:
  gdb libpython2.7
The following packages will be upgraded:
  python2.7 python2.7-minimal
2 upgraded, 2 newly installed, 0 to remove and 74 not upgraded.
Need to get 7,915 kB of archives.
After this operation, 9,836 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
WARNING: The following packages cannot be authenticated!
  python2.7 python2.7-minimal libpython2.7 gdb
Install these packages without verification [y/N]? y
Err http://us.archive.ubuntu.com/ubuntu/ precise-updates/main python2.7 amd64 2.7.3-0ubuntu3.8
  Could not connect to 192.168.0.0:59875 (192.168.0.0). - connect (101: Network is unreachable)
Err http://us.archive.ubuntu.com/ubuntu/ precise-updates/main gdb amd64 7.4-2012.04-0ubuntu2.1
  Unable to connect to 192.168.0.0:59875:
Err http://security.ubuntu.com/ubuntu/ precise-security/main python2.7 amd64 2.7.3-0ubuntu3.8
  Could not connect to 192.168.0.0:59875 (192.168.0.0). - connect (101: Network is unreachable)
Err http://security.ubuntu.com/ubuntu/ precise-security/main python2.7-minimal amd64 2.7.3-0ubuntu3.8
  Unable to connect to 192.168.0.0:59875:
Err http://security.ubuntu.com/ubuntu/ precise-security/main libpython2.7 amd64 2.7.3-0ubuntu3.8
  Unable to connect to 192.168.0.0:59875:
Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7_2.7.3-0ubuntu3.8_amd64.deb  Could not connect to 192.168.0.0:59875 (192.168.0.0). - connect (101: Network is unreachable)
Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7-minimal_2.7.3-0ubuntu3.8_amd64.deb  Unable to connect to 192.168.0.0:59875:
Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/p/python2.7/libpython2.7_2.7.3-0ubuntu3.8_amd64.deb  Unable to connect to 192.168.0.0:59875:
Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/g/gdb/gdb_7.4-2012.04-0ubuntu2.1_amd64.deb  Unable to connect to 192.168.0.0:59875:
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Até onde eu sei, há alguma configuração de rede ausente, mas estou perdendo um pouco onde. Eu posso pingar google.com e obter uma resposta bem-sucedida, então estou um pouco intrigado porque o security.ubuntu.com parece estar saindo em 192.168.0.0

Isso é o que eu vejo para ifconfig

eth0      Link encap:Ethernet  HWaddr 08:00:27:0a:49:50  
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe0a:4950/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1134 errors:0 dropped:0 overruns:0 frame:0
          TX packets:914 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:147105 (147.1 KB)  TX bytes:523962 (523.9 KB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:208 errors:0 dropped:0 overruns:0 frame:0
          TX packets:208 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:10871 (10.8 KB)  TX bytes:10871 (10.8 KB)

Qualquer ajuda seria muito apreciada!

UPDATE

Tentei adicionar

config.vm.network "public_network", bridge: [
    "en0: Wi-Fi",
    "en3: Thunderbolt"
]

Mas o problema persiste.

Aqui está a tabela de roteamento:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         10.0.2.2        0.0.0.0         UG    100    0        0 eth0
10.0.2.0        *               255.255.255.0   U     0      0        0 eth0
10.9.100.0      *               255.255.255.0   U     0      0        0 eth1

Eu também tentei fazer ping nos servidores Ubuntu, o que parece ótimo:

PING us.archive.ubuntu.com (91.189.91.24) 56(84) bytes of data.
64 bytes from economy.canonical.com (91.189.91.24): icmp_req=1 ttl=63 time=84.5 ms
64 bytes from economy.canonical.com (91.189.91.24): icmp_req=2 ttl=63 time=84.8 ms
64 bytes from economy.canonical.com (91.189.91.24): icmp_req=3 ttl=63 time=84.5 ms
64 bytes from economy.canonical.com (91.189.91.24): icmp_req=4 ttl=63 time=85.1 ms
64 bytes from economy.canonical.com (91.189.91.24): icmp_req=5 ttl=63 time=83.9 ms
64 bytes from economy.canonical.com (91.189.91.24): icmp_req=6 ttl=63 time=84.3 ms
64 bytes from economy.canonical.com (91.189.91.24): icmp_req=7 ttl=63 time=84.3 ms
64 bytes from economy.canonical.com (91.189.91.24): icmp_req=8 ttl=63 time=84.4 ms
64 bytes from economy.canonical.com (91.189.91.24): icmp_req=9 ttl=63 time=84.5 ms
64 bytes from economy.canonical.com (91.189.91.24): icmp_req=10 ttl=63 time=84.5 ms
64 bytes from economy.canonical.com (91.189.91.24): icmp_req=11 ttl=63 time=83.9 ms
64 bytes from economy.canonical.com (91.189.91.24): icmp_req=12 ttl=63 time=84.7 ms
64 bytes from economy.canonical.com (91.189.91.24): icmp_req=13 ttl=63 time=84.8 ms
64 bytes from economy.canonical.com (91.189.91.24): icmp_req=14 ttl=63 time=83.8 ms
^C
--- us.archive.ubuntu.com ping statistics ---
15 packets transmitted, 14 received, 6% packet loss, time 14024ms
rtt min/avg/max/mdev = 83.827/84.460/85.102/0.499 ms
    
por timothyclifford 18.08.2015 / 10:44

2 respostas

3

O Vagrant usa o VirtualBox. Então, vá para a sua instância e verifique se a sua placa de rede está corretamente conectada. Você pode configurar isso no seu Vagrantfile. Por exemplo, minha linha do meu Macbook conecta a rede à minha placa WLAN.

server.vm.network "public_network", bridge:'en0: WLAN (AirPort)'

talvez essa ajuda para o seu problema.

link

Verifique suas configurações do VBox. Se houver uma ponte de rede correta.

Você definiu outro gateway? Talvez faça uma nova instância e verifique se isso está funcionando. Talvez você tenha um erro de configuração em seu gerenciador de pacotes.

    
por 18.08.2015 / 11:14
2

O estranho é que o apt-get está conectando 192.168.0.0:59875.

Você está usando algum proxy para o apt-get?

Verifique isso com:

$ apt-config dump Acquire::http::Proxy
$ echo $http_proxy
    
por 18.08.2015 / 16:14