From: "Martin Leduc" <marled3@hotmail.com>
To: ramin@cannon.eng.us.uu.net
Cc: netfilter@lists.netfilter.org
Subject: Re: Problem behind my DMZ
Date: Fri, 09 Jan 2004 09:54:42 +0000 [thread overview]
Message-ID: <Law9-F354jsKlkag7KO00012b91@hotmail.com> (raw)
> > Good evening folks,
> >
> > Sorry to answer you so late, and thank you for your informations. I'm
>so
> > exited, I have make test and, basicly, it's working. Tomorow is the
> > official test. I keep you informed.
> >
> > The only thing I can't figure out is the /32 netmask address for an
>address
> > having a /28. Why dont put the /28?
> >
> > Of course I try it but the route program have reject this entries. Can
>you
> > explain to me?
> >
> > Other thing. It is possible than I can't reach other machine placed
>before
> > the firewall BOX having address IP in the same range than my firewall
>box
> > after having put the /32 host in my route table?
> >
> > Example:
> > 192.168.1.1 ISP GAteway
> > 192.168.1.2 Server (Any kind)
> > 192.168.1.3 Firewall BOX (Eth0)
> > 192.168.1.3 Firewall BOX (eth1)
> > 192.168.1.4 Server Behind Firewall BOX
> >
> > Ping Test result
> > ---------------------------
> > 192.168.1.4 can reach 192.168.1.3
> > 192.168.1.4 can reach 192.168.1.1
> > 192.168.1.4 can't reach 192.168.1.2
> >
> > In the same test
> >
> > 192.168.1.2 can reach 192.168.1.1
> > But not 1.3 and 1.4
> >
> > I ask that because if I check my DSL route table, I see the same
> > configuration like
> >
> > Destination Gateway Genmask Flags Metric Ref Use
> > Iface
> > 67.68.140.1 0.0.0.0 255.255.255.255 UH 0 0 0
>ppp0
> > 192.168.1.1 0.0.0.0 255.255.255.0 U 0 0 0
>eth0
> > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
>lo
> > 0.0.0.0 67.68.140.1 0.0.0.0 UG 0 0 0
>ppp0
> >
> > I can ping 67.68.140.1, .2, .3, .4, .5, etc....
> >
> > Can you explain?
>
>Is your IP forwarding turned on?
Yes, it is. Can you explain to me why /32 against /28 netmask, or tell me
where I can get the documentation?
>
> >
> >
> > Now the configuration :D
>
>Please use the "ip" utility instead of ifconfig/route/arp/... It's much
>easier
>and more powerful...
Ok I will tried, but is not installed by default with slackware. I will
search where I can get it.
>
>Ramin
Regards and thanks in advance
Martin
_________________________________________________________________
MSN Search, le moteur de recherche qui pense comme vous !
http://fr.ca.search.msn.com/
next reply other threads:[~2004-01-09 9:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 9:54 Martin Leduc [this message]
2004-01-09 10:57 ` Problem behind my DMZ Antony Stone
2004-01-09 15:26 ` Ramin Dousti
-- strict thread matches above, loose matches on Subject: below --
2004-01-12 12:08 Martin Leduc
2004-01-10 13:26 Martin Leduc
2004-01-10 12:55 Martin Leduc
2004-01-09 2:19 Martin Leduc
2004-01-09 4:14 ` Ramin Dousti
2004-01-08 17:46 Martin Leduc
2004-01-08 17:53 ` Antony Stone
2004-01-08 17:12 Martin Leduc
2004-01-08 17:22 ` Antony Stone
2004-01-08 15:53 Martin Leduc
2004-01-08 16:16 ` Antony Stone
2004-01-08 18:10 ` Ramin Dousti
2004-01-08 17:17 ` Antony Stone
2004-01-08 19:18 ` Ramin Dousti
2004-01-08 0:19 Martin Leduc
2004-01-08 2:27 ` Chris Brenton
2004-01-08 16:31 ` Michael Gale
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=Law9-F354jsKlkag7KO00012b91@hotmail.com \
--to=marled3@hotmail.com \
--cc=netfilter@lists.netfilter.org \
--cc=ramin@cannon.eng.us.uu.net \
/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