Koozali.org: home of the SME Server
Obsolete Releases => SME 8.x Contribs => Topic started by: dbaddour on February 03, 2014, 02:21:51 AM
-
Hi all,
New installation of the SME8 on new system.. Ran updated all went well.. I have MASQ to allow all traffic to go thru "to and From" the server is in "server and gateway dedicated". the main use is to allow traffic from 5.x subnet (main network of the office) to 2.x which most Development department data are.. the access between those subnet should be allowed to and from.
So what I have now is:
from 2.x I cannot ping the gateway and no other system on the 2.x
from 5.x I can ping the server but nothing else on the 5.x
cannot ping anything between the subnets.
my etc/rc.d/init.d/masq is set to allow all
/sbin/iptables --flush FORWARD
/sbin/iptables --flush INPUT
/sbin/iptables --flush OUTPUT
/sbin/iptables -F
/sbin/iptables -P FORWARD ACCEPT
/sbin/iptables -P INPUT ACCEPT
/sbin/iptables -P OUTPUT ACCEPT
Hint Idea please... this was working before running the update on the server... now I have no access to any at all
THanks in advance for your reply
Dave
-
dbaddour
Did you run
signal-event post-upgrade
signal-event reboot
after the yum update ?
my etc/rc.d/init.d/masq is set to allow all
/sbin/iptables --flush FORWARD
/sbin/iptables --flush INPUT
/sbin/iptables --flush OUTPUT
/sbin/iptables -F
/sbin/iptables -P FORWARD ACCEPT
/sbin/iptables -P INPUT ACCEPT
/sbin/iptables -P OUTPUT ACCEPT
... this was working before running the update on the server... now I have no access to any at all
How did you make those changes, direct to the masq file or by editing custom templates ?
Maybe your changes got lost during the upgrade, if you edited the file directly.
Check settings with
iptables -L
Did you power other involved devices off & on, after the sme server rebooted ?
-
dbaddour
No answers ?
If there is a problem it should be reported to bugzilla, so your feedback now is important to determine if a bug should be posted.
-
HI,
I am so sorry for the late reply..
I ran signal-event post-upgrade
signal-event reboot after the the update yes...
the changes I made is directly to the masq file..
what i can say that was a mis-spelling in the file.. that fixed.
the only thing that broke affter the upgrade was the SMTP relay to go thru the SME server... this i know for sure and suggest for the users when they do the upgrade to visit their settings in case are using sme GW and have the smtp going thru...
THank you for your help janet, sorry again for the late reply