Google Chromebook Pro’s & Con’s

Chromebooks have been around since 2011, odds are you may have used one or at least seen one in a local store. Chromebooks run Google’s Chrome Operating System and tied to the Google application ecosystem. Let’s take a look at some Pro’s and Con’s about using a Chromebook.

Pro: Linux-based operating system specifically designed by Google does not need anti-virus or is impervious to 99.999% of malware you will come across.

Con: Common PC-oriented applications cannot be used. Including Microsoft Office (desktop), Adobe Photoshop, Mozilla Firefox, etc. However many of these applications have analogous software or lightweight versions available via the Chrome Web Store.

Pro: Fast boot times and well known interfaces. If you’ve used the Google Chrome web browser or an Android-powered phone, you will feel right at home with a Chromebook.

Con: Limited hardware available. Many times the hardware specs of Chromebooks will be much lower that full-fledged laptops running Windows or Mac OS. However, Chrome OS and applications are so lightweight, that the hardware they ship with is more than capable.

Pro: Android Applications are coming to Chrome OS. Google is working on integrating Android apps that run on your phone or tablet to run inside of Chrome OS. Moving from one device to another will continue to become more and more seamless.

Con: People heavily integrated into the Apple ecosystem will find very few options on how to interact with their Apple-based applications and sign-in options.

Chromebooks can be very powerful devices when utilized correctly and for the majority of day-to-day uses they will fit every need you have. While they can’t fully replace your classic Windows or Apple laptop, they certainly can close the gap nicely. And their price point makes them a fantastic secondary device to keep near the couch, or a first laptop for a child.

Remote Help

Did you know that part of the End-User Technical Support services you already receive from us, includes our remote assistance feature for free?

We’ve always known that helping a user directly is the best way to correct an issue, so in 2010 we designed and deployed our remote assistance software. This secure and lightweight software is any easy to download and run for any user and allows us to view and manipulate the customer’s computer with them in real time.

The biggest surprise of using this tool was not the ease and speed of resolving a customer’s issue, but using it as a way to educate customers to features of their computer or websites one-on-one and at their own pace.

This tool has been invaluable in helping us reach our recent one million call milestone!

First Network Group, Inc. Proudly Completes One Million Support Calls

FOR IMMEDIATE RELEASE

First Network Group, Inc. Proudly Completes One Million Support Calls

Handling their first support call over 20 years ago, First Network Group, Inc. reaches another  major milestone by making their One Millionth support call!

Wapakoneta, OH (July 2017)

First Network Group, Inc. is proud to announce a major milestone in the history of the company– their one millionth call produced by their Technical Support and Customer Care Call Center.

Small businesses are judged by longevity and First Network Group has already proven their mettle in that area by surpassing 20 years in business in July 2016. However very few companies can claim the benchmark of one million support calls. If you think you’re on the phone a lot, making one million calls adds up to nearly 400 days of non-stop talk time!

The past one million calls have been made been made at First Network Group’s home office, in the small town of Wapakoneta, Ohio. Each one of these calls has focused on providing the special type of warmth and neighborly approach that can only be found in a small Midwestern town.

First Network Group has always maintained a customer first attitude, which explains why they’ve been so successful. “We’ve always said, we could support Internet, TV, telephone or whatever, but at the heart of it all was the desire to help make someone’s life easier and more enjoyable through the use of technology,” states Cory Lykins, Vice President of Tech Services.

Small town values, a customer-friendly and focused approach and dedication to bringing technology in reach of everyone– it’s clear to see why First Network Group has enjoyed so much  success through the years.

About First Network Group, Inc.

First Network Group Inc. is a specialist in building and maintaining Internet Service Provider Networks. Based in Ohio, it provides Server Administration, Network Engineering, and 24×7 emergency monitoring to reduce ISP/NSP downtime. FNGi developed and sells the DHCPatriot– a DHCP accounting and authentication server appliance. FNGi has a flexible and robust Call Center that provides multi-product End-user Technical Support Services and Customer Care options 24/7/365.

www.network1.net

Press and Media Inquiries
Cory Lykins
First Network Group, Inc.
P: +1-800-578-6381
E: info@network1.net

###

DHCPatriot 6.1.0 has entered beta testing!

We will be contacting certain DHCPatriot customers to inquire about helping us with beta testing. If anyone would like to help us beta test, please feel free to contact us and inquire about beta testing!

Email: DHCPatriot@network1.net
Phone: 800-578-6381 opt. 3

