Solved [Solved] fetch hangs on VM VirtualBox - 9.2 RELEASE

Hi all.

I tried hard NOT to post this question, but I don't seem to be able to find any more info to solve this myself.

I am running a 9.2 RELEASE on win 7 x64, using VM VirtualBox 4.3.12 (latest), that I have just installed.
It is a fresh installation, without anything modified. The purpose is to test whether fetch will hang again as it did in my previous 8.3 amd64 installataion.

I have set a bridged connection.

# uname -a

Code:
FreeBSD rev64 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Thu Sep 26 22:50:31 UTC 2013     root@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64


# ifconfig -a

Code:
em0: flags=28943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,PPROMISC> metric 0 mtu 1500
        options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
        ether 08:00:27:0b:41:2d
        inet6 fe80::a00:27ff:fe0b:412d%em0 prefixlen 64 scopeid 0x1
        inet 192.168.1.67 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>


Box's IP is 192.168.1.67, my router's IP is 192.168.1.254.
# netstat -rn

Code:
Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
default            192.168.1.254      UGS         0       13    em0
127.0.0.1          link#3             UH          0        0    lo0
192.168.1.0/24     link#1             U           0      252    em0
192.168.1.67       link#1             UHS         0        0    lo0

Internet6:
Destination                       Gateway                       Flags      Netif Expire
::/96                             ::1                           UGRS        lo0
::1                               link#3                        UH          lo0
::ffff:0.0.0.0/96                 ::1                           UGRS        lo0
fe80::/10                         ::1                           UGRS        lo0
fe80::%em0/64                     link#1                        U           em0
fe80::a00:27ff:fe0b:412d%em0      link#1                        UHS         lo0
fe80::%lo0/64                     link#3                        U           lo0
fe80::1%lo0                       link#3                        UHS         lo0
ff01::%em0/32                     fe80::a00:27ff:fe0b:412d%em0  U           em0
ff01::%lo0/32                     ::1                           U           lo0
ff02::/16                         ::1                           UGRS        lo0
ff02::%em0/32                     fe80::a00:27ff:fe0b:412d%em0  U           em0
ff02::%lo0/32                     ::1                           U           lo0


I try nslookup.
# nslookup google.com

Code:
Server:         192.168.1.254
Address:        192.168.1.254#53

Non-authoritative answer:
Name:   google.gr
Address: 173.194.40.31
Name:   google.gr
Address: 173.194.40.15
Name:   google.gr
Address: 173.194.40.23
Name:   google.gr
Address: 173.194.40.24


I run ping to see what happens.
# ping -c4 google.com

Code:
PING google.com (74.125.232.128): 56 data bytes
64 bytes from 74.125.232.128: icmp_seq=0 ttl=54 time=75.902 ms
64 bytes from 74.125.232.128: icmp_seq=1 ttl=54 time=74.734 ms
64 bytes from 74.125.232.128: icmp_seq=2 ttl=54 time=70.678 ms
64 bytes from 74.125.232.128: icmp_seq=3 ttl=54 time=75.034 ms

--- google.com ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 70.678/74.087/75.902/2.014 ms


Now comes the interesting part. I try fetch.
# fetch [url=http://google.com]http://google.com[/url]
or specific file download
# fetch [url=http://code.jquery.com/jquery-1.11.1.js]http://code.jquery.com/jquery-1.11.1.js[/url]

Nothing seems to happen here. As soon as I press "enter", a new blank line appears in the console and stays there forever.

Different example.
# portsnap fetch update

Code:
Looking up portsnap.FreeBSD.org mirrors... none found.
Fetching public key from portsnap.FreeBSD.org... failed.
No mirrors remaining, giving up.


If I press 3 times Ctrl+T swhen fetch is hanged, I get the following output:

Code:
load: 0.05  cmd: fetch 4735 [connec] 1.43r 0.00u 0.00s 0% 3536k
load: 0.04  cmd: fetch 4735 [connec] 11.54r 0.00u 0.00s 0% 3536k
load: 0.04  cmd: fetch 4735 [connec] 18.56r 0.00u 0.00s 0% 3536k

That's all the info I can think of writting now. If anything else would help, please ask me. I would be glad if someone could help me solve this one. Why fetch hangs while all other network stuff works OK?
 
Re: fetch hangs on VM VirtualBox - 9.2 RELEASE

Ok, I solved it.

It was Avast Internet Security's firewall that was blocking it. I didn't think to check it at first, since I had added certain rules to allow VirtualBox networking. Apparently, no rules are needed for that. "Internet Connection Sharing mode" must be checked in firewall configuration -> options. That fixed the problem.
 
Back
Top