Further study on my part reveals that forcing ipchains to use the interface of eth1:0 is not correct. The more I look at this issue, the less I understand the workings of ipmasq, (which I think does a very good job :-).
I need to retract my statement of the possible bug in ifconfig and I will wait for the knowledgeable answers. Thanks, -- Bill Quoting [EMAIL PROTECTED]: > Hello, > > I am finding a problem with my system in the interaction > between ifconfig and ipmasq, (enumerate-if specifically). > > System configuration- > Debian 2.1, (mostly) > Kernel 2.2.1 > eth0, internal 192.168.1.1 > eth1, external 206.xxx.xxx.xxx > eth1:0, internal 192.168.2.1 > > Problem, (feature?) > When ipmasq calls enumerate-if, eth1:0 is not returned as > an interface. This means ipchains rules are not run for > eth1:0. I have verified this manually by calling both > ifconfig and enumerate-if. The only way I can find to see > information on eth1:0, is to pass eth1:0 into ifconfig. > > I do not see a way to call ifconfig which will return ALL up > interfaces. > > My workaround is to call ipmasq and then to manually call > ipchains with the required settings. > > I do not know enough about ifconfig, but could this be a bug? > > I am open to other, (better?), workarounds if anyone else has > had this same experience. > > Thanks, > -- > Bill Bell > > > ----------------------------------------------------- > This mail sent through IMP: http://web.horde.org/imp/ > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < > /dev/null > > ----------------------------------------------------- This mail sent through IMP: http://web.horde.org/imp/
