NetFilter
[Top] [All Lists]

Re: DMZ problems

To: netfilter@lists.netfilter.org
Subject: Re: DMZ problems
From: Ted Phelps <phelps@gnusto.com>
Date: Fri, 26 Jan 2007 05:13:11 -0600
Delivered-to: sp-com-lists@consult.net
Delivered-to: netfilter-list1@securepoint.com
In-reply-to: Your message of Thu, 25 Jan 2007 17:22:09 EST. <45B92D91.8070500@aa.usno.navy.mil>
List-archive: </pipermail/netfilter>
List-help: <mailto:netfilter-request@lists.netfilter.org?subject=help>
List-id: General discussion and user questions <netfilter.lists.netfilter.org>
List-post: <mailto:netfilter@lists.netfilter.org>
List-subscribe: <https://lists.netfilter.org/mailman/listinfo/netfilter>, <mailto:netfilter-request@lists.netfilter.org?subject=subscribe>
List-unsubscribe: <https://lists.netfilter.org/mailman/listinfo/netfilter>, <mailto:netfilter-request@lists.netfilter.org?subject=unsubscribe>
References: <45B12F3B.5020306@aa.usno.navy.mil> <45B61EAB.1040706@pason.com> <45B92D91.8070500@aa.usno.navy.mil>
Sender: netfilter-bounces@lists.netfilter.org
Bill Tangren writes:
> Let's say I've been allocated 199.202.112.127/28 (these are made up 
> addresses) 
> by my ISP, and I'm told to netmask as 255.255.255.0. Let's say I assign my 
> firewall the IP address of 199.202.112.130 with a netmask of 255.255.255.0 as 
> required.> # ping 199.202.112.132
> Destination host unreachable
> 
> but
> 
> # ping -I eth1 199.202.112.132
> 
> works.

Try using 255.255.255.240 as your netmask instead?

Cheers,
-Ted


<Prev in Thread] Current Thread [Next in Thread>