Here are the current patch notes for 6.1.0:

  1. Previously ‘Auth DHCP Config -> Exclude IP Address’ did not expose the ‘Limit Displayed Entries’ box. This made searching within the list impossible. This has been resolved. The box now appears and searching of this list is possible.
  2. Filesystem trim support is now triggered on boot in addition to once daily.
  3. Swappiness is now reduced to 5% on boot.
  4. Trim is now activated on the boot flash in model 2013-1 and newer DHCPatriot systems which contain such flash.
  5. Comma Separated Value (CSV) exporter will have commas stripped from the fields as this can obviously cause a problem for comma separated value files if there are rogue commas in the file.
  6. Performance module from the upper right has been hidden on virtual systems. This due to our inability to predict the hardware available in a virtual environment.
  7. Moderate performance bug in Usage Graphs data collection found and repaired.
  8. Disabled subnets ip counts now removed from total available IPs. Previously it made no impact on the counts of available addresses or the warnings about networks being full.
  9. Sessions will now move with a subnet if a subnet is moved to a different shared network or a different type of DHCP (such as auth -> standard). Some times in the past, a subnet would be moved. Sessions would continue. But they would disappear because they were still tied to the old shared network that wasn’t their home anymore. The sessions would show up in search sessions, but not in the counts on view address usage and the graphs. They still won’t immediately show up even now, but as they renew, the count will become correct.
  10. Preliminary support has been added for temperature monitoring. In a future release, the data will be added to SNMP output and server status web administration interface function.
  11. On certain systems, syslogd can have a tendency to not restart properly after log rotation. This seems to be limited to VMware systems. To counteract this, detection and starting of failed syslog has been implemented.
  12. A problem was fixed in the Built-in Authentication where a response couldn’t be obtained if the user was suspended. This could allow the user to stay online when they shouldn’t have been. This has been corrected.
  13. A new backend feature has been added such that authenticated devices are added and removed directly from the DHCP server. This means that a DHCP server restart is no longer required when user devices are authenticated or get suspended. This will result in greater DHCP server availability than is present prior to 6.1.0. Please note that this is a rather substantial change in operation of the DHCPatriot and as such there could be some unknown bugs present. If any are discovered, we will get a patch out as soon as possible.
  14. Standard DHCP Actions -> Known Client will now automatically translate any single quote ‘ to a back-tick ` to avoid problems with queries as the entries are used during DHCP actions.
  15. Standard DHCP Actions -> Static IP Assignment will now automatically translate any single quote ‘ to a back-tick ` to avoid problems with queries as the entries are used during DHCP actions.
  16. API: The API log messages have been enhanced. More descriptive log messages for API actions and failed logins / errors and the like are now available. These can be searched by going to System Configuration -> System Logs and selecting index for the Daemon and entering *API* in the Search Text box. In certain instances, this may impact returned error messages for the API. Please ensure that your API scripts still work after updating.
  17. API: The Known Client API calls previously did not properly restart the DHCP server when performing actions. This has been corrected.
  18. User Admin Restriction fix implemented. Previously, if you had an auth network selected but no standard, it showed you all standard networks. Also, if you had a standard network selected but no auth, it showed you all auth networks. This behavior has been corrected. Now, if you have at least one from one of the types selected but no other, all of the non-selected networks are hidden regardless of whether they are auth or standard. This makes this feature behave as was intended and per the descriptive text of the feature. Network restrictions are a convenience to hide networks which a particular administrator has no interest in (such as might be the case if multiple companies are sharing a DHCPatriot system). It is located and configured in System Configuration -> Administrators on the web administration interface.
  19. VRRP for IPv6 has been added. Set this up under System Configuration -> General Setup in box 14. The IPv6 addresses of the DHCPatriot devices as well as the VRRP address must all be in the same subnet.
  20. Corrected various spelling errors in response messages.
  21. API: The Deny MAC Address list can now be added to and removed from via a new API function. To Add:
    https://patriot.network1.net/cli/?username=apiuser&password=apipass&function=DenyMacAddress&action=ADD&mac=00:00:00:00:00:01&note=A%20TEST%20OF%20API%20DENY%20MAC%20ADD
    To Remove:
    https://patriot.network1.net/cli/?username=apiuser&password=apipass&function=DenyMacAddress&action=REMOVE&mac=00:00:00:00:00:01
  22. A new area has been added to configure permissions for the various functions available on the DHCPatriot system web administration interface. We called this Set App Permissions and it can be found under the System Configuration menu. This can be used to adjust the permission levels so that custom administrator levels can be created hiding / showing certain things to various administrator levels according to requirements.
  23. DHCPv6 Option 18 and Option 37 are now supported on the DHCPatriot system. They are only supported in the case that they are ASCII text strings (as was the case with option 82 support in DHCPv4). These options will be recorded with the DHCPv6 sessions.
  24. DHCPv6 sessions are now being recorded in the database.
  25. DHCPv6 sessions are now searchable in DHCPv6 (IPv6) -> Search Sessions. You can search by Client DUID, IP Address (which will also search delegated prefix), options 18 and 37, date/time and show only online devices. Additional parameters shown (Username and MAC Address) are not yet relevant and there for future development. The search results look similar to those available in DHCPv4.
  26. A new DHCPv4 setting has been exposed. The One Lease Per Client flag can now be toggled in System Configuration -> General Setup. This flag has always been there and is thus enabled by default. The DHCP server is instructed to allow only one IP Address per client. If a client requests a new lease, the previous lease is released. In 99% of situations this is the desired behavior. Recently, we have encountered a situation with a customer where multiple IP addresses per client is desired. Thus we have exposed this setting. If disabled, a client will be able to obtain and use multiple IP addresses simultaneously.
  27. Extra DHCP settings for DHCPv6 have been added to System Configuration -> General Setup. This works in a similar manner to the extra settings for DHCP except on DHCPv6 instead of DHCPv4.
  28. A problem was corrected where, under certain rare circumstances, stop time could be one second less than start time causing session time sent to the radius server to be -1 which resulted in session time appearing to be the largest possible positive unsigned 32 bit integer from the RADIUS server’s perspective. session time will now be adjusted to 0 in this case.
  29. View Address Usage now appears in DHCPv6 complete with the ability to click the subnet and see a list of users in the subnet. Graphs are not yet present and will appear in a future version.
  30. It is now possible to disable subnets in DHCPv6. This works much the same as it does in DHCPv4. The only difference being that Prefix delegations are dependent on a subnet, and so if a subnet is disabled, all of the prefix delegations dependent on that subnet will also show disabled in view address usage.
  31. Prefix Delegation has been split off from Dynamic Subnet allocations in DHCPv6. This allows multiple Prefix Delegation pools to be setup per subnet. Access Prefix Delegations in the DHCPv6 (IPv6) -> Prefix Delegation menu item. At time of install of 6.1.x, any prefix delegation pools that are setup with a subnet will be moved to this area.

