* [sisyphus] un-def и nat
@ 2012-10-10 10:42 Anton Gorlov
2012-10-13 7:48 ` Anton Gorlov
0 siblings, 1 reply; 2+ messages in thread
From: Anton Gorlov @ 2012-10-10 10:42 UTC (permalink / raw)
To: ALT Linux Sisyphus discussion list
А никто не замечал что с un-def порой snat не работает?
Симптомы следующие - на локальном интерфейсе вижу приходящие пакеты с
адресом из локальной сети,на исходящем вижу уже отначенные пакеты и
ответные на них.а вот на локальном уже ответных пакетов не видно.
С 1 стороны pppoe до провайдера, с другой локалка по обычному эзернету.
Причём порой всё таки работает после перезагрузки
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [sisyphus] un-def и nat
2012-10-10 10:42 [sisyphus] un-def и nat Anton Gorlov
@ 2012-10-13 7:48 ` Anton Gorlov
0 siblings, 0 replies; 2+ messages in thread
From: Anton Gorlov @ 2012-10-13 7:48 UTC (permalink / raw)
To: ALT Linux Sisyphus discussions
а вот кажется и ответ. в 3.6.2 типа пофиксили
commit 52fc5048534e9d4127622fa5a269a92f3bb5218b
Author: Eric Dumazet <edumazet@google.com>
Date: Thu Oct 4 01:25:26 2012 +0000
ipv4: add a fib_type to fib_info
[ Upstream commit f4ef85bbda96324785097356336bc79cdd37db0a ]
commit d2d68ba9fe8 (ipv4: Cache input routes in fib_info nexthops.)
introduced a regression for forwarding.
This was hard to reproduce but the symptom was that packets were
delivered to local host instead of being forwarded.
David suggested to add fib_type to fib_info so that we dont
inadvertently share same fib_info for different purposes.
With help from Julian Anastasov who provided very helpful
hints, reproduced here :
<quote>
Can it be a problem related to fib_info reuse
from different routes. For example, when local IP address
is created for subnet we have:
broadcast 192.168.0.255 dev DEV proto kernel scope link src
192.168.0.1
192.168.0.0/24 dev DEV proto kernel scope link src 192.168.0.1
local 192.168.0.1 dev DEV proto kernel scope host src 192.168.0.1
The "dev DEV proto kernel scope link src 192.168.0.1" is
a reused fib_info structure where we put cached routes.
The result can be same fib_info for 192.168.0.255 and
192.168.0.0/24. RTN_BROADCAST is cached only for input
routes. Incoming broadcast to 192.168.0.255 can be cached
and can cause problems for traffic forwarded to 192.168.0.0/24.
So, this patch should solve the problem because it
separates the broadcast from unicast traffic.
And the ip_route_input_slow caching will work for
local and broadcast input routes (above routes 1 and 3) just
because they differ in scope and use different fib_info.
</quote>
Many thanks to Chris Clayton for his patience and help.
Reported-by: Chris Clayton <chris2553@googlemail.com>
Bisected-by: Chris Clayton <chris2553@googlemail.com>
Reported-by: Dave Jones <davej@redhat.com>
Signed-off-by: Eric Dumazet <edumazet@google.com>
Cc: Julian Anastasov <ja@ssi.bg>
Tested-by: Chris Clayton <chris2553@googlemail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
10.10.2012 14:42, Anton Gorlov пишет:
> А никто не замечал что с un-def порой snat не работает?
> Симптомы следующие - на локальном интерфейсе вижу приходящие пакеты с
> адресом из локальной сети,на исходящем вижу уже отначенные пакеты и
> ответные на них.а вот на локальном уже ответных пакетов не видно.
> С 1 стороны pppoe до провайдера, с другой локалка по обычному эзернету.
> Причём порой всё таки работает после перезагрузки
> _______________________________________________
> Sisyphus mailing list
> Sisyphus@lists.altlinux.org
> https://lists.altlinux.org/mailman/listinfo/sisyphus
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-10-13 7:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-10-10 10:42 [sisyphus] un-def и nat Anton Gorlov
2012-10-13 7:48 ` Anton Gorlov
ALT Linux Sisyphus discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/sisyphus/0 sisyphus/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 sisyphus sisyphus/ http://lore.altlinux.org/sisyphus \
sisyphus@altlinux.ru sisyphus@altlinux.org sisyphus@lists.altlinux.org sisyphus@lists.altlinux.ru sisyphus@lists.altlinux.com sisyphus@linuxteam.iplabs.ru sisyphus@list.linux-os.ru
public-inbox-index sisyphus
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.sisyphus
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git