Recent blog posts
This is a simple (or simplistic) Linux GTK+ application that shows a button panel or "switchboard". Each button executes a script.
This is probably not the "best practice" but it's what I'm doing lately to migrate files between servers, desktops, etc. MS has a tool that uses DFS to migrate data and maintain UNC paths, but, whenever I see systems that map paths to physical data on Windows, I worry.
The usg-50 has a pretty flexible system for saving configurations. From the Maintenance:File Manager:Configuration File screen, you manage your configuration files.
The V1910 switch requires that all configurations be saved, or they'll be lost after a power cycle. I'm sure all users learn this pretty quickly after spending time configuring a switch, and assuming that it was saved into the switch's nvram. They unplug the switch, move it, and then discover all their work is lost.
The 108T doesn't seem to have a regular upload and download screen. Instead, it can save the configuration to a TFTP server. Talk about weird.
I think Windows sucks, but one thing is for sure - the windows are there.
You need two computers. On each set up network connections in Network Manager with IP addresses in the 192.168.1.* range.
Different admins have different conventions. Here are a list of the ones I'm going to use:
This inexpensive SOHO/Small biz router has a simple and pretty feature-rich implementation of vlan routing.
I have been helping someone recover from some reckless Windows usage. You know the situation: lots of colorful apps that want you to pay for registration, and a bunch of random viruses.
It's only funny in a SMH way.
I've finally started to work on the network because, while things are heating up at work, I'm mostly on-call for the next week. I have some time on my hands to experiment.