My friend David asked me to help him tackle a problem with his network. He used a Unifi Security Gateway PRO 4 from Ubiquiti Networks but still wanted to run some Post IPTV STBs on his network. The solution took us some hours spread over several days, but finally the IPTV streams work fine.
We ended up using the LAN 2 interface as the IPTV upstream port, it turns out that the Unifi Cloud configuration doesn’t allow a static IP and a PPPoE session on the same interface. Also the built-in WAN-LAN firewall blocking firewall does need adding manual rules to allow the Multicast Traffic back in via the WAN interface. Using LAN2 allowed us to handle Multicast traffic as “Corporate LAN”-to-“Corporate LAN” traffic, which Unifi allows by default, so we can add firewall rules for LAN2 as required using the Unifi Cloud Network Controller instead of using custom JSON files on the Cloud Key. Continue Reading →
Getting to work an IPTV decoder on a POST Bamboo access with a Mikrotik router instead of Fritz!Box has been one of my long time challenges that I never got around. But finally I got it done, here is how to reproduce it.
I used ether1 port on the Mikrotik to connect to the GPON network termination unit (NTU). As POST uses VLAN 35 as the transport VLAN, i created a vlan interface on top of ether1.
The interface IPTV is a bridge as I distributed IPTV to a VLAN present on several interfaces.
Continue Reading →
I have used a Routerboard running Mikrotik’s RouterOS to connect to a POST LuxFibre FTTH access for some time. I have been asked in the past to aid with similar setups, so here comes my configuration for the RouterOS CLI.
Note: This setup does NOT (yet) provide access to the Voice service delivered by POST.
In this example I’m using “ether1” to connect to the GPON NTU. (I haven’t yet tested the RouterBoard GPON SFP module, so no need to ask about it 🙂 ) Continue Reading →
VoIP protocols have made the manipulation of the “CallerID” easier for the regular IPBX user or admin. So users started to question the industry to relax “CallerID screening” to display the original calling party number on call forwarding (done by the PBX), or the number of the company’s Headquarters and so on. While “CallerID screening” has been around for a very long time and has been a default feature in most cases, only a few customers were able to benefit from a more relaxed screening.
With the rise of ITSPs, marketing departments invented “CLIP No Screening”, a kind of “send any CallerID and we’ll accept it”. I suppose most of you understand the value of the average email with a faked sender address, well imagine what kind of phone calls you’d get once everyone would offer “CLIP No Screening” to anybody who asked for it. Continue Reading →
It was time again to re-install my Fritz!Box, unfortunately the box does crash sometimes and only a factory reset brings the broken services back to life (in between those crashes the box actually runs very solid).
So I setup all of my local services and DECT phones and concluded with the setup of my VoIP accounts. While testing ingress calls I noticed a nice HD icon on my DECT phones’ display. The Fritz!Box GUI surely lists my test calls with Codec G.722.
I have tested HD Voice with voipGATE.
POST Luxembourg had been operating a SixXS POP since March 2010. The POP worked fine for a time and some members of PRMG operated several tunnels. Unfortunately SixXs disabled the POP in 2015 after it had struggled with uptime issues for several weeks. A sad day for IPv6 in Luxembourg.
During Summer I started experimenting with different setups for a APRS Digi. In September I found very good hardware components from DC4ZZ & DB3FAT. I installed the system beginning of September on VHF and UHF using a temporary antenna and the callsign LX1DUC-4. On December 9, 2014 I received my license for the callsign LX0APD. The callsign LX0APD-4 is now on air as an APRS iGate and fill-in digipeater on VHF (144,800 MHz) and UHF (432,500 MHz) using a extremely low TX power of 16dbm.
A critical vulnerability was found in FreePBX and CVE 2014-7235 was released on September 30, 2014. An article on FreePBX.org explains all the details. If’ you’re running a FreePBX system be sure to read and act if you haven’t done so already.