Long story short, I copied a lot of data into v7 flexshares using WinSCP and found that users couldn't do anything meaningful with them.
Looking deeper it's because they were all owned by "root", the account I used for WinSCP.
In the process of chown the shares for users and/or groups I think I may have inadvertently run a chown over the root, /, directory.
The system still works fine for proxy and user directories but flexshares do not work. They still show but cannot be accessed.
More importantly I can now not login to the web GUI. I was hoping to login and delete the flexshares and then recreate them and copy the data using windows shares as this preserves the permissions.
Logging in as root says password invalid
Logging in as a user I get "LDAP Offline".
Can I fix this without rebuilding the server?
I have several community v7 systems that did an update last night
and now the marketplace is empty.
I have one v7 community system that hasn't applied these updates and it's fine as are the v7 Business versions.
I have updated the affected community system and marketplace is now empty.
Did last nights update change anything fundamental.
Is it possible to have a physical interface VLAN'd and the one of those VLAN having an additional virtual IP
What I would like to do is add Virtual IP, 10.10.11.1 to eno2.100.
I can't just add it to eno2 as the layer 3 switch rejects the packets. So can I create an eno2.100:1 = 10.10.11.1
For any one looking for the answer for this the solution was to put the
into the dhcp.conf file for the visitor network.
That way any Avaya phone coming into the switch gets tagged as VLAN 200 and so served an address by the VLAN 200 DHCP server.
We have upgraded our COS v5 to V7.3 and now our Avaya handsets are not getting the correct address from the ClearOS.
There are four physical interfaces, External, LAN, Corporate WAN and Visitor. - IP Settings.PNG
The LAN interface is set up for three VLANs with no IP address on the physical interface.
VLAN 100 - LAN
VLAN 102 - Second LAN
VLAN 200 - VOIP
DHCP is enabled on two of the VLANs and also the Visitor interface. - DHCP-Settings.PNG
A handset plugged into port 5 on the switch is being served an address from the Visitor LAN.
Excerpt from Switch Config file:
Relevant bit of DHCP.conf
At the moment we are manually setting the IP address for each handset.
OK, thanks for that, it makes a lot of sense.
I am trying to get Avaya handsets to get a DHCP address in the correct VLAN/subnet and had added a line to the dnsmasq.conf file and just wanted to restart the service without restarting the server.
Still not working as planned on a handset level, but that's a topic for a new thread.
Dave Loper wrote:
I don't know that the term 'oversight' is appropriate here. DNSmasq not only provides DHCP services but it is also the foundation for a number of services which required a functioning DNS server. The services include:
...and every single update including security updates.
Simply stopping in essentially breaks a number of things. If you are skilled enough to compensate for these by properly assembling a replacement or by over the architecture of the DNS of the server with some replacement then it will also be trivial for you do the other types of things that does whatever it is that you need to do. Some of these other tasks include:
Disabling the consumption of port 53 by DNSMasq by setting the port parameter to '0'.
Rolling in Bind and DHCPd from ISC because you want to use them instead.
The purpose for not having the start/stop button is to save people from breaking essential functions of the system. Feel free to do it manually but having that button NOT there is a good thing and will save a lot of heartache for those people who don't know/realize that the DHCP services is also the same thing that is making it so that there server can run DNS resolution on their updates.