Date: Thu, 28 May 2015 13:36:45 +0200 From: Julian Kornberger <juliank@tzi.de> To: freebsd-net@freebsd.org Subject: Re: Crash with GRE und IPFW fwd Message-ID: <5566FDCD.9000908@tzi.de> In-Reply-To: <55668B7F.9010509@freebsd.org> References: <5566565A.7030200@tzi.de> <20150528013135.GR95600@strugglingcoder.info> <55668B7F.9010509@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 28.05.2015 um 05:29 schrieb Julian Elischer: > Julian, I am guessing (with no actual information) that something in gre > processing is > assuming that the packet id going where it normally would go. (and not > where fwd is sending it). > > you really need to use objdump or gdb to look at the gre module and > work out where > > gre_output+0x467 > > is in the function. that should give you a clue on the problem. > > not too helpful I know... but you have a reproducible case at least. > kgdb may be your friend if you > have a serial cable or firewire cable. It is a multihomed machine behind two DSL routers. All packets leave the interface with the default route unless I use IPFW with fwd. Is there another way to force packets to leave the correct interface? The problem does also appear if I shutdown the second WAN interface. This is the way the traffic goes: re0 (internal network) -> fwd to gre1 -> fwd to gateway of re1 -> re1 If the traffic source is the machine an not the internal network it seems to cause no problems. I guess the problem is to use fwd twice. I will do additional tests and I will try to debug this using a serial connection next week. kind regards, Julian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5566FDCD.9000908>