Topic: ESmith Server Only and a Watchguard Firewall

[adamst]

Hi all,

I'm using Esmith behind a watchguard firewall.

All of the traffic that appears on the Watchguard appears to be coming from the Esmith server rather than the originator's IP (i.e. the user).

Is there something I can do to fix this so that the reports I see in Watchguard will be more accurate.

cheers,

Adam

[kmccarn]

Change your DHCP settings so that the Firebox is the gateway and not the SME.

This might be difficult if you are setup as server-gateway and all traffic is routed through the SME.

[adamst]

But what if I want to use the Esmith as a proxy server ?

cheers,

Adam

[kmccarn]

No problem - change the users network settings in IE (or Firefox) to use the SME as a proxy.

Although - the Firebox also has an http proxy capability - with webblocker if I remember correctly.

Of course - if you're using it as a proxy - all traffic to the firebox (for http) will look like it comes from the SME - no way around that.

 

[dhardy]

Configure the watchguard to be the default gateway in the dhcp as posted above. In the watchguard policy manager you can set a caching proxy - which you can set to be the SME box.

I haven't done this myself, although I have seen the entries in the policy manager .....  

HTH

David.

edit ...

Just goes to show that if you leave the forums up on your pc for 4 days someone has probably already replied to the post you are answering   must remember to refresh before posting!

[adamst]

Thanks for the tips !

I'll check it out and see how I go.

cheers