Disabling firewalld
You can’t really run the old iptables utilities alongside firewalld. They’re just not compatible. The best way to get around this is to disable firewalld entirely (no need to uninstall it unless you want to) , and reinstall the iptables utilities. Disabling firewalld can be done using these commands:
Stop firewalld:
systemctl stop firewalld
Disable firewalld so it won’t start on boot: Continue reading “Enable IPTables on Rocky Linux 8” »
# Generated by iptables-save v1.3.5 on Tue Oct 28 23:57:58 2014 *filter :INPUT ACCEPT [2590:547311] :FORWARD ACCEPT [11426:731834] :OUTPUT ACCEPT [3989:328501] -A INPUT -i eth0 -j ACCEPT COMMIT # Completed on Tue Oct 28 23:57:58 2014 # Generated by iptables-save v1.3.5 on Tue Oct 28 23:57:58 2014 *mangle :PREROUTING ACCEPT [24964:3178001] :INPUT ACCEPT [9150:1450474] :FORWARD ACCEPT [11426:731834] :OUTPUT ACCEPT [4655:374193] :POSTROUTING ACCEPT [15415:1060335] COMMIT # Completed on Tue Oct 28 23:57:58 2014 # Generated by iptables-save v1.3.5 on Tue Oct 28 23:57:58 2014 *nat :PREROUTING ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :POSTROUTING ACCEPT [0:0] -A PREROUTING -m state -i eth0 --state RELATED,ESTABLISHED -j ACCEPT -A PREROUTING -p tcp -m tcp -d 123.45.67.89 --dport 80 -j DNAT --to-destination 172.16.5.113 -A POSTROUTING -j MASQUERADE COMMIT # Completed on Tue Oct 28 23:57:58 2014
Install Module
CentOS 7 comes with bridging module loaded on system boot by default. Use the following command to verify whether the module is loaded or not.
# modinfo bridge filename: /lib/modules/3.10.0-327.el7.x86_64/kernel/net/bridge/bridge.ko alias: rtnl-link-bridge version: 2.3 license: GPL rhelversion: 7.2 srcversion: 905847C53FF43DEFAA0EB3C depends: stp,llc intree: Y vermagic: 3.10.0-327.el7.x86_64 SMP mod_unload modversions signer: CentOS Linux kernel signing key sig_key: 79:AD:88:6A:11:3C:A0:22:35:26:33:6C:0F:82:5B:8A:94:29:6A:B3 sig_hashalgo: sha256
If the module is not loaded, you can load it using the following command. Continue reading “Create A Network Bridge on CentOS 7” »
I had a long old ubuntu 14 into my network, had an inevitable action to upgrade it to 16. Apply the simple 2 commands to make the updaration happening-
sudo do-release-upgrade
Use the below command for Ubuntu 14 machines:
sudo apt-get dist-upgrade
Citrix Xen uses a custom virtual appliance format for import/export called “XVA”. it’s basically a strangely crafted tar-file. You don’t need this program to unpack this tar-file, just use your favourite tar unpacker (tar, gtar, bsdtar). Once unpacked you will end up with a lot of different files, ova.xml (which contains the settings for the virtual appliance, think VMware vmx) and a number of folders called Ref:/, this is your disks. Each of these folders contain hundreds of files named 00000000, 00000001 with a accompanying .CHECKSUM file (SHA1). Each file is a 1MB slice of the disk, but some of the files in the sequence will probably be missing this is because XVA do not use compression; instead it will exclude slices of the disk that only contains zeros (are empty). This tool can assemble the disk for you (you will end up with a RAW disk) that can easily be mounted and modified. It can then also split the file again and generate checksum. Once ready, you will probably want to use the “package” command to rebuild the XVA file.
I’m running this conversion into a Debian 11 Server. First thing, you need to install xvz-img package from git repo into Debian server. Let’s install some essential package first- Continue reading “Convert Xen XVA to KVM” »
This worked for Debian 8 (Jessie)
replace original /etc/sources.list with:
deb http://archive.debian.org/debian/ jessie main non-free contrib deb-src http://archive.debian.org/debian/ jessie main non-free contrib deb http://archive.debian.org/debian-security/ jessie/updates main non-free contrib deb-src http://archive.debian.org/debian-security/ jessie/updates main non-free contribapt-update
It will give a keyring error. I tried both: Continue reading “Debian 8 (Jessie) repo updated-2023” »
Start a new SSH session to your XenServer host and run the commands below.
### Using curl ### [18:18 xcp-node-01 ~]# bash -c "$(curl -sS https://xoa.io/deploy)"
### Using wget ### [18:18 xcp-node-01 ~]# bash -c "$(wget -qO- https://xoa.io/deploy)"
If you are using an old XenServer version, you may encounter SSL connection issues. This can bypassed by using the unsecure connection instead: Continue reading “XOA on XCP-NG import and install” »
Step 1. First, you need to enable the EPEL repository on your system.
yum install epel-release yum -y update
Step 2. Installing Transmission on CentOS 7.
Just run the following command to install Transmission:
yum install transmission-cli transmission-common transmission-daemon
Once complete, you can verify Transmission is installed by running the below command:
systemctl start transmission-daemon.service systemctl stop transmission-daemon.service
Step 3. Configuration Transmission.
Edit the transmission settings.json config file: Continue reading “Install transmission on Centos 7” »
Install a standard Debian Bookworm, for details consider the Debian installation guide, and configure a static IP.
Note: The Debian installer performs network configuration by IPv6 autoconfiguration and DHCP by default, if available. To force manual network configuration in the UEFI installer, press E and add netcfg/disable_autoconfig=true to the linux command line. For the BIOS installer, select the Help entry and start the installation by typing installgui netcfg/disable_autoconfig=true. For further details, see the Debian installer documentation.
It is recommended to only install the “standard system utilities” and “SSH server” package selection, as Proxmox VE brings its own packages for QEMU and LXC. A desktop environment is not necessary.
Add an /etc/hosts entry for your IP address
The hostname of your machine must be resolvable via /etc/hosts. This means that in /etc/hosts you need one of the following entries for your hostname: Continue reading “Install Proxmox 7 on Debian 12” »
Please check if all the nodes are on the same package versions: run
pveversion -v
and compare the outputs.
If they’re not matching, you can run
apt update && apt dist-upgrade
To upgrade the nodes. if there’s a kernel upgrade you will also need to reboot the machines. If after the upgrades you still don’t see the same versions of the packages, then maybe you have wrong repositories set up [0]
