From owner-freebsd-net  Fri Mar 23 12:39: 3 2001
Delivered-To: freebsd-net@freebsd.org
Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18])
	by hub.freebsd.org (Postfix) with ESMTP
	id EA09337B71A; Fri, 23 Mar 2001 12:38:48 -0800 (PST)
	(envelope-from max@vic.sabbo.net)
Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112])
	by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f2NKcjX12431;
	Fri, 23 Mar 2001 22:38:45 +0200
Received: (from max@localhost)
	by vic.sabbo.net (8.11.3/8.11.2) id f2NKcjr00532;
	Fri, 23 Mar 2001 22:38:45 +0200 (EET)
	(envelope-from sobomax@FreeBSD.org)
From: Maxim Sobolev <sobomax@freebsd.org>
Message-Id: <200103232038.f2NKcjr00532@vic.sabbo.net>
Subject: ppp(8) + ip forwarding doesn't work anymore
To: brian@freebsd.org
Date: Fri, 23 Mar 2001 22:38:45 +0200 (EET)
Cc: stable@freebsd.org, net@freebsd.org
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

I noticed that after upgrading to 4-BETA something goes wrong with ip
forwarding via ppp(8). I have a FreeBSD box (A) connected to Internet
via network interface and this system also has a modem for dial-in and
backup dial-up connection. Sometimes I need to route through this
modem traffic to/from only one specific host (B) on my internal
network, so I used the following command to do it and it worked like a
charm (50 is the first rule):

ppp.linkup:
!bg /sbin/ipfw add 50 fwd HISADDR ip from B to not 192.168.0.1/24

ppp.linkdown:
!bg delete 50

After upgrading to 4-BETA and consequently to 4-RC this doesn't work
anymore :(((. After a link is up I see this rule in my ipfw
configuration, see route to HISADDR in routing table, can ping
HISADDR  from A, but all packets from B are silently discarded (I see
count increase in `ipfw show', but ppp doesn't show any IP packets
going through). At the same time, I can get all packets from B and
other hosts routed through ppp by doing `route add default HISADDR'
after link is up, so obviously my configuration is OK. I suspect that
this has something to do with recent forwarding changes, but can't
tell more precisely.

It looks to me like a serious bug, that ought to be resolved before
4.3-RELEASE.

-Maxim
P.S. Yes, I have gateway_enable="YES" and "options IPFIREWALL_FORWARD"
on A.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message