@astrugatch I don’t think it matters really. The issue was more about the initial pinning of the certificate during the install process. After it is pinned I think this is the correct expectation (it should only communicate to the FOG server over HTTPS).

@astrugatch Okay thanks and sorry there was that issue.

Can you pull and try installing again?

Thank you!

@astrugatch we have firewalld but you can make the adjustments… some ports have been changed from the initial setup due to network restrictions.

- name: FOG_Services short: FOG Server network rules description: >- For FOG Server to handle boot, image and various tasks on workstations sources: - SUBNET_IPS allow_icmp: - echo-request - echo-reply services: - ftp - http - mountd - nfs - rpc-bind - tftp ports: - { port: 20048, proto: tcp } # nfs - { port: 20048, proto: udp } # nfs - { port: "35350-36350", proto: udp } # tftp - { port: "49512-65532", proto: udp } # multicast

@Florent For removal of the FOG Client, a connection to the server is not needed.

The only reason it’s needed during install is because it’s communicating to the fog server to get the certificates needed from the server. These certificates are not necessary to remove the software.

Nevermind. For whatever reason my host module settings were all deselected. No idea why. I am using persistent groups and these are set in that group.

When I run :

SELECT * FROM hostMAC WHERE hmMAC LIKE '%aa:bb:cc:dd:ee:ff%'; SELECT * FROM hosts WHERE hostID IN (SELECT hmHostID FROM hostMAC WHERE hmMAC LIKE '%aa:bb:cc:dd:ee:ff%');

I get output pertaining to the host that I had deleted via the GUI. Is there a way to delete those records from the DB using the MAC?

Finally got a chance to run the upgrade again and figured out my issue.

For some reason safari wasn’t happy with the upgrade. I can open fog fine from a private window or if I cleared history. It doesn’t open in Chrome, which was my other test because chrome doesn’t trust the ssl cert and no longer gives an option to bypass by default.

@astrugatch said in Script to detect and repair AD Biding:

Is that separate from the cert that is used for HTTPS? Do I need to generate a new cert or does that come from the install as long as it is recent?

It’s separate from the cert used for HTTPS. Nothing you need to mess with. It’s a code siging certificate and it’s bundled into the fog-client. So if you use a recent one you are good to go.

@astrugatch if this host isn’t already registered, this can be enabled globally, and likely won’t hurt anything even if it’s forgotten about.

FOG Configuration Page -> FOG Settings -> KERNEL ARGS add noapic

@astrugatch Latest laster is 1.5.9 as of now. There have been a fair amount of fixes since then. I would suggest you use dev-branch to make sure you have all those fixes included.

@astrugatch I haven’t done anything on this yet.

@moderators would there be any issue with using a forums topic to host torrent files for a fog VM image?

@Sebastian-Roth

Now that I have the necessary MAC addresses at least associated with the machine I am good for now. I will wait for a final release before I move. This isn’t a deal breaker kind of issue for me.

@astrugatch Good to know this was caused by browser caching. I can imagine more people running into this. Thanks!

@george1421

Looked through the guide and everything matched, it was just the tftp server password that was wrong.

@astrugatch Yeah, probably a good idea. We’d need to do extensive testing on this. E.g. iPXE boot, fog-client, storage nodes (php curl calls) and so on.

PS: Moved to feature request.

For 1.5.X LDAP ports were being applied within the database, but not used in all areas. I have since fixed this so it will use the ports list defined by the user instead of predetermined ports.

@Sebastian-Roth

fogadmin@fogimaging:~$ ls -al /var/www && ls -al /var/www/html total 16 drwxr-xr-x 4 root root 4096 Feb 13 10:53 . drwxr-xr-x 14 root root 4096 Sep 11 2017 .. drwxr-xr-x 10 www-data www-data 4096 Feb 13 11:04 fog drwxr-xr-x 2 root root 4096 Sep 11 2017 html total 20 drwxr-xr-x 2 root root 4096 Sep 11 2017 . drwxr-xr-x 4 root root 4096 Feb 13 10:53 .. lrwxrwxrwx 1 root root 13 Sep 11 2017 fog -> /var/www/fog/ -rw-r--r-- 1 root root 10701 Sep 11 2017 index.html

@george1421 Thanks for the input!

I’m not looking to specifically put F2B in; I am putting in code to log to a file login failures and successes, then the SysAdmin can choose to setup a F2B jail based on that. I believe heavily in separation of responsibilities, so I will definitely look into writing a proper tutorial.

Do you think code for simply logging the login attempts would get merged?