apt install tftpd-hpa #change TFTP_ADDRESS to by setting address to 192.168.1.1:69 or the IP you need, otherwise it will listen on all IPs and interfaces which could be a security risk. # edit /etc/default/tftpd-hpa TFTP_USERNAME="tftp" TFTP_DIRECTORY="/srv/tftp" TFTP_ADDRESS="192.168.1.1:69" TFTP_OPTIONS="--secure"........

This can break things easily in remove environments where it was normally easy to convert a normal eth0 to a bridge under br0, and that bridge would normally have the same MAC address by default, which is desirable for most situations. In Debian 11 this is different for some reason now. https://unix.stackexchange.com/questions/681013/bridge-gets-random-mac-........

Bonding is an excellent way to get both increased redundancy and throughput. It is similar to the "Network Teaming" feature in Windows. There are a few different modes but we will use mode 6, I think it's the best of both worlds, as it is not just a failover, but it provides round robin, so you will get redundancy and load balancing. So if you have a 1G single port, you will have a combined throughput of 4G at this point. Just bear in mind that the true thr........

Just a quick note and warning is that if you are testing to see if EFIPXE booting works on a VM, MAKE SURE it actually works. For example Iinitially tested using my Distro's QEMU 2.5+dfsg-5ubuntu10.46 and ovmf BIOS firmware (OVMF supports EFI). However, I found on old versions of QEMU (like 2.5), EFIbooting with GRUB NEVER works so it may appear that you have made a mistake when everything is fine when you boot a physi........

This often happens if you are adding a secondary route, especially with Linux source based routing. ip route add default via 10.10.10.254 table 10 RTNETLINK answers: Network is unreachable If that happens you will probably find that it is unreachable because your NIC does not have an IP in the 10.10.10.0/24 range so just assign an IP in that range to your NIC and try again. eg. ifconfig eth0 10.10.10.254 netmask 255.255.255.0 up........

Having a network bridge allows you to bridge traffic under multiple devices so they can talk natively without using any special routing, iptables/firewall or other trickery. To create your bridge you need the bridge-utils package for brctl and if you want to do things like bridge VMs that run on a tap device you will need the uml-utilities which provides "tunctl". 1.) Install the utilities to make our bridge sudo apt-get i........

[root@localhost:~] vmkping -I vmk1 10.0.2.69 PING 10.0.2.69 (10.0.2.69): 56 data bytes sendto() failed (Host is down) vsphere distributed switch vmotion not working [root@localhost:~] esxcfg-route -l VMkernel Routes: Network Netmask Gateway Interface&........

You can find many ways to specify the VLANin your network configuration but Ifind this is the simplest and quickest. In this case we are talking about a bridged adapter "vmbr0" but it works even if you just had a normal non-bridged interface. The key here is that in vmbr0 you'll notice there is no IP address. We just specify "manual". Below it is a similar stanza for "vmbr0.58" in this case 58 represents the VLAN (change........

It's really simple and just a matter of the following line within the subnet declaration. deny unknown-clients; See example below: subnet 10.25.20.0 netmask 255.255.255.0 { range 10.25.20.11 10.25.20.254; deny unknown-clients; option routers 10.25.20.10; option domain-name-servers 208.67.222.222;  ........

It's a basic script that reads the file "ips.txt" in the current directory and then creates a corresponding ifcfg file     #!/bin/bash GATEWAY=192.168.1.1 NETMASK=255.255.255.0 device=eth0 counter=0 for ips in `cat ips.txt`; do........

This is something I often setup for clients because it's very helpful for people in datacenters, this allows custom OS installs on demand, you can customize it more by using kickstart etc.. but here's a base I use before customizing more: This little script below will install everything you need to get booting by PXE Linux. It also assumes you set a local IP (be sure not to overwrite your existing IP) on eth0:0 (note the :0) as 192.168.1.10 and it........

route add -net 192.16.5.0 netmask 255.255.255.0 eth0 Of course adjust as you need (eg. the 192.16.5.0 should be changed to the subnet you need access to and eth0 should be changed to the network device that you want that subnet routed through). I also use the /etc/sysconfig/rc.local script and add the above into it (remember that this route only gets added AFTER all other init scripts have finished though).........

Basically the two main types of distros are Debian and RHEL/Centos based. I'm just going to give a quick overview of how the configuration of IP interfaces works in Debian/Centos based distros. *Just one thing to remember, when setting IPs statically you have to manually specify a DNS server in /etc/resolv.conf (since DHCP is what normally does it automatically) Debian/Ubuntu/Kubuntu/MEPIS The IP (DHCP &........

Setup Static IP Address ONBOOTAssuming you are using eth0 Note this will work for any version of CentOS and basically any version of Redhat Linux or Redhat based distribution. You would need to create a new file [code:1:02f8d34c30] /etc/sysconfig/network-scripts/ifcfg-eth0:0[/code:1:02f8d34c30] DEVICE=eth0:0 the ":0" at the end specifies alias 0 we could actually change this to ":99" or "........