Re: yet/last problem with masquerading

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 13 Oct 2002, Michael Schwendt wrote:

> On Sat, 12 Oct 2002 20:31:35 +0200 (CEST), Jean Francois Ortolo wrote:
> 
> >   I presume my script should contain these few instructions:
> > 
> >   --- Beggining of the script
> >   iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
> >   iptables -A FORWARD -i eth1 -j ACCEPT
> > 
> >   echo 1 > /proc/sys/net/ipv4/ip_forward
> >   route add -net 192.168.1.0 netmask 255.255.255.0  /
> >                              gw ${IPADDR} dev eth1 
> >   --- End of the script
> 
> The last line could be either a static route or a dynamic route
> created on-the-fly by pppd. Not sure why you enter it manually.
> 

  Thank you very much Sir

  I don't know what should be done to set up the dynamic route between 
eth0 and eth1, in the case of an ADSL connection.
  Would you say me how to do this ?

  Indeed, IP Masquerading is able to take into account all that is 
required, in order to make an existing connection coming along, if this 
connection was being requested from inside the lan to the external network.

  However, what happens if the current involved protocol launchs a 
request to, let's suppose 113 auth port inside the lan ?

  There should be then a new connection coming from the outside network to 
the external address of the lan, with a destination port 113, no ?

  The whole problem is whether or not this kind of authentification, would 
involve specifically a new incoming connection. Is it true ?

  Thank you very much for your help.

  Best regards.

  Jean Francois Ortolo







[Index of Archives]     [Fedora General Discussion]     [Red Hat General Discussion]     [Centos]     [Kernel]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat 9]     [Gimp]     [Yosemite News]

  Powered by Linux