Re: [Shorewall-users] multiISP on single interface

2007-01-08 Thread Roberto C. Sanchez
On Mon, Jan 08, 2007 at 05:07:47AM -0800, Vieri Di Paola wrote: I was wondering if there's a way to include multiple DSL lines on a single physical interface. I just ran out of ethernet cards and need to connect more lines, hopefully without having to setup a second shorewall gateway. If I

Re: [Shorewall-users] multiISP on single interface

2007-01-08 Thread Hristo Benev
Roberto C. Sanchez wrote: On Mon, Jan 08, 2007 at 05:07:47AM -0800, Vieri Di Paola wrote: I was wondering if there's a way to include multiple DSL lines on a single physical interface. I just ran out of ethernet cards and need to connect more lines, hopefully without having to setup a

Re: [Shorewall-users] multiISP on single interface

2007-01-08 Thread Andrew Suffield
On Mon, Jan 08, 2007 at 05:07:47AM -0800, Vieri Di Paola wrote: I was wondering if there's a way to include multiple DSL lines on a single physical interface. I think you can do this with PPPoE-forwarding modems (no PPP termination on the modem at all - *just* a modem which copies the PPPoE

Re: [Shorewall-users] shorewall/dansguardian/squid problem

2007-01-08 Thread Tom Eastep
paul cooper wrote: ive got a config thats client - server -Dansguardian-Squid - onward adn I want to transparently redirect web traffic to DG/Squid Not sure where the problem lies - hoping you guys can help me and at least tell me that its NOT my shorewall config heres the configs When

Re: [Shorewall-users] shorewall/dansguardian/squid problem

2007-01-08 Thread Tom Eastep
Tom Eastep wrote: paul cooper wrote: ive got a config thats client - server -Dansguardian-Squid - onward adn I want to transparently redirect web traffic to DG/Squid Not sure where the problem lies - hoping you guys can help me and at least tell me that its NOT my shorewall config heres

Re: [Shorewall-users] portforwarding from LAN to localhost

2007-01-08 Thread Sebastian Raring
Prasanna Krishnamoorthy wrote: Is your application even running on localhost? Sounds like it isn't. Try netstat -anp | grep 2048 and make sure that there's the corresponding process listening on 127.0.0.1:2048. Thanks for your idea. But the process is listening: [EMAIL PROTECTED]:/#

Re: [Shorewall-users] portforwarding from LAN to localhost

2007-01-08 Thread Tom Eastep
Sebastian Raring wrote: Prasanna Krishnamoorthy wrote: Is your application even running on localhost? Sounds like it isn't. Try netstat -anp | grep 2048 and make sure that there's the corresponding process listening on 127.0.0.1:2048. Thanks for your idea. But the process is

Re: [Shorewall-users] multiISP on single interface

2007-01-08 Thread Vieri Di Paola
--- Roberto C. Sanchez [EMAIL PROTECTED] wrote: Just get yourself some multi-port NICs. Intel and 3Com both make 2- and 4-port NICs. Hard to find and usually expensive although I did find a relatively cheap one: D-Link DFE 580TX - PCI - 10Base-T, 100Base-TX - 4 ports I just hope there's a

Re: [Shorewall-users] portforwarding from LAN to localhost

2007-01-08 Thread Andrew Suffield
[EMAIL PROTECTED]:/# netstat -anp Aktive Internetverbindungen (Server und stehende Verbindungen) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 127.0.0.1:2048 0.0.0.0:* LISTEN 8565/nc when I try with a

Re: [Shorewall-users] portforwarding from LAN to localhost

2007-01-08 Thread Jan Mulders
I should add,I don't think you need to make your app listen on 192.168.2.106- localhost should work too. Jan On 08/01/07, Jan Mulders [EMAIL PROTECTED] wrote: There's a better way. make your application listen on the external LAN interface - eg 192.168.2.106:2048, then add the following

Re: [Shorewall-users] portforwarding from LAN to localhost

2007-01-08 Thread Sebastian Raring
make your application listen on the external LAN interface - eg 192.168.2.106:2048 http://192.168.2.106:2048/, then add the This is a closed source app, and there are no config option for this app to make it work. I should add,I don't think you need to make your app listen on

Re: [Shorewall-users] portforwarding from LAN to localhost

2007-01-08 Thread Tressler, Joshua A.
Just had a thought when reading some of these replies. If this has been suggested and I skipped over it, I apologize. Could you just run squid and proxy the 2048 port over to 80? I've done similar things such as adding SSL to a non-ssl capable web appliance, but I think you could make it work.

Re: [Shorewall-users] multiISP on single interface

2007-01-08 Thread Will Murnane
On 1/8/07, Vieri Di Paola [EMAIL PROTECTED] wrote: Hard to find and usually expensive although I did find a relatively cheap one: D-Link DFE 580TX - PCI - 10Base-T, 100Base-TX - 4 ports I just hope there's a driver for Linux. Are you using this kind of cards? Are they working well? If you

Re: [Shorewall-users] portforwarding from LAN to localhost

2007-01-08 Thread Tom Eastep
Sebastian Raring wrote: make your application listen on the external LAN interface - eg 192.168.2.106:2048 http://192.168.2.106:2048/, then add the This is a closed source app, and there are no config option for this app to make it work. I should add,I don't think you need to make

Re: [Shorewall-users] portforwarding from LAN to localhost

2007-01-08 Thread Andrew Suffield
On Mon, Jan 08, 2007 at 06:27:36PM +, Tressler, Joshua A. wrote: Could you just run squid and proxy the 2048 port over to 80? That's exactly what my inetd/nc line did, only without the whole squid bit. squid's overkill for a simple port redirection. (inetd is how people used to do this