| Summary: | MCC is not able to configure gateway function. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Ole Reier Ulland <ole.reier.ulland> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | cooker, eeeemail, jarillon, mageia, rbcourt, thierry.vignaud |
| Version: | 4 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakx-net | CVE: | |
| Status comment: | |||
|
Description
Ole Reier Ulland
2014-10-24 00:52:44 CEST
Johnny A. Solbu
2014-10-24 00:53:01 CEST
CC:
(none) =>
cooker
claire robinson
2014-10-24 10:33:00 CEST
CC:
(none) =>
eeeemail Thierry, Colin could this be related to the new interface naming? CC:
(none) =>
mageia, thierry.vignaud
Pierre Jarillon
2014-10-24 11:36:09 CEST
CC:
(none) =>
jarillon Also See Bugs 12542 and 12883 CC:
(none) =>
rbcourt The issue is in http://gitweb.mageia.org/software/drakx-net/tree/bin/drakgw#n126 Can you add the following line before lines 132, 130 & 128? use Data::Dumper, warn Dumper $shorewall->{loc_zone}; Then rerun the tool from a terminal and attach (not paste) the resulting /tmp/drakgw.txt file to this bug report dragw 2>&1|tee /tmp/drakgw.txt Keywords:
(none) =>
NEEDINFO To me it looks like I need to be a developer and a package builder to do what you want me to do. I am neither and do not understand the instructions. However, I have installed Mageia 4.1 on a different computer to take the place of the computer in question here, as a gateway between USB-mobile modem and ethernet with other computers. The result now, after updates, from MCC - âShare the Internet connection with other local machinesâ was that the routing and nat functions work, but "bind" was installed, and that did not work. When I uninstalled "bind" and installed "dnsmasq" in its place the computer started functioning as a gateway without the need of this script. I also should add that the former computer was a 32-bit and this last one is a 64-bit. I have now done an experiment, I updated the 32-bit computer, removed the script from it, and configured with MCC. It does work as a gateway when I tested with a third computer. But the problem with "bind" persists, I also made sure that the "named" process was running. Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Status:
NEW =>
RESOLVED |