Okay for anyone still around, I was able to get this sorted, it appears that the initial file I was using was either corrupted or maybe a patch for an existing installation.

I've documented the process, copied below for reference. I won't be sharing IBMs RPM's on this post. You should be able to get these directly from IBM's website free of charge, but your mileage may vary.

Installing IBM Datapower on CentOS 8/9 or Rocky Linux 8/9 to your Hypervisor/Cloud Provider

Minimum System Requirements
• 4 vCPU
• 16 GiB RAM
• 80 GiB Disk Space
• 4 Network Interfaces – with DHCP or Statically Assigned IPs
• 2 Available Loop devices – Documented Below
• Default Partitioning will work, can be configured to meet any security requirements (separate LV for VAR for example)
• Installation without a GUI recommended with these below features
◦ “Server Installation” Option
▪ Guest Agents (Drivers for Hypervisor/Cloud recommended)
▪ Remote Management for Linux recommended – SSH and or Cockpit
• Root only account – User accounts are unnecessary
• Security Policy to adhere to any State/Fed requirements (may effect Installation Destination configuration – not documented here).

Configure Timezone and any other settings as required – no specific documentation needed

Sample User: root
Password: your-password

Upon installation check for updates and install a few required repositories.

sudo dnf update -y sudo dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm sudo dnf update -y sudo dnf search schroot sudo dnf install schroot ipvsadm kmod telnet -y

Post installation of dependencies we need to confirm our loop devices are configured.

Confirm what loop devices exist (likely there is only 1) so we’ll need to create some with the below.

List your loop devices:

ls -l /dev/loop* brw-r----- 1 rootls disk 7, 0 Jul 24 17:49 /dev/loop-control

We only have the loop-control device, so create two more loop devices with the below.

mknod -m660 /dev/loop1 b 7 8 mknod -m660 /dev/loop2 b 7 8

Confirm the devices are listed.

ls -l /dev/loop* brw-rw----. 1 root root 7, 8 Nov 27 08:10 /dev/loop1 brw-rw----. 1 root root 7, 8 Nov 27 08:10 /dev/loop2 crw-rw----. 1 root disk 10, 237 Nov 27 07:51 /dev/loop-control

