From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dor@ldc.net>
Date: Tue, 5 Apr 2005 09:02:21 +0300
From: "Dmytro O. Redchuk" <dor@ldc.net>
To: community@altlinux.ru
Subject: Re: [Comm] Master 2.4 =?koi8-u?Q?=C9_iprou?=
	=?koi8-u?Q?te2?=
Message-ID: <20050405060221.GA5481@ldc.net>
Mail-Followup-To: community@altlinux.ru
References: <02ce01c53908$146c9870$62fe0a0a@worker> <425121D1.6090604@ricom.ru>
	<035101c5390c$b2288d40$62fe0a0a@worker>
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-u
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <035101c5390c$b2288d40$62fe0a0a@worker>
User-Agent: Mutt/1.4.2.1i
X-Virus-Scanned: clamd / ClamAV version 0.74, clamav-milter version 0.74a
	on backup.ldc.net
X-Virus-Status: Clean
X-BeenThere: community@altlinux.ru
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: community@altlinux.ru
List-Id: Mailing list for ALT Linux users <community.altlinux.ru>
List-Unsubscribe: <https://lists.altlinux.ru/mailman/listinfo/community>,
	<mailto:community-request@altlinux.ru?subject=unsubscribe>
List-Archive: <http://lists.altlinux.ru/pipermail/community>
List-Post: <mailto:community@altlinux.ru>
List-Help: <mailto:community-request@altlinux.ru?subject=help>
List-Subscribe: <https://lists.altlinux.ru/mailman/listinfo/community>,
	<mailto:community-request@altlinux.ru?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2005 06:02:23 -0000
Archived-At: <http://lore.altlinux.org/community/20050405060221.GA5481@ldc.net/>
List-Archive: <http://lore.altlinux.org/community/>
List-Post: <mailto:mandrake-russian@linuxteam.iplabs.ru>

On Mon, Apr 04, 2005 at 03:51:53PM +0400, Konstantin Polansky wrote:
> *This message was transferred with a trial version of CommuniGate(tm) Pro*
> > > Что такое могло изменится в 2.4, что скрипт с маршрутами работает на
> Master
> > > 2.2, а на 2.4 не работает.
> > > Ошибок нет, в таблице  ip route все маршруты указываются, но ничего не
> > > работает...
> > А скрипт с маршрутами можно в студию?
> >
> 
> 
> ip rule add from 192.168.252.0/24 table hz
> ip rule add from 192.168.174.0/26 table hz
> ip rule add from 192.168.178.128/26 table hz
> ip rule add from 192.168.178.192/26 table hz
> ip rule add from 192.168.184.0/24 table hz
> ip rule add from 192.168.185.0/24 table hz
> ip route add 192.168.4.64/27 dev eth2 table hz
> ip route add 192.168.252.0/24 via 192.168.178.189 dev eth2 table hz
> ip route add 192.168.174.0/26 via 192.168.178.189 dev eth2 table hz
> ip route add 192.168.178.128/26 dev eth2 table hz
> ip route add 192.168.178.192/26 via 192.168.178.189 dev eth2 table hz
> ip route add 192.168.184.0/24 via 192.168.178.189 dev eth2 table hz
> ip route add 192.168.185.0/24 dev eth2 table hz
> ip route add 192.168.181.68/30 dev eth1 src 192.168.181.70 table hz
> ip route add default via 192.168.181.69 dev eth1 table hz
> ip route flush cache

ip route show table hz, please

cat /etc/iproute2/rt_tables, please

-- 
  _,-=._              /|_/|
  `-.}   `=._,.-=-._.,  @ @._,
     `._ _,-.   )      _,.-'
        `    G.m-"^m`m'        Dmytro O. Redchuk