Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Calin Ciuleanu <slayer@security21.itotal.ro>
To: lartc@vger.kernel.org
Subject: [LARTC] routing problem!
Date: Thu, 28 Mar 2002 10:52:02 +0000	[thread overview]
Message-ID: <marc-lartc-101731306219654@msgid-missing> (raw)


Hi 
My name is Calin Ciuleanu and i have some routing problem with iproute2
Here is my problem detalied:

i made one tunnel with ip tunnel that works between one cisco and a 
linux box
here is the conf for the tunnel on cisco
interface Tunnel1
 description tunnel to C5
 ip address 217.13.104.233 255.255.255.252
 tunnel source 193.231.111.225
 tunnel destination 193.226.6.227
 tunnel mode ipip
!
on the destination linux box 193.226.6.227 i made this tunnel

#ip tunnel add tunnel0 mode ipip remote 193.231.111.225 local 
193.226.6.227
#ip addr add 217.13.104.234/30 dev tunnel0
#ifconfig tunnel0 up

the tunnel works great thanks to you
on the linux box i have this main interfaces
eth0      Link encap:Ethernet  HWaddr 00:10:4B:43:4C:CF
          inet addr:193.226.6.227  Bcast:193.226.6.231  
Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1064424 errors:0 dropped:0 overruns:0 frame:0
          TX packets:872599 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:887874824 (846.7 Mb)  TX bytes:118030509 (112.5 Mb)
          Interrupt:10 Base address:0x7000
eth1      Link encap:Ethernet  HWaddr 00:00:21:29:86:BA
          inet addr:172.27.36.1  Bcast:172.27.36.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:950404 errors:0 dropped:0 overruns:0 frame:3140
          TX packets:1114735 errors:366 dropped:0 overruns:0 carrier:379
          collisions:374402 txqueuelen:100
          RX bytes:128979640 (123.0 Mb)  TX bytes:900948467 (859.2 Mb)
          Interrupt:5 Base address:0x6c00
the network connected to eth1 is with fake addresses
My routing table looks like this

root@gate:/# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
217.13.104.232  0.0.0.0         255.255.255.252 U     0      0        0 tunnel0
193.226.6.224   0.0.0.0         255.255.255.248 U     0      0        0 eth0
172.27.36.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         193.226.6.225   0.0.0.0         UG    0      0        0 eth0

I made another routing from the cisco from but now for another subnet

  ip route 217.13.104.236 255.255.255.252 Tunnel1

217.13.104.236 net 
217.13.104.237 ip1
217.13.104.238 ip3
217.13.104.239 brc

first ip is on a dummy on eth1. I made it with this command
#ifconfig eth1:0 217.13.104.237 netmask 255.255.255.252 broadcast
217.13.104.239

The interface looks like this:

eth1:0    Link encap:Ethernet  HWaddr 00:00:21:29:86:BA
          inet addr:217.13.104.237  Bcast:217.13.104.239 Mask:255.255.255.252
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:5 Base address:0x6c00
the coresponding routing table:

217.13.104.232  0.0.0.0         255.255.255.252 U     0      0        0 tunnel0
217.13.104.236  0.0.0.0         255.255.255.252 U     0      0        0 eth1
193.226.6.224   0.0.0.0         255.255.255.248 U     0      0        0 eth0
172.27.36.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         193.226.6.225   0.0.0.0         UG    0      0        0 eth0

but the other ip (217.13.104.238/30) i want to set it on one computer 
in the lan connected to eth1
My question is :
How can i route ip2: 217.13.104.238 in the tunnel and back ... 

For this 217.13.104.237 ( the dummy) traceroute works
slayer@EcoLin:~$ traceroute 217.13.104.237
traceroute to 217.13.104.237 (217.13.104.237), 30 hops max, 38 byte 
packets
 1  C3640-E0-0 (193.231.111.225)  1.341 ms  1.227 ms  1.346 ms
 2  Eco-GW.Cluj.Ro.Eu.Org (217.13.104.237)  4.296 ms  4.092 ms  4.001 ms
slayer@EcoLin:~$

but for 217.13.104.238 not
slayer@EcoLin:~$ traceroute 217.13.104.238
traceroute to 217.13.104.238 (217.13.104.238), 30 hops max, 38 byte 
packets
 1  C3640-E0-0 (193.231.111.225)  1.348 ms  1.247 ms  1.253 ms
 2  gate.campus.utcluj.ro (193.226.6.227)  4.703 ms  4.099 ms  4.333 ms
 3  * * *
 4  *
I tried something like this but it doesn't work
echo "200 kalin" >> /etc/iproute2/rt_tables
ip rule add from 217.13.104.236/32 table kalin
ip route add default dev tunnel0 table kalin

Best regards
Calin Ciuleanu




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

             reply	other threads:[~2002-03-28 10:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-28 10:52 Calin Ciuleanu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-05  3:51 [LARTC] Routing problem !!! Martin A. Brown

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-101731306219654@msgid-missing \
    --to=slayer@security21.itotal.ro \
    --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