Koozali.org: home of the SME Server

[ SOLVED ] Setup SME as proxy for concurrent ADSL lines

Offline ddtpoison

  • 4
  • +0/-0
[ SOLVED ] Setup SME as proxy for concurrent ADSL lines
« on: March 03, 2010, 09:55:28 AM »
Hi,

First of: i am helping out our sysAdmin on this because he is swamped with other priorities. My linux and SME Server skills are intermediate.

We have two ADSL connections. One for the developers and one for management. Currently the one connection is running through PFSense and the other is currently running directly through the router no proxy setup at all. The preferred situation is that we would like both to run through the SME server, thus that the SME can act as proxy for both. We do not know how to do this yet, and i decided to start here while i hit the Google.

Our company is currently using a SME 7.4 as our primary server setup for everything else.

Questions thus would be, is it at all possible and if so would any one know how to or have a link to a tutorial/how to/documentation i can use to get started?
Thank you,
« Last Edit: March 05, 2010, 08:56:24 AM by ddtpoison »

Offline Stefano

  • *
  • 10,894
  • +3/-0
Re: Setup SME as proxy for concurrent ADSL lines
« Reply #1 on: March 03, 2010, 10:35:01 AM »
SME doesn't support multi wan..

so you should put something in front of it (pfsense is, IMO, a good choice)
« Last Edit: March 03, 2010, 10:40:23 AM by Stefano »

Offline ddtpoison

  • 4
  • +0/-0
Re: Setup SME as proxy for concurrent ADSL lines
« Reply #2 on: March 05, 2010, 08:52:52 AM »
Thank you Stefano for the info.

It is a shame that SME does not support multi wan. With some research i found ClearOS which we could setup quickly and use as proxy seperate from the SME server. Initial setup and testing proves it does support multi wan succesfully and its repoprting on traffic is sufficiant.
But its user interface and the level of controls one has is much less than with SME user/manager interface.

I will try out the pfsense setup later when management is happy that something is up and running now which resolved the issue. :)