I 'm not sure I understand but
firstly.. the 'fwd' keyword DOES NOT ALTER THE PACKET
so you need to have the same rule on 139.142.135.115
so that the incoming packet is captured there, whe it gets there,
as the headers still say that it's supposed to go somewhere else.
On Tue, 10 Jul 2001,
Ok one last question.. :)
I am trying to redirect all the traffic on a certain port except for a
couple of computers.. I have this rule setup to do this..
fwd 139.142.135.115 tcp from any to any 80
How would I then make it so that those couple of machines are not
effected.. I've tried the fol
Hmm.. I'm not sure which ones you want me to swap? I think the tabs are
getting messed up.. It looks like I should swap natd and from but that
can't be right?
Ahh there we go.. Swap the any and the 139 address.. That worked..
Thanks a lot you two! :)
Pete
On Tuesday, July 10, 2001, at 05:14
On Tue, 10 Jul 2001, Julian Elischer wrote:
>
>
> On Tue, 10 Jul 2001, Nick Rogness wrote:
> > You need to add another rule:
> >
> > ipfw add divert natd all from $PUBLIC_IP to any in via en0
> ^ ^
>
On Tue, 10 Jul 2001, Nick Rogness wrote:
> You need to add another rule:
>
> ipfw add divert natd all from $PUBLIC_IP to any in via en0
^ ^
\--/
On Tue, 10 Jul 2001, Peter Warrick wrote:
> I was referred to you by an Archie Cobbs who I guess did some of the
> ipfw code in FreeBSD? I have a question that I'm hoping someone over
> on your end might be able to help me with. I apologize if this email
> has reached the wrong person btw. :)
You need to divert bith directions.
On Tue, 10 Jul 2001, Peter Warrick wrote:
> I was referred to you by an Archie Cobbs who I guess did some of the
> ipfw code in FreeBSD? I have a question that I'm hoping someone over on
> your end might be able to help me with. I apologize if this email has
