> On Wed, 2009-04-29 at 02:00 -0400, Tony Graziano wrote: > > I installed a 4.0 stable system from ISO yesterday. When doing so I > noticed the following: > > > > 1. Missing file /etc/redhat-release, which could be problematic with > > yum. > > How so? > > > 2. No yum repo for Centos or sipxecs installed, so shouldn't at least > > the sipxecs repo be installed by default. I'd prefer both with the > > CentOS repo disabled but present. > > > 3. DHCP option 120 test fails, and when setup as DHCP server it does > > not create the record for option 120. At the least there should be > > syntax in the sipxconfig gui to walk the superadmin through how to do > > that, as it's not exactly straightforward. >
I believe this may have been overlooked when this was closed: http://track.sipfoundry.org/browse/XX-4679 > Open an issue on these two, I think. > > > 4. Services "iptables" and "ip6tables" enabled at boot. While they > are > > not running after sipxecs is started, I would imagine they should be > > disabled by default. Personally I would prefer the binary files for > > those commands are non-executable to prevent any issue later on, as I > > have seen sporadic issues with earlier builds. > > We've had trouble with getting those to be disabled permanently - the > upstream rpms enable them, so whenever you update they get re-enabled. > As long as there are no problematic rules installed, the service itself > is harmless. > > > Do these make sense? If so, do any really warrant a tracker issue? > > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
