View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000713 | Kali Linux | Kali Package Bug | public | 2013-11-23 11:24 | 2025-07-14 09:36 |
| Reporter | Swift | Assigned To | muts | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | not fixable | ||
| Platform | x86 | OS | Kali | OS Version | 1.0 |
| Product Version | 1.0.4 | ||||
| Summary | 0000713: 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 | ||||
| Steps To Reproduce | aptitude update | ||||
| Additional Information | Sometimes does connect, mostly it doesn't. Is there another IP address to reroute to that works? | ||||
|
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. |
|
|
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. |
|
|
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. |
|
|
traceroute to 109.72.87.236 (109.72.87.236), 30 hops max, 60 byte packets |
|
|
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: |
|
| 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 |