On 07/28/2005 04:37:38 AM, Daniel Hartmeier wrote:
Assuming Windows ping is not doing that, you'll have to provide an
alternative way to decide which client to send replies to. There's
ICMP
sequence numbers, but they can and will overlap for concurrent ping
invokations. The ICMP echo reply quot
Okay ... so we have to look more closely ...
On Thursday 28 July 2005 14:47, Giovanni P. Tirloni wrote:
> I've deployed dozens of gateways with transparent HTTP proxy but this
> time it isn't working and I suspect pf is somehow involved in this.
> Packets aren't being redirected anywhere. I've d
Max Laier wrote:
One thing comes to my mind: What does
$sysctl net.inet.ip.forwarding
say?
# sysctl net.inet.ip.forwarding
net.inet.ip.forwarding: 1
I had some tweaks in /etc/sysctl but disabling them didn't help either.
#net.inet.ip.check_interface=1
#net.inet.tcp.blackhole=2
#net.inet.u
On Thursday 28 July 2005 14:47, Giovanni P. Tirloni wrote:
> Hello,
>
> I've deployed dozens of gateways with transparent HTTP proxy but this
> time it isn't working and I suspect pf is somehow involved in this.
> Packets aren't being redirected anywhere. I've disabled filtering
> totally to debu
Hello,
I've deployed dozens of gateways with transparent HTTP proxy but this
time it isn't working and I suspect pf is somehow involved in this.
Packets aren't being redirected anywhere. I've disabled filtering
totally to debug this.
I've a rule to redirect every connection attempt to port
On Thu, Jul 28, 2005 at 09:40:28AM +0200, Marcel Braak wrote:
> Before i had a linux/iptables firewall box that doesn't have this problem.
> I hope there's a fix for PF cause i think this is a very anoying issue.
You'll have to find out and explain to me how any other product
dispatches incoming
Melameth, Daniel D. wrote:
Pejman Moghadam wrote:
Melameth, Daniel D. wrote :
FWIW, while I haven't looked into this in detail, it appears Windows
clients always use the same ICMP ID--512...
I think this is right, beacuse of this state entry :
self icmp 192.168.1.18:512 -> 1.2
