All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin Villarreal" <martin_villarreal@hotmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] 2 ADSL links with same P-t-P address !!
Date: Thu, 06 Nov 2003 20:21:01 +0000	[thread overview]
Message-ID: <marc-lartc-106815023419631@msgid-missing> (raw)

Hi List... I cant share 2 adsl links in a Nat Box for 30 machines, the idea 
is balancing the load of that 30 machines between 2 adsl links, I tried whit 
several how to's including the LARTC How to and nothing work.... I think 
that the P-t-P can be the problem, actually I'm using only 1 ADSL for this 
problem (ppp0)
Somebody can tell me what's wrong? or what to do step by step?

Some info...

30 Machines from 192.168.1.100 to 192.168.1.130.

           -------- eth0 (no ip) ----------------- ADSL1
          |
Linux Box ----- eth1 (no ip) ----------------- ADSL2
          |
           -------- eth2 (192.168.1.100) ----------------- To Local Lan 
(192.168.1.0/24).

Here is my actual iptables rule... any suggestion with tho ppp devices? I 
must appy 15 rules for one adsl link and 15 rules for the other adsl link?

iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -d 0/0 -o ppp0 -j 
MASQUERADE

eth0      Link encap:Ethernet  HWaddr 00:04:75:C1:12:9B
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

eth1      Link encap:Ethernet  HWaddr 00:04:75:C1:12:8A
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

eth2      Link encap:Ethernet  HWaddr 00:04:75:C1:11:3B
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0

ppp0      Link encap:Point-to-Point Protocol
          inet addr:168.226.152.62  P-t-P:192.168.96.239  
Mask:255.255.255.255

ppp1      Link encap:Point-to-Point Protocol
          inet addr:200.63.152.109  P-t-P:192.168.96.239  
Mask:255.255.255.255

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
200.32.3.0      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         200.32.3.1      0.0.0.0         UG    1      0        0 eth0

192.168.96.239 dev ppp0  proto kernel  scope link  src 168.226.152.62
192.168.96.239 dev ppp1  proto kernel  scope link  src 200.63.152.109
192.168.1.0/24 dev eth2  proto kernel  scope link  src 192.168.1.100
127.0.0.0/8 dev lo  scope link
default via 192.168.96.239 dev ppp0


Thats alll.... Thanks List ....

Martin.... =)

_________________________________________________________________
Consigue aquí las mejores y mas recientes ofertas de trabajo en América 
Latina y USA: www.yupimsn.com/empleos

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

                 reply	other threads:[~2003-11-06 20:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=marc-lartc-106815023419631@msgid-missing \
    --to=martin_villarreal@hotmail.com \
    --cc=lartc@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.