Hi Brian,

Can your e-mail system see the outside world via port 83?  In other
words, perhaps traffic can get in -- but can it get out?

Regards,
Kyle Spencer


On Tue, Jan 17, 2012 at 4:35 PM, brian lance <[email protected]> wrote:
> Hey Ronny,
>
> still using that broadbandcompany email!  well this is what i have got
> currently. Well the email in behind gateway. Internally can access webmail
> port 83.....but cannot access externally. If i can solve that the rest of
> the ports will fall in line.
>
> sudo iptables -t nat -L -n
> Chain PREROUTING (policy ACCEPT)
> target     prot opt source               destination
> premodules  all  --  0.0.0.0/0            0.0.0.0/0
> DNAT       tcp  --  0.0.0.0/0            41.210.160.198      tcp dpt:83
> to:192.168.1.2:83
> DNAT       tcp  --  0.0.0.0/0            41.210.160.198      tcp dpt:433
> to:192.168.1.1:443
>
> Chain POSTROUTING (policy ACCEPT)
> target     prot opt source               destination
> postmodules  all  --  0.0.0.0/0            0.0.0.0/0
> SNAT       all  -- !41.210.160.198       0.0.0.0/0
> to:41.210.160.198
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
>
> Chain postmodules (1 references)
> target     prot opt source               destination
>
> Chain premodules (1 references)
> target     prot opt source               destination
>
>
>
> iptables v1.4.4
>
> hain PREROUTING (policy ACCEPT)
> target     prot opt source               destination
> premodules  all  --  anywhere             anywhere
> DNAT       tcp  --  anywhere             router.opm.go.ug    tcp dpt:83
> to:192.168.1.2:83
> DNAT       tcp  --  anywhere             router.opm.go.ug    tcp dpt:433
> to:192.168.1.1:443
>
> Chain POSTROUTING (policy ACCEPT)
> target     prot opt source               destination
> postmodules  all  --  anywhere             anywhere
> SNAT       all  -- !router.opm.go.ug     anywhere
> to:41.210.160.198
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
>
> Chain postmodules (1 references)
> target     prot opt source               destination
>
> Chain premodules (1 references)
> target     prot opt source               destination
>
>
> Thanks.
>
>
> On Tue, Jan 17, 2012 at 12:18 PM, Ronny Muwonge <[email protected]>
> wrote:
>>
>> Hi  Brian
>>
>> You need to add a firewall rule to accept connections "From WAN to
>> Zentyal", port 25.
>> What have you done sofar?
>> Can you copy your rules and paste here.
>> Ronny
>>
>> On 01/17/2012 12:00 PM, brian lance wrote:
>>
>> I have justed installed a Zentyal gateway to my LAN, however I am having
>> Problems doing Portforwarding for my email Server which in on my LAN.
>>
>> here is the scenario:
>>
>> zentyal eth1 (WAN): 41.xx.xx.19
>> zentyal eth0 (LAN): 192.168.1.1
>> Email LAN server IP (connected to zentyal eth0): 192.168.1.2
>>
>> port forwarding goes like this:
>>
>> interface: eth1
>> original destination: 41.xx.xx.19
>> original destination port: 83
>> protocol: TCP/UDP
>> source: Any
>> destination IP: 192.168.1.2
>>
>> Kindly assist me in resolving this issue and let me know if i am doing
>> anything wrong in the port forwarding rules.
>> I wanted to be able to access my Webmail external via
>> http://41.xx.xx.19:83 since internally(working fine) i can access via
>> http://192.168.1.2:83.
>>
>>
>> _______________________________________________
>> The Uganda Linux User Group: http://linux.or.ug
>>
>> Send messages to this mailing list by addressing e-mails to:
>> [email protected]
>> Mailing list archives: http://www.mail-archive.com/[email protected]/
>> Mailing list settings: http://kym.net/mailman/listinfo/lug
>> To unsubscribe: http://kym.net/mailman/options/lug
>>
>> The Uganda LUG mailing list is generously hosted by INFOCOM:
>> http://www.infocom.co.ug/
>>
>> The above comments and data are owned by whoever posted them (including
>> attachments if any). The mailing list host is not responsible for them in
>> any way.
>>
>>
>>
>> --
>> -----------------------------------------------------------------------
>> "If I have seen further, it is by standing on the shoulders of giants."
>> -----
>> Bernard de Chartres
>> -----------------------------------------------------------------------
>>
>>
>> _______________________________________________
>> The Uganda Linux User Group: http://linux.or.ug
>>
>> Send messages to this mailing list by addressing e-mails to:
>> [email protected]
>> Mailing list archives: http://www.mail-archive.com/[email protected]/
>> Mailing list settings: http://kym.net/mailman/listinfo/lug
>> To unsubscribe: http://kym.net/mailman/options/lug
>>
>> The Uganda LUG mailing list is generously hosted by INFOCOM:
>> http://www.infocom.co.ug/
>>
>> The above comments and data are owned by whoever posted them (including
>> attachments if any). The mailing list host is not responsible for them in
>> any way.
>
>
>
> _______________________________________________
> The Uganda Linux User Group: http://linux.or.ug
>
> Send messages to this mailing list by addressing e-mails to: [email protected]
> Mailing list archives: http://www.mail-archive.com/[email protected]/
> Mailing list settings: http://kym.net/mailman/listinfo/lug
> To unsubscribe: http://kym.net/mailman/options/lug
>
> The Uganda LUG mailing list is generously hosted by INFOCOM:
> http://www.infocom.co.ug/
>
> The above comments and data are owned by whoever posted them (including
> attachments if any). The mailing list host is not responsible for them in
> any way.
_______________________________________________
The Uganda Linux User Group: http://linux.or.ug

Send messages to this mailing list by addressing e-mails to: [email protected]
Mailing list archives: http://www.mail-archive.com/[email protected]/
Mailing list settings: http://kym.net/mailman/listinfo/lug
To unsubscribe: http://kym.net/mailman/options/lug

The Uganda LUG mailing list is generously hosted by INFOCOM: 
http://www.infocom.co.ug/

The above comments and data are owned by whoever posted them (including 
attachments if any). The mailing list host is not responsible for them in any 
way.

Reply via email to