Re: SMC Barricade 7008ABR port forwarding

The connection to port 25 on 192.168.1.7 gets established, data is exchanged and the connection is properly terminated. All this, while 192.168.1.7 "sees" the address XX.XXX.XXX.XXX.

This shows you that the replies from 192.168.1.7 get back beyond the SMC Barricade to the outside client that is trying to establish a connection to port 25 on the Barricade.

This would mean that the Barricade is actually applying NAT from the outside to the inside (instead of the other way around).

Could you try to disactivate NAT on the Barricade and check whether this changes its behavior with respect to the port forwarding problem. In that case, it's probably an bug in that part of SMC's firmware.

WiM

• Original Message ----- From: "nate" <vulndev@aphroland.org> To: <vuln-dev@securityfocus.com> Sent: Wednesday, November 27, 2002 7:25 AM Subject: SMC Barricade 7008ABR port forwarding

> I tried doing some googling but didn't come up with much.
win
> 32120 <nop,nop,timestamp 1368202 139100879> (DF)
> 00:08:52.305154 XX.XXX.XXX.XXX.65038 > 192.168.1.7.25: P 0:5(5) ack 1 win
win
> 32120 <nop,nop,timestamp 1368727 139101402> (DF)
is
> enough for alarm.
Received on Thu Nov 28 12:34:11 2002