#Remember that you need a valid gateway IPunless the Asterisk server is on the same subnet and LAN Set Valid Gateway IP (if you don't have one already) ip route 0.0.0.0 0.0.0.0 GATEWAYIP Enable VOIPTrust voice service voip ip address trusted list ipv4 0.0.0.0 0.0.0.0 sip Set Credentials For Asterisk and Register To Asterisk sip-ua........

In newer versions this is a very stubborn issue. Here is how you fix it. Step 1 - Create networks.conf sudo mkdir /etc/vbox/ sudo vi /etc/vbox/networks.conf put this in: In our case we can use the slash /16 range of 192.168.0..0, change the subnet accor........

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"........

Why choose OpenVPN instead of a firewall appliance? OpenVPN can be a reliable and easy replacement for traditional hardware or just be an additional tool that your company uses so that the firewall can focus on its job rather than acting as a VPNappliance at the same time. When comparing OpenVPN with traditional firewal........

This seems to be an ongoing issue that is still reproducable in the latest Ubuntu Vbox 6.x. The default NAT Network range is usually 10.0.2.0/24. If you change this range it does not seem to work properly. Say we change the range to 10.50.1.0/24 If you get a new lease you will find that you get an IP from the old range but the default gateway is from the new range. ........

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........

Many people may not be aware that you can turn commodity hardware into a Mikrotik OS and there are various options which is "CHR" (Cloud Hosted Router) which is a VMimage meant for Virtualization only (seriously, I've tried to dd the image to a physical server and it just crashed as it does not contain any drivers for physical). One note as well if you are trying to do a baremetal install you may get an error "Error Loading Operating System" or........

This is only really necessary in the case you don't want DHCP. If you are dealing with an encrypted LUKS server on the internet, you will often want to have a static IP so you know which IP to connect to (or if you have a semi-static IP assigned by DHCP). SET IP Address by /etc/initramfs-tools/initramfs.conf IP Address=192.168.1.27 Gateway=192.168.1.1 Subnet Mask: 255.255.255.0 Hostname=myhome.com IP=192.1........

A lot of people think arp wil do it but the arp table will only show devices you have communicated with. Using nmap is a quick and simple way to scan a range to find a machine you may not know the IP for: eg: nmap -sP 10.1.5.0/24 Just change the above to your subnet........

[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&........

#mount the VCSA DVD mount /dev/sr0 /mnt/cd #alternatively you could mount the iso directly mount -o loop vcsa.iso /your/mount/path #for this purpose we are using the CLI installer on Linux cd /mnt/cd/vcsa-cli-installer/lin64 #no it's not going to be that easy you can't just run vcsa-deploy like that you need to use a template or configured .json file ./vcsa-deploy Usage: vcsa-deploy [-h] [--version] [--supported-deploymen........

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;  ........

This is a real pain because I had to manually unplug ethernet cables for network testing or to use an alternate network or guarantee physical access to one network segment is cut off. For some reason this happened after Ikilled dbus because it was confused and blocking packets thinking they were coming from the wrong interface since eth0 and eth1 both had the same subnet and gateway. I eventually did a "service network-manager restart" but the option was........

This is actually very simple and this example assumes your network device is "eth0" In Centos your network config would be the following: /etc/sysconfig/network-scripts/ifcfg-eth0 Take the same path and just add a "-range0" So to add a range create the following file: /etc/sysconfig/network-scripts/ifcfg-eth0-range0 IPADDR_START=192.168.1.50 IPADD........

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........

I used the suggested script to bridge from OpenVPN and it took my client's server off-line! Don't ever use their "sample" scripts if you don't have another way of accessing the server than SSH. I actually found it easier to use iptables to tell it to route IPs based on a certain subnet to route through eth0: iptables -t nat -A POSTROUTING -s 192.168.200.0/24 -o eth0 -j MASQUERADE Replace "192.168.200.0/24" with your subnet of cour........

This may not apply to everyone but here is what happened to me. One day my IP connectivity for one container went dead, I could ping the hostnode from it and the hostnode could ping it but there was no external routing. I restarted the network service but it didn't help. I checked the routing table inside the VPS and the host and everything looked normal. Iadded another different IPon the same subnet to the container and it worked. Right away I st........

Subnet Mask Lengths / Quick Reference This is for when you say how many IPs would be in a /20 or /24 Now instead of doing math just remember this table or visit here more often :) /32 1 IP Address(es) /31 2 IP Address(es)........

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).........