Applications

Toggle Sidebar
News Feed
  • Nick Howitt

    At a guess, have a look at the Marketplace app. When it goes to the installing part, you get a progress bar.

  • I googled a bit with mixed results. There were a couple of ideas. One was to give the PPTP adaptor IP settings a WINS server pointing to your remote WINS server (the DC?). The other was not to use a split tunnel and force all traffic through the VPN.

  • I don't think it is possible to use NetBIOS names over a VPN. superuser.com answer.

  • For anyone bumping into this thread, copying in the system certificates is a slight hack. It is perhaps better to copy in the bootstrap certificates:
    You are copying in the bootstrap.crt twice as it is a self-signed certificate.

    From what I've recently seen, the key file is not being copied in correctly. The two certificate files exactly match the bootstrap.crt file.

    Alternatively you can probably change to point /etc/openldap/slapd.conf to the certificates in /etc/openldap/cacerts/:
    I think this folder is a hangup from the ClearOS 6.x days, but certificates are still being placed there, even though they are not used.

    For the really adventurous, you can probably use Let's Encrypt certificates following the methodology in the Using Let's Encrypt Certificates for Mail howto.

  • Nick Howitt
    Nick Howitt's reply was accepted as an answer

    Re: Clearos is not rebooting

    Do you see anything in the message log or from the command "dmesg".

    You can also try the command:

  • Hmmm

    I installed the new LAN card and logged into the system through the WAN interface. The replacement card shows up as a new ethernet interface but it says "no link" on the IP Settings even though I've configured it for a static IP. I booted the machine off a Linux Live DVD and the card's ok.

    Where to next?

    Thanks

  • Hi Shannon,
    Ben has been trying to reply to ticket 564332 but at a guess the replies are not going to you. Please can you have a look at the ticket for the response.

  • Thinking about it, on your master/slave set up, if you have /etc/pki/CA/private/ca-key.pem on either box, you can grab back your ca-cert from any openvpn client. I may also have a look to see if it is copied elsewhere as a number of programs use it. Unfortunately they may just use the bootstrap certificate rather than the ca-cert.

    If we can recover the ca completely, you'll just need to generate new system certificates. This should force you to restart OpenVPN but otherwise have no impact on the OpenVPN clients as everyone is using the same ca-cert. Just don't restart OpenVPN for the moment! It should fail without certificates.

  • I'll be speaking to the devs in an hour or so. On your Master/Slave set up, does the slave have the certificates, by any chance? Also does /etc/pki/CA/private/ca-key.pem exist on either box?

  • This depends on how adventurous you feel. The direct way is to add the network card and reboot. Log on to the console and note the IP address of the failed interface. If you want to have the same settings on the new interface, you have to either delete this interface or change its network setting to something in a different subnet. Then configure your new interface as LAN with the old IP address of the old interface. You can't get to the DHCP server here. If you can get to the Webconfig via the WAN IP then do that and go and delete the old DHCP server and configure the new one. Then plug into the new LAN and it should work. If you can't do that, plug you PC into the new NIC and if you don't get a connection/IP address, you'll need to manually configure the PC with an IP address on the same LAN as the new NIC. You'll then be able to connect to the Webconfig and configure the DHCP servers correctly.

    If you feel adventurous, once you've powered up ClearOS with the new NIC, note the LAN interface name and the new card name. Then drop to the command line in the console and edit the file /etc/udev/rules.d/70-persistent-net.rules with either vi (yuck) or nano and swap over the "NAME" of your working and non-working interfaces. Save the file then reboot - use the command "reboot" from the command line. You should then be up and running again.

    Note Windows may well detect a new network either way as the LAN interface has a new MAC address.