On Sun, 24 Nov 2002 [EMAIL PROTECTED] wrote:
> Mike Burger wrote:
>
> > > > Hello
> > > > >
> > > > > So, do you means I can setup the NAT like this ?
> > > > > iptables -t nat -A POSTROUTING -o eth0 -s 192.168.0.0/24 -j MASQUERADE
> > > > >
> > > > > Thank for your help !
> > > >
> > > > The sh
Mike Burger wrote:
> > > Hello
> > > >
> > > > So, do you means I can setup the NAT like this ?
> > > > iptables -t nat -A POSTROUTING -o eth0 -s 192.168.0.0/24 -j MASQUERADE
> > > >
> > > > Thank for your help !
> > >
> > > The short answer to the question above is yes.
> > >
> > > Note...if you
On Sun, 24 Nov 2002 [EMAIL PROTECTED] wrote:
> Mike Burger wrote:
>
> > On Sun, 24 Nov 2002 [EMAIL PROTECTED] wrote:
> >
> > > Mike Burger wrote:
> > >
> > > > I'm not suggesting using a full /12 block. I was just noting that that
> > > > range, like the 192.168 range, is listed as "private spac
Mike Burger wrote:
> On Sun, 24 Nov 2002 [EMAIL PROTECTED] wrote:
>
> > Mike Burger wrote:
> >
> > > I'm not suggesting using a full /12 block. I was just noting that that
> > > range, like the 192.168 range, is listed as "private space"...you're fine
> > > with what you have...and the /24 that y
On Sun, 24 Nov 2002 [EMAIL PROTECTED] wrote:
> Bret Hughes wrote:
>
> > On Sat, 2002-11-23 at 09:50, Mike Burger wrote:
> > >
> > > On the off chance, I did a little digging...you're safe. 172.16.0.0/12
> > > (the space between 172.16.0.0 and 172.31.255.255) is not allocated, and is
> > > actual
On Sun, 24 Nov 2002 [EMAIL PROTECTED] wrote:
> Mike Burger wrote:
>
> > I'm not suggesting using a full /12 block. I was just noting that that
> > range, like the 192.168 range, is listed as "private space"...you're fine
> > with what you have...and the /24 that you'reusing.
>
> Hello
>
> So,
Bret Hughes wrote:
> On Sat, 2002-11-23 at 09:50, Mike Burger wrote:
> >
> > On the off chance, I did a little digging...you're safe. 172.16.0.0/12
> > (the space between 172.16.0.0 and 172.31.255.255) is not allocated, and is
> > actually considered "private space". You don't have to worry abou
Mike Burger wrote:
> I'm not suggesting using a full /12 block. I was just noting that that
> range, like the 192.168 range, is listed as "private space"...you're fine
> with what you have...and the /24 that you'reusing.
Hello
So, do you means I can setup the NAT like this ?
iptables -t nat -A
I love "whois".
On 23 Nov 2002, Bret Hughes wrote:
> On Sat, 2002-11-23 at 09:50, Mike Burger wrote:
> >
> > On the off chance, I did a little digging...you're safe. 172.16.0.0/12
> > (the space between 172.16.0.0 and 172.31.255.255) is not allocated, and is
> > actually considered "private
I'm not suggesting using a full /12 block. I was just noting that that
range, like the 192.168 range, is listed as "private space"...you're fine
with what you have...and the /24 that you'reusing.
Leave what you have alone...it's working, it's not violating any RFCs or
presenting any routing/ad
On Sat, 2002-11-23 at 09:50, Mike Burger wrote:
>
> On the off chance, I did a little digging...you're safe. 172.16.0.0/12
> (the space between 172.16.0.0 and 172.31.255.255) is not allocated, and is
> actually considered "private space". You don't have to worry about it.
>
huh. Learned some
Mike Burger wrote:
> You can not put a wildcard in your /etc/hosts file...no. You can put
> individiual entries in your /etc/hosts file, for each IP.
>
> To modify the zone file, you edit (probable location)
> /var/named/db.172.16.0, and do the following:
>
> Add a line for "1" that looks like th
That's funny...I don't think I've ever seen SA whack these as spammy for
the XXXs.
On Sat, 23 Nov 2002, Cowles, Steve wrote:
> > -Original Message-
> > From: Mike Burger
> > Sent: Saturday, November 23, 2002 9:50 AM
> > Subject: Re: Problem of
> -Original Message-
> From: Mike Burger
> Sent: Saturday, November 23, 2002 9:50 AM
> Subject: Re: Problem of NAT and DNS
>
> BTW...someone else had noted, earlier, that they seemed to
> think that the address space you're using belonged to someone
>
On Sat, 23 Nov 2002 [EMAIL PROTECTED] wrote:
> Peter Robb wrote:
>
> > On Sat, 2002-11-23 at 06:13, [EMAIL PROTECTED] wrote:
> > > So, do you means I can modify the /etc/hosts like this :
> > > 172.16.0.*cleints.xxx.xxx.xxxclients
> > >
> > > BTW, how can I modify the zone file ( ip rever
You can not put a wildcard in your /etc/hosts file...no. You can put
individiual entries in your /etc/hosts file, for each IP.
To modify the zone file, you edit (probable location)
/var/named/db.172.16.0, and do the following:
Add a line for "1" that looks like the "254 IN PTR" line, below.
I
Peter Robb wrote:
> On Sat, 2002-11-23 at 06:13, [EMAIL PROTECTED] wrote:
> > So, do you means I can modify the /etc/hosts like this :
> > 172.16.0.*cleints.xxx.xxx.xxxclients
> >
> > BTW, how can I modify the zone file ( ip reverse ), then the system can
> > reverse the ip_addres range 17
On Sat, 2002-11-23 at 06:13, [EMAIL PROTECTED] wrote:
> So, do you means I can modify the /etc/hosts like this :
> 172.16.0.*cleints.xxx.xxx.xxxclients
>
> BTW, how can I modify the zone file ( ip reverse ), then the system can
> reverse the ip_addres range 172.16.0.1 - 172.16.0.253 ?
>
>
So, do you means I can modify the /etc/hosts like this :
172.16.0.*cleints.xxx.xxx.xxxclients
BTW, how can I modify the zone file ( ip reverse ), then the system can
reverse the ip_addres range 172.16.0.1 - 172.16.0.253 ?
Thank for your help !
Edward.
Mike Burger wrote:
> That would be
That would be correct. You don't have an actual entry for 172.16.0.1 in
your reverse zone file, so the system can't reverse resolve that IP until
you either put it into the zone file and reload, or put it into your
/etc/hosts file.
On Sat, 23 Nov 2002 [EMAIL PROTECTED] wrote:
> Hello,
>
> I
> -Original Message-
> From: [EMAIL PROTECTED]
> Sent: Friday, November 22, 2002 8:33 PM
> Subject: Problem of NAT and DNS
>
>
> Hello,
>
> I just setup NAT for the Intranet...
> I found I must modify /etc/hosts :
> 172.16.0.1client1.xxx.xxx.xxx
Hello,
I just setup NAT for the Intranet...
I found I must modify /etc/hosts :
172.16.0.1client1.xxx.xxx.xxxclient1
Then I can connect to ftp or telnet very quick...
So, is it the problem of IP Reverse ( DNS setting ) ?
Here is the setting of DNS :
/etc/named.conf :
zone "0.16.172.in-ad
22 matches
Mail list logo