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 eth0 detect masq eth1 detect loc eth1 detect 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.
