4.8 KiB
pct start 101
pct stop 101
pct destroy 101
pct console 101
pct reboot 101
Proxmox Container Creation
Use the following command to create a new container with reduced memory and storage:
pct create 101 /var/lib/vz/template/cache/openwrt-rootfs.tar.xz --unprivileged 1 --arch amd64 --ostype unmanaged --hostname openwrt-01 --tag network --storage local-lvm --memory 128 --swap 0 --rootfs local-lvm:1,size=512M \
--net0 name=eth0,bridge=vmbr0,firewall=1 \
--net1 name=eth1,bridge=vmbr1,firewall=1
OpenWRT Firewall Configuration
passwd
vi /etc/config/network
config interface 'wan'
option ifname 'wan'
option proto 'dhcp'
option device 'eth0'
config interface 'wan6'
option proto 'dhcpv6'
option device 'eth0'
config interface 'lan'
option ifname 'lan'
option proto 'static'
option device 'eth1'
option ipaddr '10.0.0.1'
option netmask '255.255.255.0'
vi /etc/config/firewall
config rule
option name 'Allow-SSH'
option src 'wan'
option proto 'tcp'
option dest_port '22'
option target 'ACCEPT'
config rule
option name 'Allow-HTTPS'
option src 'wan'
option proto 'tcp'
option dest_port '443'
option target 'ACCEPT'
config rule
option name 'Allow-HTTP'
option src 'wan'
option proto 'tcp'
option dest_port '80'
option target 'ACCEPT'
Applying the Configuration
After updating the configuration files:
-
Restart Network Services:
/etc/init.d/network restart -
Reload Firewall Settings:
/etc/init.d/firewall restart
Installing Packages via CLI
- Update the Package List: Before installing any new packages, it's a good practice to update the list of packages to ensure you are installing the latest versions available. You can do this by running:
opkg update
opkg install qemu-ga
poweroff
pct start 101
pct console 101
For your standalone Proxmox setup, switching between static and dynamic IP configurations and managing virtual bridges are important tasks. Below, I'll provide a concise guide to handle these changes effectively and safely.
Switching from Static IP to DHCP:
-
Update Network Interface Configuration:
- Open
/etc/network/interfacesin a text editor:nano /etc/network/interfaces - Change the
vmbr0configuration from static to DHCP:auto vmbr0 iface vmbr0 inet dhcp bridge-ports enp3s0 bridge-stp off bridge-fd 0 - Save the changes and exit the editor.
- Open
-
Restart Networking to Apply Changes:
- Apply the new network settings:
systemctl restart networking
- Apply the new network settings:
-
Find the New DHCP-Assigned IP Address:
- After the network restarts, check the assigned IP:
ip addr show vmbr0
- After the network restarts, check the assigned IP:
-
Update
/etc/hostswith the New IP:- Edit the
/etc/hostsfile to replace the old static IP with the new one:nano /etc/hosts - Modify the line with the old IP to the new one you just obtained:
192.168.86.62 whitebox.foxtrot.lan whitebox # Old IP 192.168.x.x whitebox.foxtrot.lan whitebox # New DHCP IP - Save and exit.
- Edit the
-
Reserve IP in DHCP Server (Optional but Recommended):
- To ensure the IP does not change on reboots, reserve the IP in your DHCP server settings to always assign the same IP to the MAC address of
vmbr0.
- To ensure the IP does not change on reboots, reserve the IP in your DHCP server settings to always assign the same IP to the MAC address of
Creating a New Virtual Bridge (vmbrX):
-
Add a New Virtual Bridge Configuration:
- Edit
/etc/network/interfaces:nano /etc/network/interfaces - Add a new bridge configuration at the end of the file:
auto vmbrX # Replace X with the next available number iface vmbrX inet manual bridge-ports none bridge-stp off bridge-fd 0 - Save and exit the editor.
- Edit
-
Activate the New Bridge:
- Restart the networking service to bring up the new bridge:
systemctl restart networking
- Restart the networking service to bring up the new bridge:
General Notes:
- Backup Configurations: Always backup configuration files before making changes (
cp /etc/network/interfaces /etc/network/interfaces.bak). - Documentation: Update all relevant documentation with the new bridge details and IP changes.
- Monitoring: Monitor the network and server behavior after changes to ensure everything is functioning as expected.
This approach provides a structured method to manage IP address configurations and virtual bridges on your Proxmox server, enhancing flexibility and ensuring consistent network settings across system reboots or changes.