[Cooker] [Bug 1952] [drakxtools] drakgw doesn't work due to configuring shorewall incorrectly
http://qa.mandrakesoft.com/show_bug.cgi?id=1952 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-03-13 15:23 --- My particular problem has been fixed by the latest drakxtools, thanks Florin! Thus I'm closing this bug. Others with similar problems should try latest drakxtools - I just uninstalled shorewall and deleted (well, moved it to a backup dir, actually) the /etc/shorewall directory, then ran drakgw and let it install shorewall and configure it, and it generated a valid config this time. So try that. If you still have trouble, open a new bug. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: RESOLVED creation_date: description: I hope this isn't due to a stale config anywhere (I've been running Cooker since before 9.0). On my system, drakgw currently doesn't work. It runs fine and reports success, but the shorewall settings it creates are wrong and break shorewall. It creates a /etc/shorewall/interfaces file with this lines (among all the comments): net eth0detect masqeth1detect loc eth1detect This is invalid according to the comments in the same file, which state that you can only specify each interface *once* in the interfaces file. If a single interface needs to use multiple zones, as seems to be the case, it says these need to be defined in /etc/shorewall/hosts and the zone for the interface should be set to -. The upshot of all this is that the shorewall service does not start, complaining about the multiple instances of eth1 in the /etc/shorewall/interfaces file. This makes internet connection sharing configuration impossible and may break existing setups, which is a severe problem, IMO. I have confirmed this with several ways of setting up internet connection sharing. At first I set up the firewall first then configured ICS, then I removed shorewall entirely and attempted to set up ICS without configuring the firewall. The resulting /etc/interfaces files was the same in both cases, and did not work.
[Cooker] [Bug 1952] [drakxtools] drakgw doesn't work due to configuring shorewall incorrectly
http://qa.mandrakesoft.com/show_bug.cgi?id=1952 --- Additional Comments From [EMAIL PROTECTED] 2003-03-13 02:11 --- I thought the masq detect detect line was suspect too. Here is my configuration. Eth0 is a Dlink530? via rhine, and eth1 is a netgear? via natsemi. Eth0 is my net connection and Eth1 is connected to my LAN. I manually set eth1's IP to 192.168.1.1. Eth0 pulls an IP via dhcp from my cable modem. My hub supports 5 computers, but the most I have connected at once is three. One other desktop and maybe a laptop. Those computers usually have IP addresses of 192.168.1.253 and 192.168.1.252. That is what they get via dhcp. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: I hope this isn't due to a stale config anywhere (I've been running Cooker since before 9.0). On my system, drakgw currently doesn't work. It runs fine and reports success, but the shorewall settings it creates are wrong and break shorewall. It creates a /etc/shorewall/interfaces file with this lines (among all the comments): net eth0detect masqeth1detect loc eth1detect This is invalid according to the comments in the same file, which state that you can only specify each interface *once* in the interfaces file. If a single interface needs to use multiple zones, as seems to be the case, it says these need to be defined in /etc/shorewall/hosts and the zone for the interface should be set to -. The upshot of all this is that the shorewall service does not start, complaining about the multiple instances of eth1 in the /etc/shorewall/interfaces file. This makes internet connection sharing configuration impossible and may break existing setups, which is a severe problem, IMO. I have confirmed this with several ways of setting up internet connection sharing. At first I set up the firewall first then configured ICS, then I removed shorewall entirely and attempted to set up ICS without configuring the firewall. The resulting /etc/interfaces files was the same in both cases, and did not work.
[Cooker] [Bug 1952] [drakxtools] drakgw doesn't work due to configuring shorewall incorrectly
http://qa.mandrakesoft.com/show_bug.cgi?id=1952 --- Additional Comments From [EMAIL PROTECTED] 2003-03-09 15:49 --- having the same problem with yesterday's cookerversion. (08-03-2003) --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I hope this isn't due to a stale config anywhere (I've been running Cooker since before 9.0). On my system, drakgw currently doesn't work. It runs fine and reports success, but the shorewall settings it creates are wrong and break shorewall. It creates a /etc/shorewall/interfaces file with this lines (among all the comments): net eth0detect masqeth1detect loc eth1detect This is invalid according to the comments in the same file, which state that you can only specify each interface *once* in the interfaces file. If a single interface needs to use multiple zones, as seems to be the case, it says these need to be defined in /etc/shorewall/hosts and the zone for the interface should be set to -. The upshot of all this is that the shorewall service does not start, complaining about the multiple instances of eth1 in the /etc/shorewall/interfaces file. This makes internet connection sharing configuration impossible and may break existing setups, which is a severe problem, IMO. I have confirmed this with several ways of setting up internet connection sharing. At first I set up the firewall first then configured ICS, then I removed shorewall entirely and attempted to set up ICS without configuring the firewall. The resulting /etc/interfaces files was the same in both cases, and did not work.
[Cooker] [Bug 1952] [drakxtools] drakgw doesn't work due to configuring shorewall incorrectly
http://qa.mandrakesoft.com/show_bug.cgi?id=1952 --- Additional Comments From [EMAIL PROTECTED] 2003-03-07 16:20 --- So it seems this isn't just happening for me :(. Could the other people who get duplicate lines please vote for the bug so it gets confirmed? And could you also post precise details of your networking setups - how many machines, how they are connected (which interfaces connect which machines), how the host machine connects to the internet, and the relevant IP addresses - to help Florin? Apparently it doesn't happen on his test setup, so it must be something to do with the setup that's causing it. My setup is just two machines, and all the connections are made by NICs - the host machine connects to the internet via one, eth0, and it connects to the other machine via another, eth1. To the guy who doesn't get a duplicate line, that file still looks suspect to me. It ought to put the interface that's connected to the internet in the NET zone and the interfaces that want to share it in the MASQ zone. I particularly don't like the look of that masq detect detect line. What do you think, Florin? --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I hope this isn't due to a stale config anywhere (I've been running Cooker since before 9.0). On my system, drakgw currently doesn't work. It runs fine and reports success, but the shorewall settings it creates are wrong and break shorewall. It creates a /etc/shorewall/interfaces file with this lines (among all the comments): net eth0detect masqeth1detect loc eth1detect This is invalid according to the comments in the same file, which state that you can only specify each interface *once* in the interfaces file. If a single interface needs to use multiple zones, as seems to be the case, it says these need to be defined in /etc/shorewall/hosts and the zone for the interface should be set to -. The upshot of all this is that the shorewall service does not start, complaining about the multiple instances of eth1 in the /etc/shorewall/interfaces file. This makes internet connection sharing configuration impossible and may break existing setups, which is a severe problem, IMO. I have confirmed this with several ways of setting up internet connection sharing. At first I set up the firewall first then configured ICS, then I removed shorewall entirely and attempted to set up ICS without configuring the firewall. The resulting /etc/interfaces files was the same in both cases, and did not work.
[Cooker] [Bug 1952] [drakxtools] drakgw doesn't work due to configuring shorewall incorrectly
http://qa.mandrakesoft.com/show_bug.cgi?id=1952 --- Additional Comments From [EMAIL PROTECTED] 2003-03-06 22:20 --- This bug is still valid. I use mdk9.1 rc2 (installed with ios1 on hd and hd.iso on floppy) and downloaded shorewall and etc today (6 march) from cooker. Shorewall wouldn't start beacause puplicate enteries in /etc/shorewall/interfaces I removed one line (loc eth1 detect) and everything worked just fine. drakxtools-9.1-11mdk shorewall-1.3.14-3mdk Regards, Ola A --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I hope this isn't due to a stale config anywhere (I've been running Cooker since before 9.0). On my system, drakgw currently doesn't work. It runs fine and reports success, but the shorewall settings it creates are wrong and break shorewall. It creates a /etc/shorewall/interfaces file with this lines (among all the comments): net eth0detect masqeth1detect loc eth1detect This is invalid according to the comments in the same file, which state that you can only specify each interface *once* in the interfaces file. If a single interface needs to use multiple zones, as seems to be the case, it says these need to be defined in /etc/shorewall/hosts and the zone for the interface should be set to -. The upshot of all this is that the shorewall service does not start, complaining about the multiple instances of eth1 in the /etc/shorewall/interfaces file. This makes internet connection sharing configuration impossible and may break existing setups, which is a severe problem, IMO. I have confirmed this with several ways of setting up internet connection sharing. At first I set up the firewall first then configured ICS, then I removed shorewall entirely and attempted to set up ICS without configuring the firewall. The resulting /etc/interfaces files was the same in both cases, and did not work.
[Cooker] [Bug 1952] [drakxtools] drakgw doesn't work due to configuring shorewall incorrectly
http://qa.mandrakesoft.com/show_bug.cgi?id=1952 --- Additional Comments From [EMAIL PROTECTED] 2003-03-06 23:10 --- Olaf, in my case there is not such a line duplicate, those are the last lines of the file interfaces: net ppp+ detect masq detect detect loc eth0 detect loc eth1 detect It seems is another file the one that disable internet when I activate at least one of the shorewall options :-( file:///usr/share/doc/HTML/index.html El Jueves, 6 de Marzo de 2003 22:20, mnomn escribió: --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I hope this isn't due to a stale config anywhere (I've been running Cooker since before 9.0). On my system, drakgw currently doesn't work. It runs fine and reports success, but the shorewall settings it creates are wrong and break shorewall. It creates a /etc/shorewall/interfaces file with this lines (among all the comments): net eth0detect masqeth1detect loc eth1detect This is invalid according to the comments in the same file, which state that you can only specify each interface *once* in the interfaces file. If a single interface needs to use multiple zones, as seems to be the case, it says these need to be defined in /etc/shorewall/hosts and the zone for the interface should be set to -. The upshot of all this is that the shorewall service does not start, complaining about the multiple instances of eth1 in the /etc/shorewall/interfaces file. This makes internet connection sharing configuration impossible and may break existing setups, which is a severe problem, IMO. I have confirmed this with several ways of setting up internet connection sharing. At first I set up the firewall first then configured ICS, then I removed shorewall entirely and attempted to set up ICS without configuring the firewall. The resulting /etc/interfaces files was the same in both cases, and did not work.
[Cooker] [Bug 1952] [drakxtools] drakgw doesn't work due to configuring shorewall incorrectly
http://qa.mandrakesoft.com/show_bug.cgi?id=1952 --- Additional Comments From [EMAIL PROTECTED] 2003-03-07 01:24 --- In Mandrake 9.0, I had the exact problem you are regarding duplicate interfaces being listed in /etc/shorewall/interfaces. I implemented the same solution in 9.0. In RC 2, I couldn't even connect to the net. The only reason I have net access at this point is because I have my pc set to dual boot between xp/mandrake. In RC 1 I had access, but no sharing of net access to my LAN. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I hope this isn't due to a stale config anywhere (I've been running Cooker since before 9.0). On my system, drakgw currently doesn't work. It runs fine and reports success, but the shorewall settings it creates are wrong and break shorewall. It creates a /etc/shorewall/interfaces file with this lines (among all the comments): net eth0detect masqeth1detect loc eth1detect This is invalid according to the comments in the same file, which state that you can only specify each interface *once* in the interfaces file. If a single interface needs to use multiple zones, as seems to be the case, it says these need to be defined in /etc/shorewall/hosts and the zone for the interface should be set to -. The upshot of all this is that the shorewall service does not start, complaining about the multiple instances of eth1 in the /etc/shorewall/interfaces file. This makes internet connection sharing configuration impossible and may break existing setups, which is a severe problem, IMO. I have confirmed this with several ways of setting up internet connection sharing. At first I set up the firewall first then configured ICS, then I removed shorewall entirely and attempted to set up ICS without configuring the firewall. The resulting /etc/interfaces files was the same in both cases, and did not work.
[Cooker] [Bug 1952] [drakxtools] drakgw doesn't work due to configuring shorewall incorrectly
https://qa.mandrakesoft.com/show_bug.cgi?id=1952 --- Additional Comments From [EMAIL PROTECTED] 2003-02-21 19:53 --- Still valid with updated shorewall and drakxtools as per previous comment. I hope someone is working on this, it's very important, especially as it *appears* to work and provides no feedback on what it's doing. This would completely baffle a newbie. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I hope this isn't due to a stale config anywhere (I've been running Cooker since before 9.0). On my system, drakgw currently doesn't work. It runs fine and reports success, but the shorewall settings it creates are wrong and break shorewall. It creates a /etc/shorewall/interfaces file with this lines (among all the comments): net eth0detect masqeth1detect loc eth1detect This is invalid according to the comments in the same file, which state that you can only specify each interface *once* in the interfaces file. If a single interface needs to use multiple zones, as seems to be the case, it says these need to be defined in /etc/shorewall/hosts and the zone for the interface should be set to -. The upshot of all this is that the shorewall service does not start, complaining about the multiple instances of eth1 in the /etc/shorewall/interfaces file. This makes internet connection sharing configuration impossible and may break existing setups, which is a severe problem, IMO. I have confirmed this with several ways of setting up internet connection sharing. At first I set up the firewall first then configured ICS, then I removed shorewall entirely and attempted to set up ICS without configuring the firewall. The resulting /etc/interfaces files was the same in both cases, and did not work.
