From: Arnt Karlsen <arnt@c2i.net>
To: "P.Italiaander" <pc-secure@home.nl>
Cc: netfilter@lists.netfilter.org
Subject: Re: NOT acceptable "/etc/sysconfig/network-scripts/ifup" script !!!
Date: Thu, 15 May 2003 19:48:43 +0200 [thread overview]
Message-ID: <20030515194843.6c8876f2.arnt@c2i.net> (raw)
In-Reply-To: <200305151742.26913.pc-secure@home.nl>
On Thu, 15 May 2003 17:42:26 +0200,
"P.Italiaander" <pc-secure@home.nl> wrote in message
<200305151742.26913.pc-secure@home.nl>:
> Op donderdag 15 mei 2003 14:52, schreef Arnt Karlsen:
>
> > ..I know, ipup _is_ buggy, my hint was more on Red Hats somewhat
> > sloppy QA attitude. I mean, if I should _not_ use RH9 to route
> > traffic, I would like to know _that_ from the docs.
> >
> > ..does Mandrake or Debian turn their rear end onto _whoever_ like
> > RH-9 does in
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=89171 ???
>
>
> I've checked , but Mandrake 9.1 is not effected with that bug.
> Thanks for mention it.
> On Debian i don't know ,don't have it , i use OpenBSD en Linux SuSe ,
> Redhat ,Mandrake.
>
> Does anyone have tested yet, my patched /sbin/ifup file, for
> iptables-script ??
..the wifi part of it works fine, but it _introduces_ bug # 89171,
I tested with a thinkpad 760 ED I use as AP, it runs RH-7.3.
..it looks like Red Hat cannot use mac addresses to ID nics.
--
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
next prev parent reply other threads:[~2003-05-15 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 19:55 NOT acceptable "/etc/sysconfig/network-scripts/ifup" script !!! P.Italiaander
2003-05-14 21:16 ` Arnt Karlsen
2003-05-15 0:15 ` P.Italiaander
2003-05-15 12:52 ` Arnt Karlsen
2003-05-15 15:42 ` P.Italiaander
2003-05-15 17:48 ` Arnt Karlsen [this message]
2003-05-15 19:46 ` P.Italiaander
2003-05-16 11:07 ` Arnt Karlsen
2003-05-14 22:19 ` P.Italiaander
2003-05-15 0:19 ` P.Italiaander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030515194843.6c8876f2.arnt@c2i.net \
--to=arnt@c2i.net \
--cc=netfilter@lists.netfilter.org \
--cc=pc-secure@home.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox