You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jekyll: List all categories with according post count and show and link all post items listed in the according category
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Post-receive hook to deploy the code being pushed to production branch to a specific folder
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Mount VirtualBox shared folder on boot using fstab
How to mount a VirtualBox shared folder when the Guest OS boots
Problem
While using VirtualBox's Guest Additions to mount shared folders provides a seamless way to mount shared folders, there are also disadvantages.
Shared folders will always mount in /media/sf_(share name) unless specified using through vbox drivers in the guest OS
Mounting does not happen at boot-time. Applications that require paths at boot will not be able to access the shared folder even after it is mounted - such as Docker.
Solution
Instead of relying on Guest Additions, if you have sudo permissions, shared folders can be mounted at boot-time using fstab. Using this approach allows
Ubiquiti EdgeRouter firewall rules for IOT networks
Ubiquiti Edgerouter firewall rules for IOT networks
Just going to present several variations on a theme here, tested with a Ubiquiti EdgeRouter 4 in my home lab.
Several resources were consulted in the process of creating these firewall rules, cited below under "Resources".
In these examples, the "default" or "management" VLAN1 is VLAN1, on 192.168.1.0/24. A separate VLAN8 was created
for IOT devices on 192.168.8.0/24, along with its own DHCP service on the router.
The minimum requirements here are to have the IOT devices on VLAN8 network get an address from the VLAN8 DHCP server
and access the Internet through the VLAN's gateway (192.168.8.1), allow managment network access to the