Keeping Up with Updates

It is commonly understood that computer systems need to be kept up to date in order to keep them secure, and to fix bugs. End-user computers have updates that either automatically happen, or at least notify the user when they are ready to be installed. For servers, it is typical to have scheduled maintenance to install updates and reboot.

Unfortunately, network routers, firewalls, and switches are often not given the same care. There are several reasons that this may happen:

  1. The appropriate decision maker is not aware of the need
  2. There is a desire to not modify network devices that are deemed “working”
  3. There is a desire to not have any outages of network devices
  4. A support contract is often required to get the latest software.

For #1, it is simply a matter of education, which we hope this article serves to help.

For #2, it needs to be understood that by not keeping network systems up-to-date, you are potentially exposing your network to security issues, and denial-of-service attacks.

For #3, there are a variety of techniques to make your network redundant, so that outages caused by updates are minimal. These features also make your network more robust in general, protecting against device failure. First Network Group can help to design and deploy a network architecture that is less vulnerable to outages.

#4 should be considered as a required cost of doing business. Depending on the hardware vendor, the costs will vary. There are some vendors whose support contracts are significantly less costly than others. It is important to factor in the ongoing operational costs when deciding on the particular brand and model of gear for your needs.

The bottom line is that updates to all server, storage, and network devices are critical to keeping your network secure and available to serve your customers.

To discuss your options, contact Randy Carpenter, Vice President of IT Services: rcarpen@network1.net or 1-800-578-6381, option 2

FNGi Branded Optics

fng laser opticsFirst Network Group, Inc. now offers our own line of FNGi-branded optics. This includes the common SFP optical transceivers, as well as SFP+, XFP, CFP, and more. These are sourced from major manufacturers (the same ones that make the OEM-labeled products) and programmed and tested by one of the leading suppliers in the industry.

Custom programming allows these  modules to appear the same as OEM models to switches and routers. No more having to issue special commands to get non-original SFPs to function.

We can provide direct replacements for existing OEM models. In some cases, we can offer  similar models that exceed the distance specifications, or use different wavelengths. Examples include 100+km distance support, Bi-directional optics that use only 1 fiber, and DWDM models. Our optical transceivers have a lifetime warranty.

We also provide a full catalog of optical cabling, as well. A variety of lengths, fiber types, and connectors are available.

Contact Randy Carpenter for more details and for a custom quote.
rcarpen@network1.net or 1-800-578-6381, option 2

DHCPatriot 5.5.0 has entered beta.

We will be contacting specific system owners and asking them to join our beta test period. If You would like to be a beta tester, please contact us at dhcpatriot@network1.net or 800-578-6381 opt. 3

