NTL cable modems vs Empeg BBS

OK, so NTL cable-modem customers live on the wrong side of a transparent HTTP proxy on port 80. This is all well and good, except that the proxy isn't as "transparent" as it could be. In particular, it doesn't play nice with downstream proxies (neither Apache nor Squid) in such a way that I can't login to the BBS (and other denizens of Planet Empeg can log in via a double proxy, but not post).

So, er, Drakino, how about making the BBS available on empeg.comms.net:81 or :8080 or something as well as :80? Hopefully that's just a one-line change to httpd.conf...? That way accesses to it could bypass the broken transparent proxy, which only molests traffic on port 80.

(I need to run a downstream proxy because I've got my Windows PC behind a non-NAT firewall so that it doesn't access the Internet without me knowing.)

Peter

Works fine for me.. and the other NTL cable modem users here..

Rob

That's because you're not using a downstream proxy, Rob. If you do, it doesn't work properly (slightly different variants of broken behaviour, depending on whether you use squid or apache).

Ditto, I'm currently on ADSL but before I moved house, I'd been happily posting without any problems from my 512K NTL connection.

Oh well, it turns out (without wanting to bore everyone with the network topology in my new house) my Progear is outside my firewall, so I too can post to the BBS after a night on the pop. Be very afraid.

Peter

Actually, I appologise, I forgot all about this issue. If you want, I'll investigate the possibility of allowing access on another port. My main concern is if the BBS software will redirect you properly with the necessary :whatever in the URL.