IoT saves lives but infosec wants to change that
The cybersecurity industry mocks/criticizes IoT. That's because they are evil and wrong. IoT saves lives. This was demonstrated a couple weeks ago when a terrorist attempted to drive a truck through a Christmas market in German. The truck has an Internet-connected braking system. When it detected the collision, it deployed the brakes, bringing the truck to a stop. Injuries and deaths were a 10th of the similar Nice truck attack earlier in the year.All the trucks shipped by Scania in the last five years have had mobile phone connectivity to the Internet. Scania pulls back telemetry from trucks, for the purposes of improving drivers, but also to help improve the computerized features of the trucks. They put everything under the microscope, such as how to improve air conditioning to make the trucks more environmentally friendly.
Among their features is the "Autonomous Emergency Braking" system. This is the system that saved lives in Germany.
You can read up on these features on their website, or in their annual report [*].
My point is this: the cybersecurity industry is a bunch of police-state fetishists that want to stop innovation, to solve the "security" problem first before allowing innovation Continue reading
Huawei dips into Israel's tech community for a second time this month.
Docker and the container world are growing up fast.

Many networks leverage what is known as a VRF. These are used for traffic isolation and create separate routing instances within a router. It is important that vrf awareness is confirmed for any service (DHCP, Voice GW, etc) being locally provided for a given point in the network. One use case for such a configuration might be for voice isolation with or without MPLS. In the case that a router is providing voice gateway functionality (i.e. FXO/FXS to VOIP), the voice functions must understand the VRF construct in order to properly fulfill the role.
TL;DR–This configuration sometimes does not behave as expected and, in my experience, may require a reboot after following the documented procedure.
The configuration for VRF-Aware H.323 and SIP for Voice Gateways can be found at the URL below.
http://www.cisco.com/c/en/us/td/docs/ios/12_4t/12_4t15/stork.html
Notice that it makes reference to the fact that the services need to be restarted–
To configure a voice VRF, you must shut down voice services on the gateway, assign a previously defined VPN VRF to the VoIP SPI, and then restart voice services.
As one researches this particular configuration, the concept of voice “multi-vrf” will likely come up. Based on my Continue reading