In message <[EMAIL PROTECTED]>, Jul
ian Elischer writes:
>the local fwd command is only implemented for TCP
Here is a patch against -stable that I did a while ago, but I never
got around to doing a -current version - the code there is quite
different.
Ian
Index: udp_usrreq.c
On Thu, 21 Nov 2002, Julian Elischer wrote:
> the local fwd command is only implemented for TCP
>
(patches accepted :-)
>
> On Thu, 21 Nov 2002, Scot Loach wrote:
>
> > I'm trying to implement a type of transparent proxy for UDP. My idea was to
> > use ipfw to redirect all incoming UDP pac
the local fwd command is only implemented for TCP
On Thu, 21 Nov 2002, Scot Loach wrote:
> I'm trying to implement a type of transparent proxy for UDP. My idea was to
> use ipfw to redirect all incoming UDP packets to my server, for example:
>
> ipfw add fwd 127.0.0.1,9000 udp from any to any
that were originally sent with a destination port of 9000.
scot.
-Original Message-
From: Martin Stiemerling [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 21, 2002 2:03 PM
To: Scot Loach
Cc: '[EMAIL PROTECTED]'
Subject: Re: Using ipfw to forward udp
man ipfw says to fwd:
man ipfw says to fwd:
fwd | forward ipaddr[,port]
Change the next-hop on matching packets to ipaddr, which can be
an IP address in dotted quad or a host name. The search termi-
nates if this rule matches.
If ipaddr is a local address, then matching packets will be for-
warded to port (or the por
I'm trying to implement a type of transparent proxy for UDP. My idea was to
use ipfw to redirect all incoming UDP packets to my server, for example:
ipfw add fwd 127.0.0.1,9000 udp from any to any recv em0
However this doesn't seem to work: my server only receives UDP packets that
are addressed
