From: Arnt Karlsen <arnt@c2i.net>
To: David Ruggles <david@safedatausa.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Quick Routing question
Date: Wed, 5 Mar 2003 17:37:50 +0100 [thread overview]
Message-ID: <20030305173750.5f93ec8f.arnt@c2i.net> (raw)
In-Reply-To: <00ae01c2e323$ca9b6fa0$1f0016ac@daviddesktop>
On Wed, 5 Mar 2003 09:30:35 -0500,
"David Ruggles" <david@safedatausa.com> wrote in message
<00ae01c2e323$ca9b6fa0$1f0016ac@daviddesktop>:
> ----- Original Message -----
> From: "Arnt Karlsen" <arnt@c2i.net>
> Subject: Re: Quick Routing question
>
> [Snipped Dig commands]
>
> >
> > ..you run a _root_ name server and come here asking us amateur
> > newbies with less than 25 yrs internet experience for netfilter
> > advice????? ;-)
> >
>
> I hope you're joking. 172.22.x.x is inside the Class B non-routable
> addresses set aside by RFC 1918
..got that right, only just _after_ posting. ;-)
..it's 172.22.0.0/what-netmask?
> Thanks,
> David Ruggles
>
> CCNA MCSE (NT) CNA A+
> Network Engineer, Safe Data, Inc
> 910-285-7200 david@safedatausa.com
> 010001110110111101100100011011000110111101110110011001010111001101111
> 0010110 111101110101
>
--
..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-03-05 16:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 20:10 Quick Routing question David Ruggles
2003-03-04 20:47 ` Maciej Soltysiak
2003-03-05 0:07 ` Arnt Karlsen
2003-03-05 14:30 ` David Ruggles
2003-03-05 16:37 ` Arnt Karlsen [this message]
2003-03-05 18:14 ` David Ruggles
2003-03-05 21:02 ` David Ruggles
2003-03-05 21:36 ` A netfilter question David Ruggles
-- strict thread matches above, loose matches on Subject: below --
2003-03-04 21:19 Quick Routing Question ImpulseFG
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=20030305173750.5f93ec8f.arnt@c2i.net \
--to=arnt@c2i.net \
--cc=david@safedatausa.com \
--cc=netfilter@lists.netfilter.org \
/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