Now transfer or download the Datapower and LibgCrypt RPMs to this system using something line wget or WinSCP depending on access. You can find libgcrypt here (https://rpmfind.net)

Once transferred, you may have to decompress the installation files.

tar -xf idg_lx10540.cd.ASL.prod.tar

Now we can install the program

sudo yum install idg_lx.10540.image.x86_64.rpm idg_lx10540.common.x86_64.rpm

Once installed, you’ll connect to the system via telnet on the system’s loopback address

telnet 127.0.0.1 2200 Initial login is: admin Initial Password is: admin

Confirm to all prompts with Y and then run/create and confirm a new password

You must restart the DataPower Gateway to make the Common Criteria policies effective.

idg# configure terminal;web-mgmt;admin-state enabled;local-address 0 9090;exit Global mode Modify Web management service configuration

Now you can go to the web console via your computer and using the primary IP address. In our example
https://ip-address:9090

You’ll use the login password you created while connected via SSH. You’ll have to create yet another new password.

Once the password is updated, you’ll be able to login and complete the setup by accepting the license agreement.

After accepting the licensing agreement the system will need to reboot. After logging in via SSH you’ll need to restart the web interface.

telnet 127.0.0.1 2200 admin <password> idg<config> idg <config> configure terminal;web-mgmt;admin-state enabled;local-address 0 9090;exit

That's the complete installation process from start to finish. The last step would be to setup initialization of the datapower service upon restart. I'll be working on this sometime this week probably so that the environment is fault tolerant.

@dbeato said in Exchange Mailbox Database Migration - Single Host - Indexing Time estimate:

@dustinb3403 About 1 to 4 days.

That's what I was thinking, thanks!

@scottalanmiller You can also use a website for this. I have some private pages on my website where i list things I need to look up occasionally. They aren't secret details or anything but just key things I did for this software or how I helped this user. That kind of stuff.

@DustinB3403 said in Troubleshooting Help Requested:

@wrx7m said in Troubleshooting Help Requested:

VLANs?

No, and this VM is on the same vlan as other VMs on the same host.

PS I've restored this VM to a completely different hypervisor and the issue persists. So either its the VM or the gateway.

Have you tried a different IP, or even power down this machine and assign the same IP to another host to see if it gets blocked? Is the restored VM using the same MAC address as the original or has the restored version got a reinitialised MAC?

Do you have access to check the logs on the gateway / edge / router to see if it's blocking / intercepting / messing with your host

Just used this again today, as another script I have had this attribute.

Not sure when the attribute was written to the script though. But it's working now.

This is the full error.

/bin/sh: bad interpreter: Operation not permitted

That put 4.19.13 back and now it boots

[jbusch@naggaroth ~]$ sudo dnf upgrade --refresh [sudo] password for jbusch: Last metadata expiration check: 0:00:01 ago on Mon 07 Jan 2019 11:31:06 AM CST. Dependencies resolved. ================================================================================================================================== Package Arch Version Repository Size ================================================================================================================================== Installing dependencies: kernel x86_64 4.19.13-200.fc28 updates 102 k kernel-core x86_64 4.19.13-200.fc28 updates 24 M kernel-modules x86_64 4.19.13-200.fc28 updates 28 M Transaction Summary ================================================================================================================================== Install 3 Packages

c8f5c09a-b49c-480f-943f-1faf6c8aed5e-image.png

@LilAng doesn't really have a computer at home, either!

@black3dynamite That I haven't tried. It's worth a check!

@jaredbusch said in Pi-Hole web interface not working:

On the other system I created a blank external.conf and it works now.

sudo touch /etc/lighttpd/external.conf

Got it

@scottalanmiller said in Nextcloud Troubleshooting:

@mattbagan said in Nextcloud Troubleshooting:

@scottalanmiller I saw that too. I am wondering if I could just delete the folder in question and see if that helps.

Maybe, do a move, not a delete, in case you need to put it back.

Good idea! I moved the folder and it may have taken longer then normal, but it finally loaded again.

@dustinb3403 said in CentOS 7 enabling Telnet:

And I got the port forwarding to work.

firewall-cmd --zone=public --add-forward-port=port=9090:proto=tcp:toport=23

I can now telnet to my server on port 9090 (which forward to 23).

Nice!

Before you rip and replace the install... look at the current driver version so you can compare it to the new install.

What WPA2 security mode are you using? Make sure it is AES not TKIP.

Also a known-good USB wireless adapter is handy to keep around for times like this.

@dustinb3403 said in OpenProject Installation Troubleshooting.:

eh.

I agree, but I just want to see what it's all about, which docker will work fine for. Maybe I'll revisit once I have more time. Doubt I'll be much help even then though.

Having TaskScheduler in Windows run PowerShell scritps is like rolling dice depending on the context in which you are running the script...

So when in doubt:

I always have guaranteed success when starting the PS script from a batch file first from a scheduled task.

Create a scheduled tasked using these lines in an elevated powershell window:

Creates a scheduled task:

$action = New-ScheduledTaskAction -Execute 'C:\ProgramData\scripts\PSKickoff.bat' $trigger = New-ScheduledTaskTrigger -AtStartup $principal = New-ScheduledTaskPrincipal -GroupId "BUILTIN\Administrators" -RunLevel Highest $settings = New-ScheduledTaskSettingsSet $task = New-ScheduledTask -Action $action -Trigger $trigger -Principal $principal -Settings $settings Register-ScheduledTask -TaskName "Scheduled Task Friendly but Meaningful Name" -InputObject $task

Note: Change above New-ScheduledTaskTrigger -AtStartup to match your schedule. Here's the info for it.

The batch file that the scheduled task runs:

Powershell.exe -executionpolicy bypass -File "C:\ProgramData\scripts\yourScript.ps1"

@eddiejennings said in Traffic not flowing for hosts behind NAT - Edge Router Lite:

@dbeato said in Traffic not flowing for hosts behind NAT - Edge Router Lite:

@eddiejennings said in Traffic not flowing for hosts behind NAT - Edge Router Lite:

Take 3 is a partial success. All hosts except the IIS host has full Internet connectivity. The IIS host is accepting web and FTP traffic (so NAT's doing its job now :D); however, I can't ping outside my local network, and it can't resolve DNS.

So what is the DNS Server on that Server?

Same as all of the other servers that could resolve DNS. The issue was forgetting to reconfigure the source NAT rule.

Makes sense now!