On Wed, 2003-02-26 at 20:57, Florin wrote: > Hello again, > > eth1 should appear in the masq zone ... and not in the loc zone ... but > then you need an older kernel in order to have your masquerading working > because it's broken in the current kernel ... as I previously said.
Yes, I agree. Basically, the bug is: for some reason, with my setup, drakgw is generating a "loc eth1 detect" line in /etc/shorewall/interfaces which it shouldn't be. The masquerading stuff is unrelated, as you say. To be happy, I'd want current Cooker tested on a setup which matches mine exactly: yours doesn't because, as you say, you have four NICs :). Unfortunately this is my main working system and I can't afford the inconvenience and wasted time of installing Cooker from scratch on them, and I don't have any spare disk space to do a fresh installation without wiping my current one. Otherwise I'd do this test myself. > How come you have it duplicated ? ... I cannot reproduce that here ... I > have 4 nics and they are not duplicated ... I DON'T KNOW!!! That's the whole bug! That's what I've been going on about for days! :). I *WANT* to know why drakgw is generating the loc entry. It shouldn't be. > Drakgw displays your Nics ? which ones ? and what do you select ? > is this the automatic drakgw configuration or the expert mode one (this is > what I have chosen) ... drakgw correctly detects that only my eth1 interface faces the local network, and configures it. Whether I choose automatic or expert mode doesn't matter, it generates the same faulty /etc/shorewall/interfaces file. -- adamw
