Ok, one of our pfSense in Production just did it again, greet me with a friendly “Unable to check for updates”. My first suspect was DNS again, but after checking all resolvers can resolve the firmware.netgate.com domain without any issue. Next Step to try was in cli if the Package manager itself became a zombie or stuck somewhere. What is interesting is that it gave a response that was not expected. ...
Hey, just a heads-up that this content is based on an automatically imported version from our old CMS. If the formatting isn’t perfect, I’m sorry about that. If you look at the Windows command prompt from a network perspective, Linux has better “weapons” to offer. Often it’s the little things that frustrate me with Windows from time to time. For example, the DHCP client. In Linux it is sufficient to enter dhcpc -v to get a detailed logged output of what happened in the background with the DHCP. In Windows you can only rely on the presented Information, define some Log Actions or just wisely nod your head. ...
Hey, just a heads-up that this content is based on an automatically imported version from our old CMS. If the formatting isn’t perfect, I’m sorry about that. The Background Yesterday Netgate made a big leap into a new version branching for pfSense with pfSense plus. Instead of having 2.45, 2.5 versioning, there is now a partly proprietary pfSense+ build using Month/Year Versions for all Netgate-owned devices and optional bought subscriptions. The new Versions are YY.MM.VV, so 21.02 is the first one. ...
Hey, just a heads-up that this content is based on an automatically imported version from our old CMS. If the formatting isn’t perfect, I’m sorry about that. I cannot point out often enough how critical it is to keep your internet-based Servers updated. I use and manage some Servers, about 20 currently. But I hate to check them on a weekly base for Security Updates. I still remember days where Sysadmins brag with uptimes – not a smart thing to do. ...
Hey, just a heads-up that this content is based on an automatically imported version from our old CMS. If the formatting isn’t perfect, I’m sorry about that. Recently I moved from my old PI3B to an Intel NUC i3 as my “Home Server”. It has enough power to run all my local services and is still not wasteful in terms of power consumption and space requirement like a “real” Server, and it is fanless. ...
Hey, just a heads-up that this content is based on an automatically imported version from our old CMS. If the formatting isn’t perfect, I’m sorry about that. TL;DR HoneySIP is a SIP Honeypot Blacklist for use in Firewalls to Block SIP Crawlers and Bruteforcer. All IPs coming from own SIP Validating Honeypots at several servers. If you run a Server accessible over the Internet you will quickly find a lot of “interested” Eyes on it, especially if it is a VoIP System using SIP on default udp/5060. In an Ideal World this system would never be exposed to the Internet – but if you have a PBX which need to be accessible by a lot of remote workers and know how critical SIP/RTP can be you want to avoid forcing SIP over VPN. ...
Hey, just a heads-up that this content is based on an automatically imported version from our old CMS. If the formatting isn’t perfect, I’m sorry about that. Cause I’m not „blogging“ regularly on this page I just want to post more things in a “Today I learned” fashion. Specially if you work on/at Events and IT there are a lot of things which leave you puzzled questioning thing and forcing you to find solutions “RIGHT NOW”. While others in normal IT Ops have time to test things, Event-IT things are often MacGyver jobs. Working on a remote unknown site with other people’s IT Infrastructure and take what you get, at the end nobody cares – it need to work. ...
Hey, just a heads-up that this content is based on an automatically imported version from our old CMS. If the formatting isn’t perfect, I’m sorry about that. Whoever works with Linux servers on the web knows it, logs filled with attempted accesses, bruteforcers or simply spambots. Fortunately, there are some sites that have specialized in collecting these “bad IPs” via honeypots or logging reports. ...
Hey, just a heads-up that this content is based on an automatically imported version from our old CMS. If the formatting isn’t perfect, I’m sorry about that. Just as a note to myself or anybody who is interested in it, feel free to use. Often you come across hrefs linking to ssh://user@whatever:22. By default, Windows does not know what to do with this protocol. If you go to select the standard protocol handler for it, you only get redirected to the MS Store, offering you some expensive terminal apps you actually do not want to use. I, for myself, have been using the Pro version of MobaXterm for many years. MobaXterm has shell integration, but I never got it running right or being selectable as a protocol handler, unfortunately. But this is why I made this little method to actually make it working. ...
Hey, just a heads-up that this content is based on an automatically imported version from our old CMS. If the formatting isn’t perfect, I’m sorry about that. Just a tiny write up with some Link recommendations I want to put here. 1. privacytools.io This one is a great page containing a lot of useful Information and Links how to improve your everyday privacy on the way through the web. Not only for beginners also some good useful Information and recommendation for experts. The Page is setup by some reddit users in privacy chan and is updated frequently. ...