I have same issue with port forwarding. thought it was a config problem for me. I have SSH on a non-standard port on the WAN side and it is supposed to be forwarding to standard port 22 on the LAN side server. I get a connection established, but no data (not even a logon prompt) and then about 15 seconds later it will finally drop the connection. -Sean
> Date: Wed, 26 Sep 2007 12:50:50 +1000> From: [EMAIL PROTECTED]> CC: > [email protected]> Subject: [pfSense Support] Re: jabber and NAT woes> > > I've done a further test. I also get my connection dropped if I use ssh> and > ssh to a public IP address that is port forwarded to a server in the> LAN.> > > So I'm guessing this issue is something to do with NAT on pfSense,> rather > than ejabberd.> > Any help will be very appreciated.> > Geoff Crompton > wrote:> > We've just transition from using IPCop 1.4.13 to using pfSense > 1.2-RC2.> > The transition wasn't so bad. However we are having problems with > jabber> > connections now.> > > > Our ejabberd (version 1.1.2-6, from the > Etch Debian package) runs inside> > a vserver in our dmz zone. Our domain > name jabber.strategicdata.com.au> > resolves to the IP address on the WAN > interface (not an Virtual IP). We> > have configured NAT rules to port > forward the connections to the> > ejabberd vserver.> > > -- > Geoff Crompton> > Debian System Administrator> http://www.strategicdata.com.au> Phone: +61 3 > 9340 9000> Fax: +61 3 9348 2015> > > ---------------------------------------------------------------------> To > unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail: > [EMAIL PROTECTED]> _________________________________________________________________ Connect to the next generation of MSN Messenger http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline
