All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krepper Guillermo <maurob@terranet.com.ar>
To: lartc@vger.kernel.org
Subject: [LARTC] almost got routing working, but as I sad "Almost", i need some help
Date: Tue, 24 Apr 2001 20:38:10 +0000	[thread overview]
Message-ID: <marc-lartc-98814496611022@msgid-missing> (raw)

Hi

Here is the architecture:

I have 2 Internet connections 


router 1 -- eth0 	|	| eth1
		| Linux	|
		| Router	|
router 2 -- eth2 	|	| eth3 --- PC (66.60.1.3)


Internet Connection:
	router 1 = 200.63.1.1	eth0 = 200.63.1.2
	router 2 = 66.60.1.1	eth2 = 66.60.1.2

Lan Connection
	eth1 (NAT) = 	192.168.200.0/24
			192.168.201.0/24
			192.168.202.0/24

	eth3 (IP Aliasing) = 	200.63.1.3, 200.63.1.4, 200.63.1.5
				66.60.1.3, 66.60.1.4, 66.60.1.5


$ip rule
0:      from all lookup local
32762:  from 66.60.1.3 lookup 101
32763:  from all to 66.60.1.3 lookup 100
32764:  from 192.168.200.0/24 lookup 200
32765:  from 192.168.100.0/24 lookup 300
32766:  from all lookup main
32767:  from all lookup 253

$ ip route
255.255.255.255 dev eth1  scope link					(for DHCP)
200.63.1.0/24 dev eth0  proto kernel  scope link  src 200.63.1.2
192.168.200.0/24 dev eth1  proto kernel  scope link  src 192.168.200.254
192.168.201.0/24 dev eth1  proto kernel  scope link  src 192.168.201.254
192.168.202.0/24 dev eth1  proto kernel  scope link  src 192.168.202.254
66.60.1.0/24 dev eth2  proto kernel  scope link  src 66.60.1.2
127.0.0.0/8 dev lo  scope link
default via 66.60.1.1 dev eth2				(66.60.1.1 = router 2)

$ ip route list table 300
192.168.200.0/24 via 192.168.200.254 dev eth1
192.168.201.0/24 via 192.168.201.254 dev eth1
192.168.202.0/24 via 192.168.202.254 dev eth1
default via 200.63.1.1 dev eth0                 		(200.63.1.1 = router

$ ip route list table 200
192.168.200.0/24 via 192.168.200.254 dev eth1
192.168.202.0/24 via 192.168.202.254 dev eth1
default via 66.60.1.1 dev eth2

$ ip route list table 100
66.60.1.3 via 66.60.1.2 dev eth3

	So far so good, but when I want to access the Internet with 66.60.1.3 (on 
eth3) I can't. 
But what I can do is ping any other machine on (192.168.200.0/24, 
192.168.201.0/24, 192.168.202.0/24) from 66.60.1.3.

So I did a rule from 66.60.1.3 like this and didn't work

# ip route list table 101
200.63.1.1 via 200.63.1.2 dev eth0
66.60.1.1 via 66.60.1.2 dev eth2
default via 66.60.33.1 dev eth2 

If you need any additional informational please tell me and I will send them

OK so I almost got it but need to solve this problem any ideas? or is there 
another way of doing this?

Thanks Krepper Guillermo




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

                 reply	other threads:[~2001-04-24 20:38 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-98814496611022@msgid-missing \
    --to=maurob@terranet.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 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.