Re: IPmasq from 2.0 to slink, and what about aliases..?
This may be a little blurry too :)
I had similar problems a couple months ago, decided that it was time to really
dig into IPCHAINS and eventually wrote my own firewall scripts. Figured it was
my ignorance and/or playing with the unstable branch. Interestingly enough I set
up dial-up system for a business (and boy do I wish the day when modems are
relics would arrive) recently and upgraded the kernel to 2.2 while staying
completely within stable branch. Same problem. However it was fixable by
running the ipmasq script again (which was happening for all of my ppp
connections anyway).
Dariush Pietrzak wrote:
> Hello,
> i'm not sure what to do about this, but i had problems with upgrade...
> i had impasq package installed and working.. then i upgraded system...
> everythink was going fine...until some day i've decided that it's about
> time to upgrade kernel and maybe few more things i've delayed not to
> reboot the system..
> The thing is..that although ipmasq upgrade removed ipmasq.conf files it
> left out some init.d/ entries and with that my system was fireing
> masqarade (old...from 2.0) without ipmasq.files... which led to denys on
> all interfaces in and out.. new ipmasq been fired before..
> Anyway.. this made me sick for couple of hours ..
> Maybe that's why i'm writing so strangely..
> .. so what i want is someone to tell me where can i find a list of such ee
> bugs? not to shout out about already solved problems..
> Another thing is that new ipmasq uses enumerate-interfaces or sth...
> causing messages in logs saying sth about non-existent eth0_1 interface
> instead of eth0:0
>
> Eeee. my message is somewhat blury.. hope I'll be able to ee describe my
> thoughts more clearly next time... sorry.
>
> --
> To UNSUBSCRIBE, email to debian-firewall-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: