Re: [SOGo] Using SOGo behind a router
Hi Stefan an others, thanks for your advice, I'll try it both ways. If I'm successful, I'll report it, otherwise, too ;) Thanks very much, Greets Tim Am 07.04.2012 um 23:16 schrieb Stefan Klatt: Am 07.04.2012 19:39, schrieb Romain LE DISEZ: Hi Tim, a better description of the problem than it does not work could help. But, here is my idea. When configuring a SOGo server, you configure Apache to set some headers that indicate to SOGo the URL/port used for the connection. If it work internally, you probably set those headers: RequestHeader set x-webobjects-server-port 80 RequestHeader set x-webobjects-server-name 192.168.1.3 RequestHeader set x-webobjects-server-url http://192.168.1.3; But these values are incorrects when accessing from the outside. Try to change these values with the outside URL / port: RequestHeader set x-webobjects-server-port 665 RequestHeader set x-webobjects-server-name 140.134.120.134 RequestHeader set x-webobjects-server-url http://140.134.120.134:675; If it works, you found the problem. The fix is to create two vhosts in Apache. You can also use a generic configuration (but for the port forwarding, you must have inside port = outside port). See the diff attached for a generic Apache configuration (generated on a CentOS, can't guarantee it is applicable on a Debian). It's better to work with (dynamic) DNS names. For this you need an internal DNS server which resolves the internal IP address for the (dynamic) name you use external and you get everytime the right IP address. If you have no DNS server in your local network you can use an entry at the local host table on each PC or on the firewall/router (if this is supported). Stefan -- *CaC, Computer and Communication* Inhaber Stefan Klatt End-2-End Senior Network Consultant Triftstrasse 9 60528 Frankfurt Germany USt-IdNr.: DE260461592 Tel.: +49-(0)172-6807809 Tel.: +49-(0)69-67808-900 Fax: +49-(0)69-67808-837 Email: stefan.kl...@cac-netzwerk.de stefan_klatt.vcf -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Using SOGo behind a router
Hi Marc, hi Christian, sry for not describing my setup in detail: Lets say the subnet behind the router is something like: 192.168.1.0/24 The WAN in which the router is placed is the 140.134.120.134 subnet. When I try to connect to SOGo via lightning or webinterface in the subnet (192.168...) everything works. But when I connect to the subnet via port forwarding through the router (port 675 is forwarded to the internal address of the SOGo server (say its 192.168.1.3) on port 80) it does not work. How should a setup look like to fully connect with the SOGo server from outside (140.134.12)? Thanks in advance and happy easter, Tim Am 05.04.2012 um 11:49 schrieb Christian Mack: Hello Tim Am Donnerstag, 05. April 2012 11h:10m CEST, Kniggedigge kniggedi...@freenet.de schrieb: I just tried to use SOGo behind a router in a subnet. When I'm accessing SOGo in the subnet, there's no problem. But when I try to access SOGo from the WAN, the address is always rewritten. Is there anybody who figured out how to configure apache, so that it is possible to access SOGo from the outside? Obviously your Router uses NAT. So it always rewrites the IP of the Sender to its own. And in order to reach your server behind it, you have to use the IP of your router instead of the IP of your SOGo server. That's how NAT works! You could use the same DNS name from inside and outside, if you use split DNS. This means, if you search with the DNS name of your SOGo server, you have to provide to the Internet the IP of your router and for your subnet you provide the IP of your real SOGo server. This only works with 2 DNS servers with different information, which must be kept synchronized. Kind regards, Christian Mack -- Christian Mack Rechenzentrum Universitauml;t Konstanz mailto:christian.m...@uni-konstanz.de http://www.rz.uni-konstanz.de/ -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Using SOGo behind a router
Hi Tim, a better description of the problem than it does not work could help. But, here is my idea. When configuring a SOGo server, you configure Apache to set some headers that indicate to SOGo the URL/port used for the connection. If it work internally, you probably set those headers: RequestHeader set x-webobjects-server-port 80 RequestHeader set x-webobjects-server-name 192.168.1.3 RequestHeader set x-webobjects-server-url http://192.168.1.3; But these values are incorrects when accessing from the outside. Try to change these values with the outside URL / port: RequestHeader set x-webobjects-server-port 665 RequestHeader set x-webobjects-server-name 140.134.120.134 RequestHeader set x-webobjects-server-url http://140.134.120.134:675; If it works, you found the problem. The fix is to create two vhosts in Apache. You can also use a generic configuration (but for the port forwarding, you must have inside port = outside port). See the diff attached for a generic Apache configuration (generated on a CentOS, can't guarantee it is applicable on a Debian). Greetings. Le Samedi 07 Avril 2012 13:54 CEST, Kniggedigge kniggedi...@freenet.de a écrit: Hi Marc, hi Christian, sry for not describing my setup in detail: Lets say the subnet behind the router is something like: 192.168.1.0/24 The WAN in which the router is placed is the 140.134.120.134 subnet. When I try to connect to SOGo via lightning or webinterface in the subnet (192.168...) everything works. But when I connect to the subnet via port forwarding through the router (port 675 is forwarded to the internal address of the SOGo server (say its 192.168.1.3) on port 80) it does not work. How should a setup look like to fully connect with the SOGo server from outside (140.134.12)? Thanks in advance and happy easter, Tim Am 05.04.2012 um 11:49 schrieb Christian Mack: Hello Tim Am Donnerstag, 05. April 2012 11h:10m CEST, Kniggedigge kniggedi...@freenet.de schrieb: I just tried to use SOGo behind a router in a subnet. When I'm accessing SOGo in the subnet, there's no problem. But when I try to access SOGo from the WAN, the address is always rewritten. Is there anybody who figured out how to configure apache, so that it is possible to access SOGo from the outside? Obviously your Router uses NAT. So it always rewrites the IP of the Sender to its own. And in order to reach your server behind it, you have to use the IP of your router instead of the IP of your SOGo server. That's how NAT works! You could use the same DNS name from inside and outside, if you use split DNS. This means, if you search with the DNS name of your SOGo server, you have to provide to the Internet the IP of your router and for your subnet you provide the IP of your real SOGo server. This only works with 2 DNS servers with different information, which must be kept synchronized. Kind regards, Christian Mack -- Christian Mack Rechenzentrum Universitauml;t Konstanz mailto:christian.m...@uni-konstanz.de http://www.rz.uni-konstanz.de/ -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists -- Romain LE DISEZ Support technique, Netensia Administratif Commercial : +33 811 555 005 (prix d'un appel local) Support Hébergement : +33 2 97 69 05 68 Télécopie : +33 2 97 68 14 01 -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Using SOGo behind a router
Am 07.04.2012 19:39, schrieb Romain LE DISEZ: Hi Tim, a better description of the problem than it does not work could help. But, here is my idea. When configuring a SOGo server, you configure Apache to set some headers that indicate to SOGo the URL/port used for the connection. If it work internally, you probably set those headers: RequestHeader set x-webobjects-server-port 80 RequestHeader set x-webobjects-server-name 192.168.1.3 RequestHeader set x-webobjects-server-url http://192.168.1.3; But these values are incorrects when accessing from the outside. Try to change these values with the outside URL / port: RequestHeader set x-webobjects-server-port 665 RequestHeader set x-webobjects-server-name 140.134.120.134 RequestHeader set x-webobjects-server-url http://140.134.120.134:675; If it works, you found the problem. The fix is to create two vhosts in Apache. You can also use a generic configuration (but for the port forwarding, you must have inside port = outside port). See the diff attached for a generic Apache configuration (generated on a CentOS, can't guarantee it is applicable on a Debian). It's better to work with (dynamic) DNS names. For this you need an internal DNS server which resolves the internal IP address for the (dynamic) name you use external and you get everytime the right IP address. If you have no DNS server in your local network you can use an entry at the local host table on each PC or on the firewall/router (if this is supported). Stefan -- *CaC, Computer and Communication* Inhaber Stefan Klatt End-2-End Senior Network Consultant Triftstrasse 9 60528 Frankfurt Germany USt-IdNr.: DE260461592 Tel.: +49-(0)172-6807809 Tel.: +49-(0)69-67808-900 Fax: +49-(0)69-67808-837 Email: stefan.kl...@cac-netzwerk.de attachment: stefan_klatt.vcf signature.asc Description: OpenPGP digital signature
[SOGo] Using SOGo behind a router
Hi folks, I just tried to use SOGo behind a router in a subnet. When I'm accessing SOGo in the subnet, there's no problem. But when I try to access SOGo from the WAN, the address is always rewritten. Is there anybody who figured out how to configure apache, so that it is possible to access SOGo from the outside? Thanks for your help in advance, Greets Tim-- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Using SOGo behind a router
Hello Tim Am Donnerstag, 05. April 2012 11h:10m CEST, Kniggedigge kniggedi...@freenet.de schrieb: I just tried to use SOGo behind a router in a subnet. When I'm accessing SOGo in the subnet, there's no problem. But when I try to access SOGo from the WAN, the address is always rewritten. Is there anybody who figured out how to configure apache, so that it is possible to access SOGo from the outside? Obviously your Router uses NAT. So it always rewrites the IP of the Sender to its own. And in order to reach your server behind it, you have to use the IP of your router instead of the IP of your SOGo server. That's how NAT works! You could use the same DNS name from inside and outside, if you use split DNS. This means, if you search with the DNS name of your SOGo server, you have to provide to the Internet the IP of your router and for your subnet you provide the IP of your real SOGo server. This only works with 2 DNS servers with different information, which must be kept synchronized. Kind regards, Christian Mack -- Christian Mack Rechenzentrum Universitauml;t Konstanz mailto:christian.m...@uni-konstanz.de http://www.rz.uni-konstanz.de/ -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Using SOGo behind a router
Tim, Kniggedigge schrieb (05.04.2012 11:10 Uhr): I just tried to use SOGo behind a router in a subnet. When I'm accessing SOGo in the subnet, there's no problem. But when I try to access SOGo from the WAN, the address is always rewritten. I think, what you want to tell is that your problem is with NAT, isn't it? You come across a lot of routers while using the internet, and this is probably alway fine. :) Is there anybody who figured out how to configure apache, so that it is possible to access SOGo from the outside? It think you have to tell a few more details about your configuration and your the issues you see. Marc -- users@sogo.nu https://inverse.ca/sogo/lists
