Bug 12432

Summary:	upgrade with network repositories sends martian requests to 127.0.0.1
Product:	Mageia	Reporter:	Robert Munro <ramunro>
Component:	Installer	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	High	CC:	doktor5000
Version:	3	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
URL:	https://forums.mageia.org/en/viewtopic.php?f=8&t=6819
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Robert Munro 2014-01-25 15:50:28 CET

The installer upgrade process from Mageia2 to Mageia3 with network repositories selected sends many martian requests on the internet interface directed to the loopback address 127.0.0.1 attempting to contact the network repositories.

It appears that these requests are trying to access local repositories on the same system that's being upgraded, but in that case they should be directed to the loopback interface "lo" instead of the internet interface "eth0".

A gateway firewall machine running an iptables firewall with /proc/sys/net/ipv4/conf/<int_iface>/log_martians set to 1 will catch these errors and log them to syslog.

These martian requests timeout, however that takes time for each one, and it slows down the upgrade processing considerably.

This doesn't occur during the Mageia3 install process with network repositories selected, but only during Mageia3 upgrade processing, so the install processing completes much faster.

Comment 1 Florian Hubold 2014-02-02 18:55:16 CET

Also see https://forums.mageia.org/en/viewtopic.php?f=8&t=6819 for more information.

Priority: Normal => High
URL: (none) => https://forums.mageia.org/en/viewtopic.php?f=8&t=6819
CC: (none) => doktor5000
Severity: minor => major

Comment 2 Robert Munro 2014-02-02 19:43:41 CET

Since the upgrade with network repositories tries to access a local mirror, in addition to directing those network requests to the real loopback interface "lo" instead of the external interface, I'd suggest that before it begins the upgrade process should set a flag on to look for a local mirror, then reset the flag off if it doesn't find a local mirror for the first package it checks, so it doesn't keep trying to find a local mirror for all packages. This will still accommodate developers who maintain local mirrors while not slowing upgrades for the majority of users who don't.

Comment 3 Manuel Hiebel 2014-02-02 19:46:58 CET

maybe this is fixed since, in the installer of mageia 4 ?

Assignee: bugsquad => thierry.vignaud

Comment 4 Dick Gevers 2014-11-16 09:24:46 CET

@ramunro@speakeasy.net or anyone else: installers of m3 and m4 will not change anymore.

Please advise if this is current with 5beta1? Otherwise we regret it has to be closed as OLD.

Keywords: (none) => NEEDINFO

Comment 5 Marja Van Waes 2015-03-31 16:03:53 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD