Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "gaston" <gaston@steel.com.ar>
To: lartc@vger.kernel.org
Subject: [LARTC] Routing problem
Date: Fri, 05 Sep 2003 16:12:02 +0000	[thread overview]
Message-ID: <marc-lartc-106277831121014@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101530055025659@msgid-missing>


	    Internet
		|
		|
	________|________
	|		|
	| Cisco 2600	|                   		                	        |   		|   
IP: 208.53.98.254               
	|_______________|
		|
		|	
		|
		|
		|	
		|
	________|_________
	|		|
	|     Switch 1	|                   		                    
	|_______________|
	
		|	
		|
		|
		|	
		|
	       ETH0 ---> IP:208.53.98.198        Net 208.53.98.0/25
	________|________
	|		|
   	|    Linux      | 
	|_______________|
		|
	       ETH1 --> IP:208.53.164.254    Net 208.53.164.0/24		
		|
		|
	________|_________
	|		|
	|     Switch 2	| ------ Clients                   		                    
       
	|_______________|
			
Red Hat Linux 9
Kernel: 2.4.20-8
I used the traditional routing config (without iproute2)


Routing table:

208.53.98.128   0.0.0.0         255.255.255.128 U                   0 eth0
208.53.164.0    0.0.0.0         255.255.255.0   U                   0 eth1
169.254.0.0     0.0.0.0         255.255.0.0     U                   0 eth1
127.0.0.0       0.0.0.0         255.0.0.0       U                   0 lo
0.0.0.0         208.53.98.254   0.0.0.0         UG                  0 eth0

		
Cisco 2600 config:

ip route 208.53.164.0 255.255.255.0 208.53.98.198


Problem:

This configuration didn't work. From the clients network (208.53.164.0) I
could only reach the Cisco router but was unable to reach Internet. 

The only quick solution was to connect Switch 1 with Switch 2.


Any ideas why this didn't work? 

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

  parent reply	other threads:[~2003-09-05 16:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-05  3:55 [LARTC] routing problem suresh
2002-03-05 17:28 ` Ard van Breemen
2002-03-06  6:44 ` suresh
2002-11-20 17:31 ` [LARTC] Routing problem Mauro Cerboni
2002-11-22  0:03 ` Jose Luis Domingo Lopez
2002-11-22  0:32 ` George J. Jahchan, Eng.
2002-12-17 16:53 ` [LARTC] ROUTING Problem Andre Lorenz
2003-09-05 16:12 ` gaston [this message]
2003-09-07 23:03 ` [LARTC] Routing problem Damion de Soto
2003-09-08  6:41 ` Ronny Aasen
2003-09-08 14:46 ` gaston
2003-09-09 13:59 ` gaston
2003-11-10 12:29 ` [LARTC] routing problem Meretei Balázs
2003-11-10 23:55 ` Damion de Soto
2003-11-11  4:22 ` Martin A. Brown
2004-04-06 11:09 ` [LARTC] Routing problem huffo
2004-04-06 12:28 ` huffo
2004-04-06 23:32 ` Damion de Soto
2004-04-07  1:16 ` huffo
2004-04-07  1:26 ` huffo
2006-12-12 13:07 ` [LARTC] Routing Problem Javier A Toledano
2006-12-13 15:05 ` Taylor, Grant

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-106277831121014@msgid-missing \
    --to=gaston@steel.com.ar \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox