View Issue Details

IDProjectCategoryView StatusLast Update
0000713Kali LinuxKali Package Bugpublic2025-07-14 09:36
ReporterSwift Assigned Tomuts  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionnot fixable 
Platformx86OSKaliOS Version1.0
Product Version1.0.4 
Summary0000713: Metasploit doesn't upgrade
Description

Metasploit does not upgrade after aptitude update && aptitude upgrade. Error:

Err http://http.kali.org/kali/ kali/main metasploit-framework i386 4.8.0-2013112001-1kali0
Connection failed [IP: 109.72.87.236 80]
Failed to fetch http://http.kali.org/kali/pool/main/m/metasploit-framework/metasploit-framework_4.8.0-2013112001-1kali0_i386.deb Connection failed [IP: 109.72.87.236 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Steps To Reproduce

aptitude update
aptitude upgrade

Additional Information

Sometimes does connect, mostly it doesn't. Is there another IP address to reroute to that works?

Activities

muts

muts

2013-11-27 12:39

reporter   ~0001095

Unable to reproduce. It might have been a temporary issue with one of our mirrors. Please reopen if the problem persists, after an apt-get update && apt-get upgrade.

Swift

Swift

2013-11-27 15:01

reporter   ~0001098

Unfortunately the issue is persistent (has been for 5-6 weeks now). This happens because I'm from the Netherlands and when upgrading Kali resolves to non working IP-addresses. This could be solved by resolving or rerouting to mainstream working IP-addresses for upgrades.

A work-around I'm using now is that I update through TOR-network. Because of different IP from endstation I get resolved to other working IP-addresses for upgrading.

rhertzog

rhertzog

2013-11-27 15:58

administrator   ~0001099

The 109.72.87.236 IP is mirror.pcextreme.nl, a mirror close to you. That mirror seems to be working fine, at least from the point of view of the mirror redirector that tests it regularly (both via rsync and via HTTP).

Maybe you should get in touch with your ISP to understand why the connection doesn't work ?

traceroute 109.72.87.236 might help to understand where it blocks. We could also ask the mirror operator if you can give us your own IP.

Swift

Swift

2013-11-27 17:55

reporter   ~0001100

traceroute to 109.72.87.236 (109.72.87.236), 30 hops max, 60 byte packets
1
2

3
4

5
6

7
8

9
10

11
12

13
14

15
16

17
18

19
20

21
22

23
24

25
26

27
28

29
30

rhertzog

rhertzog

2013-11-27 19:59

administrator   ~0001101

That traceroute is definitely not normal. You should get the answer of your immediate gateway in most cases. Are you sure that you don't have a firewall close to you that blocks the traffic to that host or the network it's part of?

In any case, you should get in touch with your network operator (or ISP) because it's not our fault...

Here's what it looks like from here:
$ traceroute 109.72.87.236
traceroute to 109.72.87.236 (109.72.87.236), 30 hops max, 60 byte packets
1 Freebox-Server.local (192.168.1.1) 0.453 ms 0.438 ms 0.634 ms
2 78.225.60.254 (78.225.60.254) 22.599 ms 24.258 ms 24.732 ms
3 213.228.22.126 (213.228.22.126) 26.605 ms
4 lyon-crs16-1-be1005.intf.routers.proxad.net (212.27.50.181) 34.516 ms 34.559 ms 34.559 ms
5 marseille-6k-1-po50.intf.routers.proxad.net (212.27.50.101) 38.781 ms 39.121 ms 39.147 ms
6 p11-crs16-1-be1102.intf.routers.proxad.net (78.254.249.89) 48.280 ms
7 bzn-crs16-2-be2000.intf.routers.proxad.net (78.254.250.125) 38.130 ms
8 te0-1-0-4.377.mag21.par01.atlas.cogentco.com (149.6.115.25) 50.525 ms te0-7-0-10.365.mag21.par01.atlas.cogentco.com (149.6.160.101) 78.256 ms te0-4-0-35.373.mag21.par01.atlas.cogentco.com (149.6.115.17) 77.517 ms
9 be2038.ccr21.par01.atlas.cogentco.com (154.54.74.253) 53.631 ms be2040.mpd21.par01.atlas.cogentco.com (154.54.78.37) 53.266 ms be2038.ccr21.par01.atlas.cogentco.com (154.54.74.253) 54.336 ms
10 te0-1-1-1.ccr22.ams03.atlas.cogentco.com (130.117.51.97) 91.577 ms te0-3-0-5.mpd22.ams03.atlas.cogentco.com (154.54.37.6) 64.592 ms te0-5-0-5.mpd22.ams03.atlas.cogentco.com (130.117.51.81) 91.511 ms
11 te1-1.ccr01.ams02.atlas.cogentco.com (154.54.60.134) 86.057 ms te3-1.ccr01.ams02.atlas.cogentco.com (154.54.60.126) 87.464 ms te2-1.ccr01.ams02.atlas.cogentco.com (154.54.60.130) 88.262 ms
12 149.11.80.66 (149.11.80.66) 59.712 ms 149.11.80.70 (149.11.80.70) 89.254 ms 149.11.80.66 (149.11.80.66) 61.029 ms
13 core2.ams02.pcextreme.nl (89.30.133.18) 91.787 ms 92.378 ms 94.436 ms
14 mpr2.ams02.pcextreme.nl (92.63.170.30) 91.448 ms 92.377 ms 93.114 ms
15 hosted.by.pcextreme (109.72.87.236) 93.498 ms 94.849 ms 85.558 ms

Issue History

Date Modified Username Field Change
2013-11-23 11:24 Swift New Issue
2013-11-27 12:39 muts Note Added: 0001095
2013-11-27 12:39 muts Status new => closed
2013-11-27 12:39 muts Assigned To => muts
2013-11-27 12:39 muts Resolution open => unable to reproduce
2013-11-27 15:01 Swift Note Added: 0001098
2013-11-27 15:01 Swift Status closed => feedback
2013-11-27 15:01 Swift Resolution unable to reproduce => reopened
2013-11-27 15:58 rhertzog Note Added: 0001099
2013-11-27 17:55 Swift Note Added: 0001100
2013-11-27 17:55 Swift Status feedback => assigned
2013-11-27 19:59 rhertzog Note Added: 0001101
2013-11-27 19:59 rhertzog Status assigned => closed
2013-11-27 19:59 rhertzog Resolution reopened => not fixable
2025-07-14 09:36 g0tmi1k Priority high => normal