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 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.
