All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: linux@arcoscom.com
Cc: lartc@mailman.ds9a.nl, netfilter-devel@lists.netfilter.org,
	netfilter@lists.netfilter.org
Subject: [LARTC] Re: dst cache overflow
Date: Wed, 10 Jan 2007 07:15:58 +0000	[thread overview]
Message-ID: <45A492AE.2030909@trash.net> (raw)
In-Reply-To: <55635.10.1.1.10.1167946368.squirrel@www.arcoscom.com>

ArcosCom Linux User wrote:
> The log says:
> 
> Dec 30 00:52:27 cura kernel: dst cache overflow
> Dec 30 00:52:27 cura kernel: MASQUERADE: No route: Rusty's brain broke!
> Dec 30 00:52:27 cura kernel: dst cache overflow
> Dec 30 00:52:28 cura kernel: zlan0: received tcn bpdu on port 1(eth0)
> Dec 30 00:52:28 cura kernel: zlan0: topology change detected, propagating
> Dec 30 00:52:28 cura kernel: dst cache overflow
> Dec 30 00:52:30 cura kernel: zlan0: received tcn bpdu on port 1(eth0)
> Dec 30 00:52:30 cura kernel: zlan0: topology change detected, propagating
> Dec 30 00:52:32 cura kernel: zlan0: received tcn bpdu on port 1(eth0)
> Dec 30 00:52:32 cura kernel: zlan0: topology change detected, propagating
> Dec 30 00:52:32 cura kernel: printk: 15 messages suppressed.
> Dec 30 00:52:32 cura kernel: dst cache overflow
> Dec 30 00:52:34 cura kernel: zlan0: received tcn bpdu on port 1(eth0)
> Dec 30 00:52:34 cura kernel: zlan0: topology change detected, propagating
> Dec 30 00:52:36 cura kernel: zlan0: received tcn bpdu on port 1(eth0)
> Dec 30 00:52:36 cura kernel: zlan0: topology change detected, propagating
> Dec 30 00:52:37 cura kernel: printk: 40 messages suppressed.
> Dec 30 00:52:37 cura kernel: dst cache overflow
> 
> zlan0 is a bridge (with STP configured) between some LANs.
> 
> Thanks
> 
> P.D.: I'm a bit desesperated with this error, I changed "MASQUERADE" with
> "SNAT" with no sense. Some hours after router is booted up, the network
> appears to be UP but all ifaces haven't responses.


The MASQUERADE message is just an effect of the problem. Please describe
your setup in more detail (what kind of devices, how are they connected,
ebtables/iptables rules, routing, ...).

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

WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: linux@arcoscom.com
Cc: lartc@mailman.ds9a.nl, netfilter-devel@lists.netfilter.org,
	netfilter@lists.netfilter.org
Subject: Re: dst cache overflow
Date: Wed, 10 Jan 2007 08:15:58 +0100	[thread overview]
Message-ID: <45A492AE.2030909@trash.net> (raw)
In-Reply-To: <55635.10.1.1.10.1167946368.squirrel@www.arcoscom.com>

ArcosCom Linux User wrote:
> The log says:
> 
> Dec 30 00:52:27 cura kernel: dst cache overflow
> Dec 30 00:52:27 cura kernel: MASQUERADE: No route: Rusty's brain broke!
> Dec 30 00:52:27 cura kernel: dst cache overflow
> Dec 30 00:52:28 cura kernel: zlan0: received tcn bpdu on port 1(eth0)
> Dec 30 00:52:28 cura kernel: zlan0: topology change detected, propagating
> Dec 30 00:52:28 cura kernel: dst cache overflow
> Dec 30 00:52:30 cura kernel: zlan0: received tcn bpdu on port 1(eth0)
> Dec 30 00:52:30 cura kernel: zlan0: topology change detected, propagating
> Dec 30 00:52:32 cura kernel: zlan0: received tcn bpdu on port 1(eth0)
> Dec 30 00:52:32 cura kernel: zlan0: topology change detected, propagating
> Dec 30 00:52:32 cura kernel: printk: 15 messages suppressed.
> Dec 30 00:52:32 cura kernel: dst cache overflow
> Dec 30 00:52:34 cura kernel: zlan0: received tcn bpdu on port 1(eth0)
> Dec 30 00:52:34 cura kernel: zlan0: topology change detected, propagating
> Dec 30 00:52:36 cura kernel: zlan0: received tcn bpdu on port 1(eth0)
> Dec 30 00:52:36 cura kernel: zlan0: topology change detected, propagating
> Dec 30 00:52:37 cura kernel: printk: 40 messages suppressed.
> Dec 30 00:52:37 cura kernel: dst cache overflow
> 
> zlan0 is a bridge (with STP configured) between some LANs.
> 
> Thanks
> 
> P.D.: I'm a bit desesperated with this error, I changed "MASQUERADE" with
> "SNAT" with no sense. Some hours after router is booted up, the network
> appears to be UP but all ifaces haven't responses.


The MASQUERADE message is just an effect of the problem. Please describe
your setup in more detail (what kind of devices, how are they connected,
ebtables/iptables rules, routing, ...).

  parent reply	other threads:[~2007-01-10  7:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-02 22:24 dst cache overflow ArcosCom Linux User
2007-01-04 21:32 ` [LARTC] " ArcosCom Linux User
2007-01-04 21:32   ` ArcosCom Linux User
2007-01-04 21:39   ` [LARTC] " Alexandru Dragoi
2007-01-04 21:42   ` Alexandru Dragoi
2007-01-10  7:15   ` Patrick McHardy [this message]
2007-01-10  7:15     ` Patrick McHardy
2007-01-10 11:33     ` [LARTC] " ArcosCom Linux User
2007-01-10 11:33       ` ArcosCom Linux User
2007-01-10 11:40     ` [LARTC] " ArcosCom Linux User
2007-01-10 11:40       ` ArcosCom Linux User
2007-01-10 12:16     ` [LARTC] " ArcosCom Linux User
2007-01-10 12:16       ` ArcosCom Linux User
2007-01-10 12:57       ` [LARTC] " Patrick McHardy
2007-01-10 12:57         ` Patrick McHardy
2007-01-10 13:17     ` [LARTC] " ArcosCom Linux User
2007-01-10 13:17       ` ArcosCom Linux User
2007-01-10 13:20     ` [LARTC] " ArcosCom Linux User
2007-01-10 13:20       ` ArcosCom Linux User
2007-01-10 15:01       ` [LARTC] " Jesper Dangaard Brouer
2007-01-10 15:01         ` Jesper Dangaard Brouer
2007-01-10 15:58         ` [LARTC] " ArcosCom Linux User
2007-01-10 16:01           ` ArcosCom Linux User
2007-01-10 19:40           ` [LARTC] " Jesper Dangaard Brouer
2007-01-10 19:40             ` Jesper Dangaard Brouer
2007-01-12  1:06             ` [LARTC] " ArcosCom Linux User
2007-01-12  1:06               ` ArcosCom Linux User
2007-01-10 18:32   ` [LARTC] " Torsten Luettgert

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=45A492AE.2030909@trash.net \
    --to=kaber@trash.net \
    --cc=lartc@mailman.ds9a.nl \
    --cc=linux@arcoscom.com \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=netfilter@lists.netfilter.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.