aa.43.155.45 is the m0n0wall WAN IP
MAP 192.168.222.183 2069 <- -> aa.43.155.45 47193 [126.96.36.199 22]
age 471 use 0 sumd 0xee3c/0xee3c pr 6 bkt 437/266 flags 1 drop 0/0
ifp xl0 bytes 384 pkts 8
Hope this helps explaining what my issue is.
On Wed, 30 Mar 2005 10:06:12 -0500, Don Munyak <don dot munyak at gmail dot com> wrote:
> We have been using a commercial version Secure Shell from ssh.com on a
> windows2k workstation for the last two years. Outbound connectivity
> and firewalling was orignially managed using a cisco 1720 with
> reflexive acl's. I reviewed the old config file but didn't see where
> we had any special permit statements.
> I just implemented m0n0wall ver 1.11 . Now our LAN client is unable to
> connect to the remote ssh server. The application reports that either
> the firewall is not setup properly or the server is down.
> We checked with the server admin. Their server is working.
> I could use some help either trouble shooting this or with
> establishing a firewall pass rule
> - Don