Re: 2 ISP connection sharing problem

Linux Advanced Routing and Traffic Control

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

 



Hi Arman,

If you want to route part1 to ISP1 and Part 2 to ISP2. You should have
the following rules

ip rule add from  193.168.3.0/25 to 0.0.0.0/0  table 100
ip route add default via 192.168.1.1  table 100

ip rule add from 192.168.3.128/25 to 0.0.0.0/0  table 200
ip route add default via  203.81.213.1 table 200



On 9/3/07, Martin A. Brown <martin@xxxxxxxxxxxx> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Arman,
>
>  : I have divided my network into 2 parts now that is
>  : 193.168.3.127/25 and 192.168.3.128/25.
>
> According to this output, below, you have not divided your /24 into
> two different networks, and it's really not clear exactly what you
> are asking.  Neither of these show up in your routing table:
>
>  192.168.3.0/25  (netmask 255.255.255.128)
>  192.168.3.128/25  (netmask 255.255.255.128)
>
>  : Destination     Gateway         Genmask         Flags Metric Ref    Use
>  : Iface
>  : 192.168.3.0     *               255.255.255.0   U     0      0        0 eth0
>  : 203.81.213.0    *               255.255.255.0   U     0      0        0 eth2
>  : 192.168.1.0     *               255.255.255.0   U     0      0        0 eth1
>  : 169.254.0.0     *               255.255.0.0     U     0      0        0 eth2
>  : default         203.81.213.1    0.0.0.0         UG    0      0        0 eth2
>
>  : I want to route part1 to ISP1 and Part 2 to ISP2.
>
> Without further data ("ip rule show", "ip route show table $ALT") we
> cannot know which interface your ISP2 is reachable through.
>
>  : I have made changes into rules. But I think my Tables T1,T2 are
>  : not used and default table is in use. How can I command to use
>  : tables T1,T2 instead of default table. route command output is
>
> There are a number of resources you might wish to examine first.  I
> would recommend first understanding the RPDB lookup mechanism [0]
> and then following the steps for multiple uplinks in the (venerable)
> LARTC documentation [1].
>
> You may find it fruitful to simulate the route lookup on a
> packet by packet basis by learning how to use the "ip route get"
> command:
>
>  # ip route get iif eth4 70.14.115.3 from XX.YY.204.58
>  70.14.115.3 from XX.YY.204.58 via XX.YY.204.1 dev eth8  src 192.168.4.1
>      cache <src-direct>  mtu 1500 advmss 1460 metric10 64 iif eth4
>  # ip route get iif eth3 70.14.115.3 from 192.168.3.117
>  70.14.115.3 from 192.168.3.117 via XX.YY.204.1 dev eth7  src 192.168.3.1
>      cache <src-direct>  mtu 1500 advmss 1460 metric10 64 iif eth3
>
> Good luck,
>
> - -Martin
>
>  [0] http://linux-ip.net/html/routing-selection.html
>     http://linux-ip.net/html/routing-selection.html#routing-selection-adv
>  [1] http://lartc.org/howto/lartc.rpdb.multiple-links.html
>
> - --
> Martin A. Brown
> http://linux-ip.net/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
> Comment: pgf-0.72 (http://linux-ip.net/sw/pine-gpg-filter/)
>
> iD8DBQFG3E3iHEoZD1iZ+YcRApZPAJwNhRk25oxC17Zmgy2sLNtBq7HRoACdGk/P
> p07vvD2W9yfFK+Ws/wPAjT0=
> =BAoI
> -----END PGP SIGNATURE-----
>


-- 
"The network is the computer"
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux