Re: [SOGo] Different Apache configuration for internal/external requests

2013-01-20 Thread Anselm Martin Hoffmeister

Am 20.01.2013 01:17, schrieb Holger A. Brinkhaus:

Hi all,

at the moment //etc/apache2/conf.d/SOGo.conf/ is configured for external
access (which works via DynDNS). This works fine but also means that
this is also used for my internal access. For this reason I am limited
to external bandwidth also for my internal accesses. Is there a
possibility to change this?

Best Regards
   Holger



Hi Holger,

what I suspect is happening in your case (at least it seemed to be like 
that in a setup here):


Internal access to Sogo: Packets sent to public IP address go to the DSL 
device, are forwarded to the internet, go back - and such traverse the 
slow DSL line twice. A bit weird that the DSL device would not recognize 
its own external IP there... but I tracerouted it once.


You obviously have a server machine running locally, in the LAN. Is 
having a DNS server running on that feasible? What did the trick for us 
was using the Linux box as DNS-server for the LAN (be sure to configure 
the DHCP-server accordingly, or tell the DSL router to use that machine 
instead of the provider's DNS servers).


With the ISC BIND (well, there are others - I just know BIND best) you 
can allow recursive requests - that is a good idea for the local 
network. Don't necessarily set any forwarders there, the BIND can very

well talk to the DNS root servers itself.

Also create a local zone for myaccount.dyndns.org with something like

myaccount.dyndns.org. 300 IN SOA .
myaccount.dyndns.org. 300 IN NS myaccount.dyndns.org.
myaccount.dyndns.org. 300 IN A 192.168.55.5
myaccount.dyndns.org. 300 IN  2001:db8:fe24:2ff1::3705


This should make all DNS requests be answered normally except those
for the single DNS record of your dyndns name, for which your LAN 
clients are served the local IP address. The Apache will not need
any special configuration as long as you don't have any IP-address based 
stuff in there but go through the FQDN in all cases.


You could still differentiate in Apache by the source IP address, if 
that is at all necessary.


In my opinion this is not the most ideal solution, but far easier than
having a second FQDN, and also easier than f*ix*ing the routing tables.
DSL devices tend to be suckers when it comes to accessing their external
IP address from the internal LAN and forwarding ports to internal.

HTH
AMH
--
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] Documentation for installing funambol extension

2013-01-20 Thread Покотиленко Костик
В Птн, 18/01/2013 в 13:19 -0600, Jeff Folk пишет:
 http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf
 
 page 43

Maybe it worth considering inclusing Contents in the guide next time
it's touched?

 On Jan 18, 2013, at 1:09 PM, Holger A. Brinkhaus wrote:
 
  Hi,
  
  thanks a lot - but this document is for client side - i meant the needed 
  extension on server side
  
  Best Regards
Holger
  
  
  Am Freitag, 18. Januar 2013 20:01 CET, Jeff Folk jf...@qzoneinc.com 
  schrieb:
  
  The sig screwed up the link…
  
  http://www.sogo.nu/files/docs/SOGo%20Mobile%20Devices%20Configuration.pdf
  
  
  On Jan 18, 2013, at 12:53 PM, Jeff Folk wrote:
  
  
   On Jan 18, 2013, at 12:34 PM, Holger A. Brinkhaus wrote:
  
   Hi All,
  
   sorry for disturbing you with such question: But I am searching the 
   whole sogo-side and cannot find any help. From other topics in this 
   group I know that there has to be one documentation for funambol 
   integration to Sogo (or had been there). Can anybody provide me with 
   the right link (or document if not available any more on Sogo)
  
   Best Regards
   Holger
  
  
   http://www.sogo.nu/files/docs/SOGo%20Mobile%20Devices%20Configuration.pdf--
   users@sogo.nu
   https://inverse.ca/sogo/lists
  
  --
  users@sogo.nu
  https://inverse.ca/sogo/lists
  
  
  
  
 
 -- 
 users@sogo.nu
 https://inverse.ca/sogo/lists


-- 
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] Different Apache configuration for internal/external requests

2013-01-20 Thread Holger A. Brinkhaus
Hi Anselm,

yes - the situation is exactly as you have described it. Your suggestion is very good and I will test it today.

Best Regards
 Holger

Am Sonntag, 20. Januar 2013 10:57 CET, Anselm Martin Hoffmeister ans...@hoffmeister.be schrieb:


	Am 20.01.2013 01:17, schrieb Holger A. Brinkhaus:
	 Hi all,
	
	 at the moment //etc/apache2/conf.d/SOGo.conf/ is configured for external
	 access (which works via DynDNS). This works fine but also means that
	 this is also used for my internal access. For this reason I am limited
	 to external bandwidth also for my internal accesses. Is there a
	 possibility to change this?
	
	 Best Regards
	 Holger
	
	
	Hi Holger,
	
	what I suspect is happening in your case (at least it seemed to be like
	that in a setup here):
	
	Internal access to Sogo: Packets sent to public IP address go to the DSL
	device, are forwarded to the internet, go back - and such traverse the
	slow DSL line twice. A bit weird that the DSL device would not recognize
	its own external IP there... but I tracerouted it once.
	
	You obviously have a server machine running locally, in the LAN. Is
	having a DNS server running on that feasible? What did the trick for us
	was using the Linux box as DNS-server for the LAN (be sure to configure
	the DHCP-server accordingly, or tell the DSL router to use that machine
	instead of the providers DNS servers).
	
	With the ISC BIND (well, there are others - I just know BIND best) you
	can allow recursive requests - that is a good idea for the local
	network. Dont necessarily set any forwarders there, the BIND can very
	well talk to the DNS root servers itself.
	
	Also create a local zone for myaccount.dyndns.org with something like
	
	myaccount.dyndns.org. 300 IN SOA .
	myaccount.dyndns.org. 300 IN NS myaccount.dyndns.org.
	myaccount.dyndns.org. 300 IN A 192.168.55.5
	myaccount.dyndns.org. 300 IN  2001:db8:fe24:2ff1::3705
	
	
	This should make all DNS requests be answered normally except those
	for the single DNS record of your dyndns name, for which your LAN
	clients are served the local IP address. The Apache will not need
	any special configuration as long as you dont have any IP-address based
	stuff in there but go through the FQDN in all cases.
	
	You could still differentiate in Apache by the source IP address, if
	that is at all necessary.
	
	In my opinion this is not the most ideal solution, but far easier than
	having a second FQDN, and also easier than f*ix*ing the routing tables.
	DSL devices tend to be suckers when it comes to accessing their external
	IP address from the internal LAN and forwarding ports to internal.
	
	HTH
	AMH
	--
	users@sogo.nu
	https://inverse.ca/sogo/lists







Re: [SOGo] Documentation for installing funambol extension

2013-01-20 Thread Ludovic Marcotte

On 20/01/13 04:35, Покотиленко Костик wrote:

Maybe it worth considering inclusing Contents in the guide next time
it's touched?


How about reading the table of contents?

--
Ludovic Marcotte
+1.514.755.3630  ::  www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence 
(www.packetfence.org)

--
users@sogo.nu
https://inverse.ca/sogo/lists