Re: [squid-users] Configuring Squid to run with Elster Client

From: Juri Haberland <list-squid.users@dont-contact.us>
Date: Wed, 25 Jun 2003 12:42:23 +0000 (UTC)

"Michael Ehlers" <mehlers@adata.de> wrote:

> for using the Elster Windows Client (www.elster.de) this needs spezial
> requirements. The internal running Port 3128
> works fine for internet browsing. But Elster needs spezial Entries we have
> implemented in /etc/squid.conf
> but not working.
>
> Elster needs for the local Network the following Ports:
>
> 1024 --> Gateway to 62.157.211.58 Port 8000
> 1025 --> Gateway to 62.157.211.59 Port 8000
> 1026 --> Gateway to 194.112.100.70 Port 8000
> 1027 --> Gateway to 193.109.238.26 Port 8000
> 1029 --> Gateway to 193.109.238.27 Port 8000
>
> *The IP-Adresses are spezial Servers of Elster
>
> We have this Gateway functionality testet in JanaProxy (Konfiguration
> Example: http://www.voks.de/Programminfos/Konfiguration_AVMKEN_Jana.pdf)
> and this works from the same Server in Windows VMWare Session. The Host
> System ist SuSE Linux 8.0. In the future all German companies
> would work with Elster and if they are using Squid Proxy this should work.

Hmm, does this application talk HTTP to these special servers? If not,
then Squid is not the right tool. Assuming it's a special protocol you
need either a generic proxy or just open up the firewall for those
clients to talk on these special ports to those servers.
Another approach could be to use the DNAT (destination address
translation) functionality of ithe Linux iptables firewall.

And slap the developers of Elster for not using standard protocols.
This will be much fun for a lot of german systems administrators...

Cheers,
Juri

-- 
Juri Haberland  <juri@koschikode.com> 
Received on Wed Jun 25 2003 - 06:42:16 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:17:38 MST