Re: Odd ipfw behaviour

2002-02-19 Thread Michael R. Wayne
On Mon, Feb 18, 2002 at 09:31:13AM -0800, Crist J. Clark wrote: > > Do these patches help? Unfortunately, I was called out of town and will not be able to get back to work with my test setup until next week. Will post update then. /\/\ \/\/ To Unsubscribe: send mail to [EMAIL PROTECTED] with

Re: Odd ipfw behaviour

2002-02-18 Thread Crist J. Clark
On Mon, Feb 18, 2002 at 11:08:02AM -0800, Julian Elischer wrote: > that patch is an MFC of a fix that went into -current. > it allows teh 'fwd' ing of packets from the 'input' filter to > external machines.. > > i.e. > this doesn't work without this patch: > > ipfw add 100 fwd 1.2.3.4 tcp from a

Re: Odd ipfw behaviour

2002-02-18 Thread Julian Elischer
that patch is an MFC of a fix that went into -current. it allows teh 'fwd' ing of packets from the 'input' filter to external machines.. i.e. this doesn't work without this patch: ipfw add 100 fwd 1.2.3.4 tcp from any to 1.2.3.5 80 in recv fxp0 On Mon, 18 Feb 2002, Luigi Rizzo wrote: > On Mon

Re: Odd ipfw behaviour

2002-02-18 Thread Crist J. Clark
On Mon, Feb 18, 2002 at 10:09:28AM -0800, Luigi Rizzo wrote: > On Mon, Feb 18, 2002 at 10:04:58AM -0800, Crist J. Clark wrote: > > > > Do these patches help? > > > > > > can you please summarise the problem and what the fix is trying to > > > achieve ? > > > > I don't really understand what the

Re: Odd ipfw behaviour

2002-02-18 Thread Luigi Rizzo
On Mon, Feb 18, 2002 at 10:04:58AM -0800, Crist J. Clark wrote: > > > Do these patches help? > > > > can you please summarise the problem and what the fix is trying to > > achieve ? > > I don't really understand what the problem might be, and the issue is Precisely for this reason, what is that

Re: Odd ipfw behaviour

2002-02-18 Thread Crist J. Clark
On Mon, Feb 18, 2002 at 09:38:52AM -0800, Luigi Rizzo wrote: > On Mon, Feb 18, 2002 at 09:31:13AM -0800, Crist J. Clark wrote: > > On Mon, Feb 18, 2002 at 12:01:17PM -0500, Michael R. Wayne wrote: > > > On Mon, Feb 18, 2002 at 05:49:46AM -0800, Crist J. Clark wrote: > > > > What precise version of

Re: Odd ipfw behaviour

2002-02-18 Thread Luigi Rizzo
On Mon, Feb 18, 2002 at 09:31:13AM -0800, Crist J. Clark wrote: > On Mon, Feb 18, 2002 at 12:01:17PM -0500, Michael R. Wayne wrote: > > On Mon, Feb 18, 2002 at 05:49:46AM -0800, Crist J. Clark wrote: > > > What precise version of FreeBSD are you running, BTW? > > > > 4.5 RELEASE, as stated in ori

Re: Odd ipfw behaviour

2002-02-18 Thread Crist J. Clark
On Mon, Feb 18, 2002 at 12:01:17PM -0500, Michael R. Wayne wrote: > On Mon, Feb 18, 2002 at 05:49:46AM -0800, Crist J. Clark wrote: > > What precise version of FreeBSD are you running, BTW? > > 4.5 RELEASE, as stated in original message. Do these patches help? Index: ip_input.c

Re: Odd ipfw behaviour

2002-02-18 Thread Michael R. Wayne
On Mon, Feb 18, 2002 at 05:49:46AM -0800, Crist J. Clark wrote: > What precise version of FreeBSD are you running, BTW? 4.5 RELEASE, as stated in original message. /\/\ \/\/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message

Re: Odd ipfw behaviour

2002-02-18 Thread Crist J. Clark
What precise version of FreeBSD are you running, BTW? -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscri

Re: Odd ipfw behaviour

2002-02-18 Thread Michael R. Wayne
On Sat, Feb 16, 2002 at 12:47:21AM -0800, Crist J. Clark wrote: > On Fri, Feb 15, 2002 at 06:09:51PM -0500, Michael R. Wayne wrote: > > > Using this ipfw rule on ProxyFirewall: > >fwd $(squid-box) log tcp from $(windows-box) to any 80 > > and checking the logs on ProxyFirewall, I see this ho

Re: Odd ipfw behaviour

2002-02-16 Thread Crist J. Clark
On Fri, Feb 15, 2002 at 06:09:51PM -0500, Michael R. Wayne wrote: [snip] > Using this ipfw rule on ProxyFirewall: >fwd $(squid-box) log tcp from $(windows-box) to any 80 > and checking the logs on ProxyFirewall, I see this horrible mess: > > ipfw: 11005 Forward to SQUIDbox TCP BROWSERbox:16