Here are the changes in 5.5.0:

  1. API: A new API feature allows the retrieval of the entire list of users from Built-in Authentication: User Maintenance (or some sub-set thereof) from the DHCPatriot. The results can be limited by Identifier, username, static IP, simuse and status. Here is an example URL of the API call:
    https://patriot.network1.net/cli/BuiltInAuthAPI.php? function=BASearchCustomers&username=apiuser&password=apipass&identifier=Jim%20Smith&user=jsmith&staticip=1.3.5.7&simu se=3&status=Active
  2. API: A new API feature,GetNetworkConfig, provides all of the DHCP subnets in one xml return. Here is an example URL of the API call:
    https://patriot.network1.net/cli/?function=GetNetworkConfig&username=apiuser&password=apipass
  3. API: Added a new set of API calls that provide the ability to add, edit, delete and list the known client entries. This is basically an API interface that lets you perform all of the known client (Standard DHCP Actions -> Known Client) operations. See below for example API calls:
    Add: https://patriot.network1.net/cli/? function=KnownClient&username=apiuser&password=apipass&ACTION=ADD&mac=01:03:05:11:10:09&IDENT=Jose%20Aldo&TFT Pfile=some.file
    Edit: https://patriot.network1.net/cli/? function=KnownClient&username=apiuser&password=apipass&ACTION=EDIT&mac=01:03:05:11:10:45&IDENT=John%20Doe&TFT Pfile=some.other.file&id=5
    Delete: https://patriot.network1.net/cli/? function=KnownClient&username=apiuser&password=apipass&ACTION=DELETE&id=5
    List: https://patriot.network1.net/cli/? function=KnownClient&username=apiuser&password=apipass&ACTION=LIST

Continue reading

A Basic Evolution of the Virus

In the early days of networking computers, viruses were little more than proof of concept bits of code. Can I write a program or exploit a function where I can remotely open a CD drive on another computer or cause some other strange behavior?

These prank style antics grew bigger in scope and power and quickly began to spread around the Internet. Then the environment took a more sinister turn, by bulking up the things these viruses could do. Viruses became punishing programs that would eat up CPU speed, bloat up free hard drive space, spin drives faster than they were designed for and even delete user or operating system data.

They were deployed by people to punish others and destroy property and data. Without tangible rewards creating viruses start to get a bit bland. Viruses then started evolving to an end game or reward. Viruses that previously may have taken a computer offline either by design or by unmitigated spread of the infection fell out of favor. It was becoming more and more important to not have the target go offline or notice the infection. If the target went offline, the attacker wasn’t able to reap the benefits of the infection.

And what were those benefits? In that generation, most of the time it was stealing address book entries to sell to spammers. Personal information was rarely targeted, but corporate data was ripe for the picking.

This is the era of BotNet. Many viruses infect, spread and lay totally dormant. These infected computers are now slaves to the whims of the attacker. If an attacker wants to take down a large site with a DDOS attack, they can wake up 1,000’s of these sleeping infections to begin slamming a site with traffic. Each computer sending out just enough traffic not to be noticed but when combined as a whole their effects can be devastating. These “Bots” can also be put to task to sneak out little bits of Spam here and there. Not enough to get flagged by the normal detection practices of a modern ISP, but combined with the sheer numbers of those infected can wreak a lot of junk mail havoc.

The virus/malware industry has gone thru a major transformation over the years. Viruses have evolved from simple pranks to a hacker’s tool with which to make money, create mass damage or capture information. Viruses don’t say “Happy 1999!” on your screen anymore and stop there. These new viruses like to hide, wait and use the power of their combined infection numbers to make the criminals involved a lot of money.

DHCPatriot 5.4.0 has been released

  1. When unsuspending a user device in Auth DHCP Actions -> Suspend User, the limit displayed entries was not saved during the unsuspend process. This has been corrected and list limits are now remembered as user devices are unsuspended.
  2. IPv6 logins to the web administration interface were impossible. This was traced to storage of the remote IP address being to small. The size has been increased so that it can store IPv6 addresses. The DHCPatriot system can now be administered from an IPv6 address.
  3. Discovered that there was a problem where sometimes cron would no longer rotate logs or database files until it was restarted. Cron now restarts once per day to avoid this situation.
  4. Both IPv4 and IPv6 versions of Firewall setup under System Configuration now support assigning several services to an IP address simultaneously. Previously you had to repeat the process several times to open the firewall for more than one service to a specific IP or subnet.
  5. IPv6 Ping and Trace route are now supported in the web administration interface as well as the CLI admin menu. Options 12 and 13 are ping6 and trace6 respectively. Reboot and shutdown have moved to options 14 and 15 respectively
  6. API: Unsuspending via the API can now perform a RADIUS authentication check as the web administration interface does if the parameter AuthTest=true is passed to the API. Example: https://patriot.network1.net/cli/? function=SuspendEnable&username=apiuser&password=apipass&action=unsuspend&us er=bobaaron&AuthTest=true
  7. API: StickyIP ADD: It is now possible to add a sticky IP via the API by using a URL of the following format: https://patriot.network1.net/cli/? username=&password=&function=StickyIPs&action=ADD&Stickymac=&Stickyuserna me=&Stickyip=&Stickynote=

Continue reading