From: Raymond Leach <raymondl@knowledgefactory.co.za>
To: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: RE: Today's Brain Teaser.
Date: 12 Mar 2003 12:31:33 +0200 [thread overview]
Message-ID: <1047465092.11442.35.camel@raylinux.internal> (raw)
In-Reply-To: <4D613EBFB75BD6118A5B00508BEEC62C0111CBC1@JESS>
[-- Attachment #1: Type: text/plain, Size: 2385 bytes --]
On Wed, 2003-03-12 at 11:20, Jonathan Humphrey wrote:
> As a company we have two t1's (greedy i know!)
>
> the aaa.aaa.aaa.aaa address range is the external address's for one T1
> xxx.xxx.xxx.xxx is the address range for the other T1
>
How does the xxx.xxx.xxx.xxx connect to the linux router? eth1:1? Or are
the two t1's connected to the router (something like a Cisco 2501)? If
that's the case, then I would check the routing tables (and interfaces)
on the router first ...
> Does that make sense!
>
> -----Original Message-----
> From: Raymond Leach [mailto:raymondl@knowledgefactory.co.za]
> Sent: 12 March 2003 09:09
> To: Netfilter Mailing List
> Subject: Re: Today's Brain Teaser.
>
>
> On Wed, 2003-03-12 at 10:35, Jonathan Humphrey wrote:
> > I've been struggling with this one for some time, i am currently at
> > the end of my teather so if anyone has any great ideas about why
> this
> > happens let me know.
> >
> > Basically, i have a linux server that has three interfaces;
> >
> > eth1 aaa.aaa.aaa.202 External Facing network
> > eth0 bbb.bbb.bbb.254 Internal protected network
> > eth1:0 aaa.aaa.aaa.197 External IP Address for
> > FTPServer
> >
> > I have a device that sits on xxx.xxx.xxx.5 that cannot get to any
> > service on aaa.aaa.aaa.197, however every other ip address i have
> > tried can. I suspect that if i release the real ip address of
> > aaa.aaa.aaa.197 then everyone reading this list could too.
> >
> > And it's on the .5 address, if i try from xxx.xxx.xxx.15 i can
> > connect.
> Where is xxx.xxx.xxx.5? Is it on the internal or external network?
>
> >
> > Nothing is being show as dropped in the logs either.
> >
> > Thanks,
> >
> > Jonathan Humphrey
> >
> >
> >
> **********************************************************************
> > This email and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they
> > are addressed. If you have received this email in error please
> notify
> > the system manager.
> >
> > This footnote also confirms that this email message has been swept
> by
> > MIMEsweeper for the presence of computer viruses.
> >
> >
> **********************************************************************
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-03-12 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 9:20 Today's Brain Teaser Jonathan Humphrey
2003-03-12 10:31 ` Raymond Leach [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 18:21 Jonathan Humphrey
2003-03-12 12:28 Jonathan Humphrey
2003-03-12 8:35 Jonathan Humphrey
2003-03-12 9:08 ` Raymond Leach
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=1047465092.11442.35.camel@raylinux.internal \
--to=raymondl@knowledgefactory.co.za \
--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