proxy route gateway ip masquerading ip chains ?

proxy route gateway ip masquerading ip chains ?

Post by piet » Mon, 11 Dec 2000 22:29:32



2 computers:
computer1: internet access trough cable modem. Red Hat6.0. i get
assigned an ip address from my provider automatically.

computer2: win98 with modem

I want to go on the internet using my connection on computer1.
So i dial in to computer1 (so far it works).
But then what: how do i configure the lin and the win machine?

piet

 
 
 

proxy route gateway ip masquerading ip chains ?

Post by Adam KOS » Mon, 11 Dec 2000 22:55:25


:2 computers:
:computer1: internet access trough cable modem. Red Hat6.0. i get
:assigned an ip address from my provider automatically.
:
:computer2: win98 with modem
:
:I want to go on the internet using my connection on computer1.
:So i dial in to computer1 (so far it works).
:But then what: how do i configure the lin and the win machine?
:
You have to set up your linux box to be able to answer incoming calls.  I
did this several times, pppd is the right choice for you.  You need to
assign an unique IP number for the modem, such as 192.168.x.y.  Then
configure your kernel to forward packets to and from the modem.  Your
provider gave you a 'real' IP number, ip masqing is the connection between
the real and 'intranet' number.  Do not forget, that you need kernel
support in order to get all these working together.  Btw. pppd must have
proxying enabled.  The key is (after mgetty is working fine):
echo 1 > /proc/sys/net/ipv4/ip_forward
ipchains -A forward -j MASQ

I, though recommend you to set up your rules properly, do not allow any
packets that are not necessary.

Sorry for my english, i haven't been reading this list for a long time.

cheers
adam

=====================================================================
| Adam Kosa                               | Experience is something |

| HP    : http://ka.lyss.net              | need it.                |
=====================================================================

 
 
 

proxy route gateway ip masquerading ip chains ?

Post by piet » Tue, 12 Dec 2000 06:15:58




> :2 computers:
> :computer1: internet access trough cable modem. Red Hat6.0. i get
> :assigned an ip address from my provider automatically.
> :
> :computer2: win98 with modem
> :
> :I want to go on the internet using my connection on computer1.
> :So i dial in to computer1 (so far it works).
> :But then what: how do i configure the lin and the win machine?
> :
> You have to set up your linux box to be able to answer incoming calls.  I
> did this several times, pppd is the right choice for you.  You need to

I already got this far. I can dialin from computer1 to computer2 and
make a connection using pppd and mgetty.

Quote:> assign an unique IP number for the modem, such as 192.168.x.y.  Then

I know how to address an ip nr to an ehternet card but not how to
address one to a modem. How do i do this? Can i use linuxconf? is it the
same as assiging an ip to device ppp0?
I suppose the modem on the win computer needs an ip nr as well

Quote:> configure your kernel to forward packets to and from the modem.  Your

i have never touched the kernel before so i suppose it's time for me to
read some howto's on the subject. Do i need kernelcfg for this or is
there more to it?

Quote:> provider gave you a 'real' IP number, ip masqing is the connection between

not really. I have an address and port for automatic proxy
configuration.
Further i received ip nrs of the first and second DNS server

Quote:> the real and 'intranet' number.  Do not forget, that you need kernel
> support in order to get all these working together.  Btw. pppd must have
> proxying enabled.  The key is (after mgetty is working fine):
> echo 1 > /proc/sys/net/ipv4/ip_forward
> ipchains -A forward -j MASQ

> I, though recommend you to set up your rules properly, do not allow any
> packets that are not necessary.

i have heard from this before "rules" but that's all. I'll have some
more howto's to read.

Quote:

> Sorry for my english, i haven't been reading this list for a long time.

hey no problem, you make yourself perfectly clear.
Thanks
Piet

- Show quoted text -

> cheers
> adam

> =====================================================================
> | Adam Kosa                               | Experience is something |

> | HP    : http://ka.lyss.net              | need it.                |
> =====================================================================

 
 
 

1. IP-Chains vs. IP-Masquerade

I'm planning on setting up the Linux box to act as a gateway for a private

As I understand it from skimming the HOW-TOs, IP-Chains sets the firewall
rules and can also handle masquerading.
IP-Masquerade is for masquerading only.

If I install IP-Chains, is there any reason (read: functionality /
performance benefit) to install IP-Masquerade?

Thanks!

2. Voice activated recording from line-in.

3. IP Masquerade , IP Chains

4. USB DDK 0.9

5. Route IP masqueraded packets according to their source IP?

6. How does tar allocate it's r/w buffer?

7. IP Masquerade works, but how do you route an unMasquerade IP?

8. vmstat sr question - whether or not to add memory

9. virtual IP - masquerading - "real" IP - routing

10. ipfw (IP Firewall), proxy and IP routing on Solaris 2.4

11. IP for masqueraded net other than masquerading host IP

12. Configuring net (IP-tunnel, IP-Alias, Proxy-ARP, NAT, IP-Masq?)

13. IP chain/Masquerading Help Sought