Description of problem: With Mageia 3 beta 3, I want to share my Internet connection with other machines using drakgw, so I run drakgw as I did in Mageia 2, but the result is that I cannot connect to Internet from any of the two PCs. I am able to connect from one PC to the other using ssh, but the Internet connection doesn't work on any of them (it stops working on the PC which is directly connected to Internet). Also in Mageia 2, opening again drakgw gave the choice to disable the network sharing, while in Mageia 3 beta 3 it wants to configure again the connection. As I can't disable it, the only way I found to recover Internet is disabling the firewall. How reproducible: Always Steps to Reproduce: 1. Go to MCC -> Network & Internet -> Share the Internet connection with other local machines 2. Configure the network sharing. Before this you may need to configure the firewall so the wlan adapter is protected by the firewall and the ethernet adapter is not protected. 3. Check your Internet connection. I noticed that from one PC I can connect to the other using ssh, but Internet is not working. 4. Open again drakgw and it won't offer to disable the network sharing. To recover Internet you have to disable the firewall. Reproducible: Steps to Reproduce:
was it working before the last update ?
No it wasn't. I remember having tried with beta 1 or 2 and it also didn't work.
Assignee: bugsquad => mageia
I have the opposit problem. It would work with all betas and RC's But I can't get it to work with Official Release of 3 I had to switch my server back to Mageia 2 and I'm putting off upgrading 6 other due to this problem.
CC: (none) => rbcourt
I can't test with Mageia 3 final because the firewall configuration tool seems to be broken. I cannot configure my firewall properly, I can't check which network interfaces I want to protect or not, so drakgw says that there is no adapter available.
After reading the Errata I was able to get past the point of selecting which network to protect. It still didn't work.
I tried again following the information from the errata. The behavior has changed a bit: The PC connected directly to Internet now works well, but the secondary PC is still not seeing Internet. I still can connect from one to other using ssh.
Since I have quadruple boots I install pc-linux-os 64 bit. (Which I believe is taken from Mageia anyways) When Mageia get this fixed I will start using Mageia again.
With Mageia 3 updated until today, I want to share my Internet connection with other machines using drakgw, so I run drakgw and set my fist machine with IP 192.168.2.1 Netmask 255.255.255.0 Gateway 192.168.2.1 get DNS from DHCP and the second machine with IP 192.168.2.2 Netmask 255.255.255.0 Gateway 192.168.2.1 I share the connection, my shorewall is (/etc/shorewall/interfaces) net ppp0 detect where ppp0 is my internet connection and eth0 my lan (see bug https://bugs.mageia.org/show_bug.cgi?id=5596) I am able to connect from one PC to the other using ping, but the Internet connection doesn't work on any of them (it stops working on the PC which is directly connected to Internet). If I want to restart the Internet connection i must to disconnect the ethernet wired from my fist machine but ping from one pc to the other fails.
CC: (none) => kensan
Bug confirmed in Mageia 4 beta 1. The behaviour is the described in comment 8.
Is this still valid in Mageia 4 with all updates installed? In Mageia 5RC (due in a few days)?
Keywords: (none) => NEEDINFO
Still valid with Mageia 5 RC fully updated
Works for me in Mageia 5 Cauldron
Works for Robert, bug for Perilio, there must be differences in your setups probably.
Keywords: NEEDINFO => (none)Whiteboard: (none) => MGA4TOO MGA5TOO FOR_ERRATA
I identified two issues: 1-) In the first step, when it asks for the local IP address, by default it was written 192.168.1.1, which is the same of my router. That is what made my direct conected laptop not work (I guess). I noticed it in my second attempt on configuring it because it showed a message saying something like: "Potential conflict in the local network address found in the configuration of wlp20s0! (translated from spanish)". However, I am sure that this message did not appear on my first try, but it should have. 2-) dhcpd is not started unless the ethernet wire is conected, so the secondary device was not getting a IP address. I do not know if this is the normal behaviour. Thanks. For me this bug is solved
I found out years ago by trial and error you can't have the same ip range on both sides of the firewall/router. I also noted that most of the routers I 've worked with use the 192.168 range. So on my internel network I use 10.0 as the address range. This is since the Mandrake days! Yes Mandrake.
Hi Perilio and Robert (and others), Thanks for the feedback :-) So, IIUC, this is fixed in pre-Mageia5, but we should expand http://doc.mageia.org/mcc/5/en/content/drakgw.html WDYT about adding the following as note just above "Configure the client": "Please keep in mind that ip addresses need to be unique, like phone numbers. So if the gateway is connected to a modem/router that supplies ip addresses in the 192.168.*.* range, then it is safer to let your gateway computer use a 10.0.*.* range, if you set it act as DHCP server." (CC'ing docteam)
Keywords: (none) => USABILITYCC: (none) => doc-bugs, marja11Version: Cauldron => 4Whiteboard: MGA4TOO MGA5TOO FOR_ERRATA => FOR_ERRATA
s/it act/it to act/
For me this bug is solved, but: I tried again with a liveCD, and the first time I configure the network sharing it does not show the error message about the conflict with the IPs. This message is shown when I use drakgw to configure the sharing for a second time once I have configured it previously. Someone should have a look into this issue.
I've never gotten an error message for the same range of ips's on eacjh side.
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 => RESOLVEDResolution: (none) => OLD