I recently received a letter from the company that monitors my home alarm. It basically stated that to avoid a $3US surcharge that I must opt out of receiving bill in the mail (which is fine) and that I must set up automatic transactions. I also found this form attached.
If you are using Outlook and Evernote on the Mac, check out the article below. It outlines an AppleScript that allows the user to press Command+E to add an email, or selected portion of an email to Evernote.
As I implemented this, I did run into a couple of caveats. My suggestion is to make sure to read the comments in the script and to relaunch Outlook between changes. Thanks to Justin Lancy for a great tip.
Although not immediately obvious, the FirePOWER Series 3 devices can do a form of IPS on a stick. This means that the capability described here should be available to the current appliance versions of the FirePOWER managed devices. The premise involves connecting broadcast domains (VLANs) to bring the managed device inline between the initiator and responder of a flow. Configuration is fairly straightforward but does have some caveats.
- Even though only a single port is required, a virtual switch must be configured (this cannot just be an inline pair)
- BPDUs being bridged between VLANs are detected and will render the switchport(s) in an inconsistent state
- The FirePOWER physical interface will not activate until it is also bound to a Virtual Switch
The diagram shows two devices in the same VLAN (we will assume /24 for the configuration). The device on the top is in VLAN 100. The FirePOWER managed device bridges VLAN 100 to VLAN 101 and allows the two devices to communicate directly with one another. The connection to the FirePOWER device is a single 802.1q trunk.
Frames arriving on VLAN 100 will be processed and egress with a VLAN tag of 101. This configuration is similar to a Router on a Stick but this example processes frames at layer 2. This methodology has been used to shoehorn an IPS between endpoints for quite a while.
R1 Configuration Continue reading
There are lots of differences in the way that individuals communicate and interact. One difference I often notice is whether a given individual does or does not respond. Using myself as an example, I will typically respond to a text message or email even if no question is posed. Often I will either Thank the sender or provide some unnecessary comment.
My wife on the other hand almost never responds to an information only message. If nothing is being requested, don’t expect a response. I find that lots of people exhibit this behavior and there’s nothing wrong with it. The lack of a response doesn’t necessarily mean the information isn’t appreciated. It is important to realize that just because you do something a certain way, don’t expect others to do the same.
I have a new podcast recommendation to share. The title is Citizens of Tech and is a product of our good friend Ethan Banks and Eric Suthphen. Although it is part of the PacketPushers ecosystem, it is a very different type of podcast. As opposed to typical network-centric topics, this show seems to include all things tech (and things that tech people are interested in).
Check out the first episode here–
I wanted to take a moment and give a well-deserved congratulations to the 2015 Cisco Learning Network Designated VIPs. These fine folks spend a ton of time giving back to the community by helping others in their learning process.
New VIPs for 2015
- Aref Alsouqi
- Darren Starr
- Joshua Johnson
- Milan Rai
Returning from Previous Year(s)
While working with firewalls for the last few years, I’ve seen many logs polluted with scanning traffic. Obviously this is the type of thing that I want to see when someone is legitimately scanning, or attempting to scan, through the firewall. However, there are a few cases that seeing this traffic is simply an indication of some other issue in the network.
An example I have seen on several occasions is someone configuring a network management station to discover 192.168.0.0/16, 172.16.0.0/12 or 10.0.0.0/8. If not properly handled in the routed network architecture, the associated traffic could make its way to the firewall or even to the ISP. An ASA might block the traffic due to policy, reroute it back toward the internal network, drop it due to the intra-interface hairpin configuration, or forward it onward. In most cases, this traffic will cause a lot of “noise” in the syslogs produced by the firewall.
To fully understand the problem, the diagram below can be used for discussion–
In this example, R1 has a static default route that points to the IP address of FW1. R1 advertises this via EIGRP to its internal neighbors. If a networked host attempts to reach a nonexistent subnet of 10.0.0.0/8, the traffic would follow the default route to FW1. This issue might also occur if something was communicating with a legitimate internal host and the destination network segment went down. One obvious example would be when a network management station is monitoring a portion of the network that goes offline. To get a baseline understanding, the output below shows the relevant configuration from R1. Continue reading
One of the the concepts that comes up occasionally is that of precedence. For example, one might consider the following routing table entries.
ip route 0.0.0.0 0.0.0.0 184.108.40.206 //default route
ip route 192.168.0.0 255.255.0.0 220.127.116.11 //supernet/cidr route
ip route 192.168.1.0 255.255.255.0 18.104.22.168 //network route
ip route 192.168.1.0 255.255.255.128 22.214.171.124 //subnet route
ip route 192.168.1.20 255.255.255.255 126.96.36.199 //host route
Questions often arise around which path a packet would take when it matches more than one entry. For example, a packet may have a destination address of 192.168.1.20. In this case it matches every single route entry. Continue reading
So I go to the IRS Page that allows taxpayers to check status of a refund. This is under the number “3” at the following URL–
The following banner pops up prior to setting a browser cookie.
I’m not a lawyer, so I have some questions regarding how to interpret this–
- Should this be read as–
- Use of this system constitutes consent to monitoring, interception, recording, reading, copying or capturing by authorized personnel of all activities. (or)
- Use of this system constitutes consent to monitoring, interception, recording, reading, copying or capturing by authorized personnel of all activities.
- And what does authorized personnel of all activities mean. If I use the system, I have to be authorized, or I’m breaking the law (as identified two sentences later–Unauthorized use is prohibited).
- So based on #2 above (authorized user). When I use that definition of authorized user in #1, the IRS isn’t accepting responsibility if I somehow happened to perform the following on another user’s information – monitoring, interception, recording, reading, copying or capturing. (doesn’t exclude my accountability, but it certainly alleviates the IRS accountability)
- “There is no right to privacy in this system“?
- So I’d hope the IRS can access my information, that is sort of the point of the system.
- But I also hope that data is private (meaning that the information isn’t publicly available), which is not what the banner states.
Posted in Rant, Technology
As a System Engineer, I do occasionally have to do real field work. When that happens, having access to a TFTP and FTP server is sometimes required. Although the [lack of] UI makes the use counterintuitive, these tools are available in OSX. This post includes the commands required to enable, confirm, and disable both TFTP and FTP in the native Mac environment.
//load the TFTP daemon (typically starts automatically)
sudo launchctl load -F /System/Library/LaunchDaemons/tftp.plist
//confirm that TFTP is listening (netstat)
netstat -atp UDP | grep tftp
udp6 0 0 *.tftp *.* //IPv6 Listening
udp4 0 0 *.tftp *.* //IPv4 Listening
//unload the TFTP daemon
sudo launchctl unload -F /System/Library/LaunchDaemons/tftp.plist
//confirm that TFTP is no longer listening (netstat)
netstat -atp UDP | grep tftp
- Default Directory is /private/tftpboot
- Copying a file from a device to the TFTP server requires it be “pre” created (Hint: sudo touch /private/tftpboot/<filename>)
- File permissions typically need to be modified (Hint: sudo chmod 766 /private/tftpboot/*)
- I just use my TFTP directory for transient file transfers
I just read a short post by Lindsay Hill titled Doing Community Programs Right. I think the points made are accurate and well-founded. Prior to working for Cisco, I was part of the “CLN Designated VIP Program”. I had the opportunity to connect with others in and around the industry. I think these online communities are great and there is a wealth of knowledge sharing that happens. During key conferences many of our paths cross and even more interesting conversations happen.
I’d personally like to bring some of those concepts into the local communities I work in. I think many of the same tenants would be important. I wouldn’t want a local group to be about any single vendor (even Cisco) or partner. It would be really interesting to just get a bunch of people together that wanted to share their technology challenges and how they are addressing them. Continue reading
Posted in Rant, Technology
I just wanted to take a moment and make a new podcast recommendation. This recommendation is the handiwork of several of our industry friends. The premise is around the unique use of technologies by small and medium business. This podcast should server as a good listen for everyone interested in SMB tech!