All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Routing problem !!!
Date: Fri, 05 Dec 2003 03:51:19 +0000	[thread overview]
Message-ID: <marc-lartc-107059632823830@msgid-missing> (raw)

Hello again,

 : Martin, as you can see in my last post i have route to 10.0.0.1 in the
 : main routing table , so i have ping to the gateway but i can't connect
 : to inet.

OK.  So, you can ping the gateway.....can you ping the gateway from the
source IPs you want to have Internet access?

But, before we cover that, we need to back up to the "Why?" question.  You
don't explain enough for me to understand why you need the second routing
table.  In looking at your two routing tables, I don't see any reason for
two.

 : #ip r l t main
 : 10.0.0.0/16 dev eth0  scope link
 :
 :
 : The only way to connect to inet is adding:
 :
 : ip r a default via 10.0.0.1 t main
 :
 : If i add the default gw in table main , i can connect to inet but i'd
 : like to do this in other table.

I have some questions, then:

 - Are the packets initiated from the Linux box?
 - What is the source IP on a packet which is not leaving the box in
   the manner you desire?  Can you add an "ip rule" to define the
   characteristics of this packet?
 - Are you trying to force packets to be sourced from a particular IP?
 - Are you trying to block particular packets from getting to the
   Internet?

 : Can you help me ?

I'll most certainly try.

 :  eth0: 10.0.0.2/16
 :  eth1: 10.0.0.1    (inet gateway)
 :
 :  #ip ru l :
 :
 :  0:      from all lookup local
 :  32765:  from 10.0.0.2 lookup tabla1
 :  32766:  from all lookup main
 :  32767:  from all lookup default
 :
 :
 :  #ip r l t tabla1
 :
 :
 :  10.0.0.0/16 dev eth0  scope link  src 10.0.0.2
 :  127.0.0.0/8 dev lo  scope link
 :  default via 10.0.0.1 dev eth0
 :
 :  #ip r l t main
 :
 :  10.0.0.0/16 dev eth0  scope link

[ snipped some of my earlier ravings ]

-Martin

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

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

             reply	other threads:[~2003-12-05  3:51 UTC|newest]

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

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-107059632823830@msgid-missing \
    --to=mabrown-lartc@securepipe.com \
    --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.