KMS on OPNsense (pfSense Alternative)

Discussion in 'Application Software' started by AirstarGroup, Jan 16, 2019.

  1. AirstarGroup

    AirstarGroup MDL Novice

    Jan 16, 2019
    2
    1
    0
    Hello All!

    I have a home server (firewall) that is running OPNsense. I was wondering if anyone could help me with getting KMS-on-pfSense (I cannot post a link here, it's on GitHub though) to work? The current issue I'm having is that any time that I run vlmcsd commands it returns the following in SSH:

    Code:
    root@firewall:~ # vlmcsd -v
    Warning: [::]:1688: Address already in use
    Warning: 0.0.0.0:1688: Address already in use
    Fatal: Could not listen on any socket.
    Any ideas as to how I can fix this?
     
  2. tiphergane

    tiphergane MDL Novice

    Nov 26, 2010
    2
    0
    0
    Give us the result of the following commands :

    • ps aux | grep vlmcsd
    • netstat -tanpu | grep vlmcsd
    vlmcsd is the daemon, if you wanna check the server, you need to type vlmcs -v and the output will be:

    Code:
    vlmcs -v
    
    Request Parameters
    ==================
    
    Protocol version                : 6.0
    Client is a virtual machine     : No
    Licensing status                : 2 (OOB grace)
    Remaining time (0 = forever)    : 43200 minutes
    Application ID                  : 55c92734-d682-4d71-983e-d6ec3f16059f (Windows)
    SKU ID (aka Activation ID)      : e0b2d383-d112-413f-8a80-97f373a5820c (Windows 10 Enterprise G)
    KMS ID (aka KMS counted ID)     : 7ba0bf23-d0f5-4072-91d9-d55af5a481b6 (Windows 10 China Government)
    Client machine ID               : c454a140-a70a-48aa-8f42-2d03a267c958
    Previous client machine ID      : 00000000-0000-0000-0000-000000000000
    Client request timestamp (UTC)  : 2019-01-29 08:09:45
    Workstation name                : ceo-laptop.htc.pro
    N count policy (minimum clients): 25
    
    Connecting to 127.0.0.1:1688 ... successful
    
    Performing RPC bind ...
    ... NDR64 ... BTFN ... NDR32 ... successful
    Sending activation request (KMS V6) 1 of 1
    
    Response from KMS server
    ========================
    
    Size of KMS Response            : 260 (0x104)
    Protocol version                : 6.0
    KMS host extended PID           : 03612-03858-XXX-963629-03-6145-XXXXX.0000-2752674
    KMS host Hardware ID            : 3A1C04FFEDB60076
    Client machine ID               : c454a140-a70a-48aa-8f42-2d03a267c958
    Client request timestamp (UTC)  : 2019-01-29 08:09:45
    KMS host current active clients : 50
    Renewal interval policy         : 10080
    Activation interval policy      : 120 
     
  3. AirstarGroup

    AirstarGroup MDL Novice

    Jan 16, 2019
    2
    1
    0
    So, I got this to work actually. It automatically starts on system boot and is running with no issues whatsoever now. Thanks for the help!