All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Samad <alex@samad.com.au>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Routing problem (RTNETLINK answers: Invalid argument) on
Date: Thu, 15 Feb 2007 00:00:38 +0000	[thread overview]
Message-ID: <20070215000038.GU4088@samad.com.au> (raw)
In-Reply-To: <200702131450.13852.paul@diasoft.nl>


[-- Attachment #1.1: Type: text/plain, Size: 2025 bytes --]

On Wed, Feb 14, 2007 at 08:30:48AM +0100, Paul Viney wrote:
> > > I still seem to have much the same problem. I no longer get ICMP
> > > unreachable errors, but the packet just seems to disappear - I can't see
> > > it being forwarded on any interface, nor can I find any kind of reply -
> > > icmp or otherwise.
> >
> > sounds like a firewall issue!
> 
> It does sound like a firewall issue, but the only firewall rule I have at the 
> moment is the one doing the DNAT. If I do 'iptables -t nat -L -v', then I can 
> see the number of packets increasing. Once I remove the firewall rule, I get 
> my "icmp unreachable" errors again. Funnily enough, if I then reinstate the 
> firewall (dnat) rule, then I still get "icmp unreachable" errors and the 
> packet count doesn't go up for the rule. It's almost as though the rule 
> doesn't get consulted. 'ip route flush cache' doesn't make a difference. 
> After about 5 minutes the "icmp unreachable" errors stop and the packet count 
> starts going up, although I still can't find my packet on the next hop. (I do 
> have forwarding switched on). The packet count on a iptables log rule on the 
> forward table does not go up, giving me the impression that routing has 
> failed. 

This could be connection tracking, once you start a ping, connection tracking
will keep it in its cache, so even though you have placed it (the rule) back in
it doesn't count for the established link...

> I also tried ip r get <random internet address> from 192.168.12.5, which did 
> indeed give me the same "RTNETLINK answers: Invalid argument" error. I guess 
> that means that my understanding of the purpose of 'ip r get' is indeed 
> faulty. 

does 192.168.12.5 exist on your box, can up do an ip a
also do you have forwarding on ?

> 
> Thanks for all your help so far.
> 
> Paul Viney
> 
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> 

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-02-15  0:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13 13:50 [LARTC] Routing problem (RTNETLINK answers: Invalid argument) on Paul Viney
2007-02-13 20:40 ` Alex Samad
2007-02-13 21:54 ` Paul Viney
2007-02-14  2:53 ` Alex Samad
2007-02-14  7:30 ` Paul Viney
2007-02-14  7:35 ` Paul Viney
2007-02-14 20:17 ` [LARTC] Routing problem (RTNETLINK answers: Invalid argument) Torsten Luettgert
2007-02-14 23:30 ` [LARTC] Routing problem (RTNETLINK answers: Invalid argument) on Paul Viney
2007-02-15  0:00 ` Alex Samad [this message]
2007-02-18 20:30 ` [LARTC] Routing problem (RTNETLINK answers: Invalid argument) Brian J. Murrell

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=20070215000038.GU4088@samad.com.au \
    --to=alex@samad.com.au \
    --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.