Re: [SLUG] Port forwarding weirdities

2009-11-03 Thread db
There is a known bug in openwrt, at least on the 2.4 kernel. The bug is that ... After some period time, forwarding a port from X to Y will break :) (forwarding will go screwy ). (where X / Y are different port numbers) You can forward from Y to Y reliably or should at least should be able

Re: [SLUG] Port forwarding weirdities

2009-11-03 Thread Jeremy Visser
On Tue, 2009-11-03 at 22:00 +1100, db wrote: There is a known bug in openwrt, at least on the 2.4 kernel. The bug is that ... After some period time, forwarding a port from X to Y will break :) [citation needed] Do you have a link I could follow up on that with? My Google-Fu has failed me

Re: [SLUG] Port forwarding weirdities

2009-11-03 Thread Ishwor Gurung
Hi Jeremy, 2009/11/3 Jeremy Visser jer...@visser.name: On Wed, 2009-10-28 at 21:37 +1100, Ishwor Gurung wrote: What about just dumping NAT table i.e., without the grep magic foo? Sure. I've attached an `iptables -t nat -L` from working, and broken. [...] What's weird is that the line that

Re: [SLUG] Port forwarding weirdities

2009-11-03 Thread Jeremy Visser
On Tue, 2009-11-03 at 23:34 +1100, Ishwor Gurung wrote: Hrmm. Try patching it against r17555 and see how it goes - https://dev.openwrt.org/changeset/17555. There are a bunch of fixes in r16278 plus try disable QOS'ing packets (seems to be the common wisdom of the ticket discussion) Aha.

Re: [SLUG] Port forwarding weirdities

2009-11-02 Thread Jeremy Visser
On Wed, 2009-10-28 at 21:37 +1100, Ishwor Gurung wrote: What about just dumping NAT table i.e., without the grep magic foo? Sure. I've attached an `iptables -t nat -L` from working, and broken. (Not sure if such attachments are allowed on this list, but I have seen some pretty hideous

Re: [SLUG] Port forwarding weirdities

2009-10-30 Thread Jeremy Visser
On Wed, 2009-10-28 at 19:26 +1100, pe...@chubb.wattle.id.au wrote: See if there's another iptables rule redirecting output port 80 to somewhere else. I'm using white russian in almost exactly this config, and it's all working for me. I've been meaning to get back to you on this, and in

[SLUG] Port forwarding weirdities

2009-10-28 Thread Jeremy Visser
G'day SLUG, Okay, so, I have a Linksys WRT54G running OpenWrt, serving as the Internet router for our home. You know the drill — NAT, PPPoE, whatever. Router's LAN IP address is 192.168.0.1. Several port forwards are in place (y'know — SSH, HTTP, SMTP, IMAP, and whatnot) that are already working

Re: [SLUG] Port forwarding weirdities

2009-10-28 Thread peter
Jeremy == Jeremy Visser jer...@visser.name writes: Jeremy Okay, so, I have a Linksys WRT54G running OpenWrt, serving as Jeremy the Internet router for our home. You know the drill — NAT, Jeremy PPPoE, whatever. Yup, same as I have Jeremy Router's LAN IP address is 192.168.0.1. Several port

Re: [SLUG] Port forwarding weirdities

2009-10-28 Thread Ben Donohue
I've only ever port forwarded port 80 from external to port 80 on an internal web server. A client picks a high port and sends this request to port 80 on the web server. The web server responds out from port 80 to the high port on the client. So from a router it would port forward any

Re: [SLUG] Port forwarding weirdities

2009-10-28 Thread Ishwor Gurung
Hi, Okay, so, I have a Linksys WRT54G running OpenWrt, serving as the Internet router for our home. You know the drill — NAT, PPPoE, whatever. Router's LAN IP address is 192.168.0.1. Several port forwards are in place (y'know — SSH, HTTP, SMTP, IMAP, and whatnot) that are already working