ASUS Home Router Bugs Open Consumers to Snooping Attacks

The two flaws allow man-in-the-middle attacks that would give an attacker access to all data flowing through the router.

A pair of flaws in ASUS routers for the home could allow an attacker to compromise the devices – and eavesdrop on all of the traffic and data that flows through them.

The bugs are specifically found in the RT-AC1900P whole-home Wi-Fi model, within the router’s firmware update functionality. Originally uncovered by Trustwave, ASUS has issued patches for the bugs, and owners are urged to apply the updates as soon as they can.

The first issue (CVE-2020-15498) stems from a lack of certificate checking.

The router uses GNU Wget to fetch firmware updates from ASUS servers. It’s possible to log in via SSH and use the Linux/Unix “grep” command to search through the filesystem for a specific string that indicates that the vulnerability is present: “–no-check-certificate.”

In vulnerable versions of the router, the files containing that string are shell scripts that perform downloads from the ASUS update servers, according to Trustwave’s advisory, issued on Thursday. This string indicates that there’s no certificate checking, so an attacker could use untrusted (forged) certificates to force the install of malicious files on the targeted device.

An attacker would need to be connected to the vulnerable router to perform a man in the middle attack (MITM), which would allow that person complete access to all traffic going through the device.

The latest firmware eliminates the bug by not using the Wget option anymore.

The second bug (CVE-2020-15499) is a cross-site scripting (XSS) vulnerability in the Web Management interface related to firmware updates, according to Trustwave.

“The release notes page did not properly escape the contents of the page before rendering it to the user,” explained the firm. “This means that a legitimate administrator could be attacked by a malicious party using the first MITM finding and chaining it with arbitrary JavaScript code execution.”

ASUS fixed this in the latest firmware so that the release notes page no longer renders arbitrary contents verbatim.

“Since routers like this one typically define the full perimeter of a network, attacks targeting them can potentially affect all traffic in and out of your network,” warned Trustwave.

ASUS patched the issues in firmware version 3.0.0.4.385_20253.

The bug disclosure comes less than two weeks after a bombshell security review of 127 popular home routers found most contained at least one critical security flaw, according to researchers. Not only did all of the routers the researchers examined have flaws, many “are affected by hundreds of known vulnerabilities,” the researchers said.

On average, the routers analyzed–—by vendors such as D-Link, Netgear, ASUS, Linksys, TP-Link and Zyxel—were affected by 53 critical-rated vulnerabilities (CVE), with even the most “secure” device of the bunch having 21 CVEs, according to the report. Researchers did not list the specific vulnerabilities.

#iot #vulnerabilities #web security #asus #bug #cve-2020-15498 #cve-2020-15499 #firmware update #home router #man in the middle #mitm #patch #rt-ac1900p #security vulnerability #total compromise #trustwave

What is GEEK

Buddha Community

ASUS Home Router Bugs Open Consumers to Snooping Attacks

The two flaws allow man-in-the-middle attacks that would give an attacker access to all data flowing through the router.

A pair of flaws in ASUS routers for the home could allow an attacker to compromise the devices – and eavesdrop on all of the traffic and data that flows through them.

The bugs are specifically found in the RT-AC1900P whole-home Wi-Fi model, within the router’s firmware update functionality. Originally uncovered by Trustwave, ASUS has issued patches for the bugs, and owners are urged to apply the updates as soon as they can.

The first issue (CVE-2020-15498) stems from a lack of certificate checking.

The router uses GNU Wget to fetch firmware updates from ASUS servers. It’s possible to log in via SSH and use the Linux/Unix “grep” command to search through the filesystem for a specific string that indicates that the vulnerability is present: “–no-check-certificate.”

In vulnerable versions of the router, the files containing that string are shell scripts that perform downloads from the ASUS update servers, according to Trustwave’s advisory, issued on Thursday. This string indicates that there’s no certificate checking, so an attacker could use untrusted (forged) certificates to force the install of malicious files on the targeted device.

An attacker would need to be connected to the vulnerable router to perform a man in the middle attack (MITM), which would allow that person complete access to all traffic going through the device.

The latest firmware eliminates the bug by not using the Wget option anymore.

The second bug (CVE-2020-15499) is a cross-site scripting (XSS) vulnerability in the Web Management interface related to firmware updates, according to Trustwave.

“The release notes page did not properly escape the contents of the page before rendering it to the user,” explained the firm. “This means that a legitimate administrator could be attacked by a malicious party using the first MITM finding and chaining it with arbitrary JavaScript code execution.”

ASUS fixed this in the latest firmware so that the release notes page no longer renders arbitrary contents verbatim.

“Since routers like this one typically define the full perimeter of a network, attacks targeting them can potentially affect all traffic in and out of your network,” warned Trustwave.

ASUS patched the issues in firmware version 3.0.0.4.385_20253.

The bug disclosure comes less than two weeks after a bombshell security review of 127 popular home routers found most contained at least one critical security flaw, according to researchers. Not only did all of the routers the researchers examined have flaws, many “are affected by hundreds of known vulnerabilities,” the researchers said.

On average, the routers analyzed–—by vendors such as D-Link, Netgear, ASUS, Linksys, TP-Link and Zyxel—were affected by 53 critical-rated vulnerabilities (CVE), with even the most “secure” device of the bunch having 21 CVEs, according to the report. Researchers did not list the specific vulnerabilities.

#iot #vulnerabilities #web security #asus #bug #cve-2020-15498 #cve-2020-15499 #firmware update #home router #man in the middle #mitm #patch #rt-ac1900p #security vulnerability #total compromise #trustwave

Phobos: Simplifying Kafka for Ruby Apps

Phobos

Simplifying Kafka for Ruby apps!

Phobos is a micro framework and library for applications dealing with Apache Kafka.

• It wraps common behaviors needed by consumers and producers in an easy and convenient API
• It uses ruby-kafka as its Kafka client and core component
• It provides a CLI for starting and stopping a standalone application ready to be used for production purposes

Why Phobos? Why not ruby-kafka directly? Well, ruby-kafka is just a client. You still need to write a lot of code to manage proper consuming and producing of messages. You need to do proper message routing, error handling, retrying, backing off and maybe logging/instrumenting the message management process. You also need to worry about setting up a platform independent test environment that works on CI as well as any local machine, and even on your deployment pipeline. Finally, you also need to consider how to deploy your app and how to start it.

With Phobos by your side, all this becomes smooth sailing.

Installation

Add this line to your application's Gemfile:

gem 'phobos'

And then execute:

$ bundle

Or install it yourself as:

$ gem install phobos

Usage

Phobos can be used in two ways: as a standalone application or to support Kafka features in your existing project - including Rails apps. It provides a CLI tool to run it.

Standalone apps

Standalone apps have benefits such as individual deploys and smaller code bases. If consuming from Kafka is your version of microservices, Phobos can be of great help.

Setup

To create an application with Phobos you need two things:

• A configuration file (more details in the Configuration file section)
• A phobos_boot.rb (or the name of your choice) to properly load your code into Phobos executor

Use the Phobos CLI command init to bootstrap your application. Example:

# call this command inside your app folder
$ phobos init
    create  config/phobos.yml
    create  phobos_boot.rb

phobos.yml is the configuration file and phobos_boot.rb is the place to load your code.

Consumers (listeners and handlers)

In Phobos apps listeners are configured against Kafka - they are our consumers. A listener requires a handler (a ruby class where you should process incoming messages), a Kafka topic, and a Kafka group_id. Consumer groups are used to coordinate the listeners across machines. We write the handlers and Phobos makes sure to run them for us. An example of a handler is:

class MyHandler
  include Phobos::Handler

  def consume(payload, metadata)
    # payload  - This is the content of your Kafka message, Phobos does not attempt to
    #            parse this content, it is delivered raw to you
    # metadata - A hash with useful information about this event, it contains: The event key,
    #            partition number, offset, retry_count, topic, group_id, and listener_id
  end
end

Writing a handler is all you need to allow Phobos to work - it will take care of execution, retries and concurrency.

To start Phobos the start command is used, example:

$ phobos start
[2016-08-13T17:29:59:218+0200Z] INFO  -- Phobos : <Hash> {:message=>"Phobos configured", :env=>"development"}
______ _           _
| ___ \ |         | |
| |_/ / |__   ___ | |__   ___  ___
|  __/| '_ \ / _ \| '_ \ / _ \/ __|
| |   | | | | (_) | |_) | (_) \__ \
\_|   |_| |_|\___/|_.__/ \___/|___/

phobos_boot.rb - find this file at ~/Projects/example/phobos_boot.rb

[2016-08-13T17:29:59:272+0200Z] INFO  -- Phobos : <Hash> {:message=>"Listener started", :listener_id=>"6d5d2c", :group_id=>"test-1", :topic=>"test"}

By default, the start command will look for the configuration file at config/phobos.yml and it will load the file phobos_boot.rb if it exists. In the example above all example files generated by the init command are used as is. It is possible to change both files, use -c for the configuration file and -b for the boot file. Example:

$ phobos start -c /var/configs/my.yml -b /opt/apps/boot.rb

You may also choose to configure phobos with a hash from within your boot file. In this case, disable loading the config file with the --skip-config option:

$ phobos start -b /opt/apps/boot.rb --skip-config

Consuming messages from Kafka

Messages from Kafka are consumed using handlers. You can use Phobos executors or include it in your own project as a library, but handlers will always be used. To create a handler class, simply include the module Phobos::Handler. This module allows Phobos to manage the life cycle of your handler.

A handler is required to implement the method #consume(payload, metadata).

Instances of your handler will be created for every message, so keep a constructor without arguments. If consume raises an exception, Phobos will retry the message indefinitely, applying the back off configuration presented in the configuration file. The metadata hash will contain a key called retry_count with the current number of retries for this message. To skip a message, simply return from #consume.

The metadata hash will also contain a key called headers with the headers of the consumed message.

When the listener starts, the class method .start will be called with the kafka_client used by the listener. Use this hook as a chance to setup necessary code for your handler. The class method .stop will be called during listener shutdown.

class MyHandler
  include Phobos::Handler

  def self.start(kafka_client)
    # setup handler
  end

  def self.stop
    # teardown
  end

  def consume(payload, metadata)
    # consume or skip message
  end
end

It is also possible to control the execution of #consume with the method #around_consume(payload, metadata). This method receives the payload and metadata, and then invokes #consume method by means of a block; example:

class MyHandler
  include Phobos::Handler

  def around_consume(payload, metadata)
    Phobos.logger.info "consuming..."
    output = yield payload, metadata
    Phobos.logger.info "done, output: #{output}"
  end

  def consume(payload, metadata)
    # consume or skip message
  end
end

Note: around_consume was previously defined as a class method. The current code supports both implementations, giving precendence to the class method, but future versions will no longer support .around_consume.

class MyHandler
  include Phobos::Handler

  def self.around_consume(payload, metadata)
    Phobos.logger.info "consuming..."
    output = yield payload, metadata
    Phobos.logger.info "done, output: #{output}"
  end

  def consume(payload, metadata)
    # consume or skip message
  end
end

Take a look at the examples folder for some ideas.

The hander life cycle can be illustrated as:

.start -> #consume -> .stop

or optionally,

.start -> #around_consume [ #consume ] -> .stop

Batch Consumption

In addition to the regular handler, Phobos provides a BatchHandler. The basic ideas are identical, except that instead of being passed a single message at a time, the BatchHandler is passed a batch of messages. All methods follow the same pattern as the regular handler except that they each end in _batch and are passed an array of Phobos::BatchMessages instead of a single payload.

To enable handling of batches on the consumer side, you must specify a delivery method of inline_batch in phobos.yml, and your handler must include BatchHandler. Using a delivery method of batch assumes that you are still processing the messages one at a time and should use Handler.

When using inline_batch, each instance of Phobos::BatchMessage will contain an instance method headers with the headers for that message.

class MyBatchHandler
  include Phobos::BatchHandler

  def around_consume_batch(payloads, metadata)
    payloads.each do |p|
      p.payload[:timestamp] = Time.zone.now
    end

    yield payloads, metadata
  end

  def consume_batch(payloads, metadata)
    payloads.each do |p|
      logger.info("Got payload #{p.payload}, #{p.partition}, #{p.offset}, #{p.key}, #{p.payload[:timestamp]}")
    end
  end

end

Note that retry logic will happen on the batch level in this case. If you are processing messages individually and an error happens in the middle, Phobos's retry logic will retry the entire batch. If this is not the behavior you want, consider using batch instead of inline_batch.

Producing messages to Kafka

ruby-kafka provides several options for publishing messages, Phobos offers them through the module Phobos::Producer. It is possible to turn any ruby class into a producer (including your handlers), just include the producer module, example:

class MyProducer
  include Phobos::Producer
end

Phobos is designed for multi threading, thus the producer is always bound to the current thread. It is possible to publish messages from objects and classes, pick the option that suits your code better. The producer module doesn't pollute your classes with a thousand methods, it includes a single method the class and in the instance level: producer.

my = MyProducer.new
my.producer.publish(topic: 'topic', payload: 'message-payload', key: 'partition and message key')

# The code above has the same effect of this code:
MyProducer.producer.publish(topic: 'topic', payload: 'message-payload', key: 'partition and message key')

The signature for the publish method is as follows:

def publish(topic: topic, payload: payload, key: nil, partition_key: nil, headers: nil)

When publishing a message with headers, the headers argument must be a hash:

my = MyProducer.new
my.producer.publish(topic: 'topic', payload: 'message-payload', key: 'partition and message key', headers: { header_1: 'value 1' })

It is also possible to publish several messages at once:

MyProducer
  .producer
  .publish_list([
    { topic: 'A', payload: 'message-1', key: '1' },
    { topic: 'B', payload: 'message-2', key: '2' },
    { topic: 'B', payload: 'message-3', key: '3', headers: { header_1: 'value 1', header_2: 'value 2' } }
  ])

There are two flavors of producers: regular producers and async producers.

Regular producers will deliver the messages synchronously and disconnect, it doesn't matter if you use publish or publish_list; by default, after the messages get delivered the producer will disconnect.

Async producers will accept your messages without blocking, use the methods async_publish and async_publish_list to use async producers.

An example of using handlers to publish messages:

class MyHandler
  include Phobos::Handler
  include Phobos::Producer

  PUBLISH_TO = 'topic2'

  def consume(payload, metadata)
    producer.async_publish(topic: PUBLISH_TO, payload: {key: 'value'}.to_json)
  end
end

Note about configuring producers

Since the handler life cycle is managed by the Listener, it will make sure the producer is properly closed before it stops. When calling the producer outside a handler remember, you need to shutdown them manually before you close the application. Use the class method async_producer_shutdown to safely shutdown the producer.

Without configuring the Kafka client, the producers will create a new one when needed (once per thread). To disconnect from kafka call kafka_client.close.

# This method will block until everything is safely closed
MyProducer
  .producer
  .async_producer_shutdown

MyProducer
  .producer
  .kafka_client
  .close

Note about producers with persistent connections

By default, regular producers will automatically disconnect after every publish call. You can change this behavior (which reduces connection overhead, TLS etc - which increases speed significantly) by setting the persistent_connections config in phobos.yml. When set, regular producers behave identically to async producers and will also need to be shutdown manually using the sync_producer_shutdown method.

Since regular producers with persistent connections have open connections, you need to manually disconnect from Kafka when ending your producers' life cycle:

MyProducer
  .producer
  .sync_producer_shutdown

Phobos as a library in an existing project

When running as a standalone service, Phobos sets up a Listener and Executor for you. When you use Phobos as a library in your own project, you need to set these components up yourself.

First, call the method configure with the path of your configuration file or with configuration settings hash.

Phobos.configure('config/phobos.yml')

or

Phobos.configure(kafka: { client_id: 'phobos' }, logger: { file: 'log/phobos.log' })

Listener connects to Kafka and acts as your consumer. To create a listener you need a handler class, a topic, and a group id.

listener = Phobos::Listener.new(
  handler: Phobos::EchoHandler,
  group_id: 'group1',
  topic: 'test'
)

# start method blocks
Thread.new { listener.start }

listener.id # 6d5d2c (all listeners have an id)
listener.stop # stop doesn't block

This is all you need to consume from Kafka with back off retries.

An executor is the supervisor of all listeners. It loads all listeners configured in phobos.yml. The executor keeps the listeners running and restarts them when needed.

executor = Phobos::Executor.new

# start doesn't block
executor.start

# stop will block until all listers are properly stopped
executor.stop

When using Phobos executors you don't care about how listeners are created, just provide the configuration under the listeners section in the configuration file and you are good to go.

Configuration file

The configuration file is organized in 6 sections. Take a look at the example file, config/phobos.yml.example.

The file will be parsed through ERB so ERB syntax/file extension is supported beside the YML format.

logger configures the logger for all Phobos components. It automatically outputs to STDOUT and it saves the log in the configured file.

kafka provides configurations for every Kafka::Client created over the application. All options supported by ruby-kafka can be provided.

producer provides configurations for all producers created over the application, the options are the same for regular and async producers. All options supported by ruby-kafka can be provided. If the kafka key is present under producer, it is merged into the top-level kafka, allowing different connection configuration for producers.

consumer provides configurations for all consumer groups created over the application. All options supported by ruby-kafka can be provided. If the kafka key is present under consumer, it is merged into the top-level kafka, allowing different connection configuration for consumers.

backoff Phobos provides automatic retries for your handlers. If an exception is raised, the listener will retry following the back off configured here. Backoff can also be configured per listener.

listeners is the list of listeners configured. Each listener represents a consumer group.

Additional listener configuration

In some cases it's useful to share most of the configuration between multiple phobos processes, but have each process run different listeners. In that case, a separate yaml file can be created and loaded with the -l flag. Example:

$ phobos start -c /var/configs/my.yml -l /var/configs/additional_listeners.yml

Note that the config file must still specify a listeners section, though it can be empty.

Custom configuration/logging

Phobos can be configured using a hash rather than the config file directly. This can be useful if you want to do some pre-processing before sending the file to Phobos. One particularly useful aspect is the ability to provide Phobos with a custom logger, e.g. by reusing the Rails logger:

Phobos.configure(
  custom_logger: Rails.logger,
  custom_kafka_logger: Rails.logger
)

If these keys are given, they will override the logger keys in the Phobos config file.

Instrumentation

Some operations are instrumented using Active Support Notifications.

In order to receive notifications you can use the module Phobos::Instrumentation, example:

Phobos::Instrumentation.subscribe('listener.start') do |event|
  puts(event.payload)
end

Phobos::Instrumentation is a convenience module around ActiveSupport::Notifications, feel free to use it or not. All Phobos events are in the phobos namespace. Phobos::Instrumentation will always look at phobos. events.

Executor notifications

• executor.retry_listener_error is sent when the listener crashes and the executor wait for a restart. It includes the following payload:
  • listener_id
  • retry_count
  • waiting_time
  • exception_class
  • exception_message
  • backtrace
• executor.stop is sent when executor stops

Listener notifications

• listener.start_handler is sent when invoking handler.start(kafka_client). It includes the following payload:
  • listener_id
  • group_id
  • topic
  • handler
• listener.start is sent when listener starts. It includes the following payload:
  • listener_id
  • group_id
  • topic
  • handler
• listener.process_batch is sent after process a batch. It includes the following payload:
  • listener_id
  • group_id
  • topic
  • handler
  • batch_size
  • partition
  • offset_lag
  • highwater_mark_offset
• listener.process_message is sent after processing a message. It includes the following payload:
  • listener_id
  • group_id
  • topic
  • handler
  • key
  • partition
  • offset
  • retry_count
• listener.process_batch_inline is sent after processing a batch with batch_inline mode. It includes the following payload:
  • listener_id
  • group_id
  • topic
  • handler
  • batch_size
  • partition
  • offset_lag
  • retry_count
• listener.retry_handler_error is sent after waiting for handler#consume retry. It includes the following payload:
  • listener_id
  • group_id
  • topic
  • handler
  • key
  • partition
  • offset
  • retry_count
  • waiting_time
  • exception_class
  • exception_message
  • backtrace
• listener.retry_handler_error_batch is sent after waiting for handler#consume_batch retry. It includes the following payload:
  • listener_id
  • group_id
  • topic
  • handler
  • batch_size
  • partition
  • offset_lag
  • retry_count
  • waiting_time
  • exception_class
  • exception_message
  • backtrace
• listener.retry_aborted is sent after waiting for a retry but the listener was stopped before the retry happened. It includes the following payload:
  • listener_id
  • group_id
  • topic
  • handler
• listener.stopping is sent when the listener receives signal to stop.
  • listener_id
  • group_id
  • topic
  • handler
• listener.stop_handler is sent after stopping the handler.
  • listener_id
  • group_id
  • topic
  • handler
• listener.stop is send after stopping the listener.
  • listener_id
  • group_id
  • topic
  • handler

Plugins

List of gems that enhance Phobos:

Phobos DB Checkpoint is drop in replacement to Phobos::Handler, extending it with the following features:

• Persists your Kafka events to an active record compatible database
• Ensures that your handler will consume messages only once
• Allows your system to quickly reprocess events in case of failures

Phobos Checkpoint UI gives your Phobos DB Checkpoint powered app a web gui with the features below. Maintaining a Kafka consumer app has never been smoother:

• Search events and inspect payload
• See failures and retry / delete them

Phobos Prometheus adds prometheus metrics to your phobos consumer.

• Measures total messages and batches processed
• Measures total duration needed to process each message (and batch)
• Adds /metrics endpoit to scrape data

Development

After checking out the repo:

• make sure docker is installed and running (for windows and mac this also includes docker-compose).
• Linux: make sure docker-compose is installed and running.
• run bin/setup to install dependencies
• run docker-compose up -d --force-recreate kafka zookeeper to start the required kafka containers
• run tests to confirm no environmental issues
  • wait a few seconds for kafka broker to get set up - sleep 30
  • run docker-compose run --rm test
  • make sure it reports X examples, 0 failures

You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.

Test

Phobos exports a spec helper that can help you test your consumer. The Phobos lifecycle will conveniently be activated for you with minimal setup required.

• process_message(handler:, payload:, metadata: {}, encoding: nil) - Invokes your handler with payload and metadata, using a dummy listener (encoding and metadata are optional).

### spec_helper.rb
require 'phobos/test/helper'
RSpec.configure do |config|
  config.include Phobos::Test::Helper
  config.before(:each) do
    Phobos.configure(path_to_my_config_file)
  end
end 

### Spec file
describe MyConsumer do
  let(:payload) { 'foo' }
  let(:metadata) { Hash(foo: 'bar') }

  it 'consumes my message' do
    expect_any_instance_of(described_class).to receive(:around_consume).with(payload, metadata).once.and_call_original
    expect_any_instance_of(described_class).to receive(:consume).with(payload, metadata).once.and_call_original

    process_message(handler: described_class, payload: payload, metadata: metadata)
  end
end

Upgrade Notes

Version 2.0 removes deprecated ways of defining producers and consumers:

• The before_consume method has been removed. You can have this behavior in the first part of an around_consume method.
• around_consume is now only available as an instance method, and it must yield the values to pass to the consume method.
• publish and async_publish now only accept keyword arguments, not positional arguments.

Example pre-2.0:

class MyHandler
  include Phobos::Handler

  def before_consume(payload, metadata)
    payload[:id] = 1
  end

  def self.around_consume(payload, metadata)
    metadata[:key] = 5
    yield
  end
end

In 2.0:

class MyHandler
  include Phobos::Handler

  def around_consume(payload, metadata)
    new_payload = payload.dup
    new_metadata = metadata.dup
    new_payload[:id] = 1
    new_metadata[:key] = 5
    yield new_payload, new_metadata
  end
end

Producer, 1.9:

  producer.publish('my-topic', { payload_value: 1}, 5, 3, {header_val: 5})

Producer 2.0:

  producer.publish(topic: 'my-topic', payload: { payload_value: 1}, key: 5, 
     partition_key: 3, headers: { header_val: 5})

Version 1.8.2 introduced a new persistent_connections setting for regular producers. This reduces the number of connections used to produce messages and you should consider setting it to true. This does require a manual shutdown call - please see Producers with persistent connections.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/klarna/phobos.

Linting

Phobos projects Rubocop to lint the code, and in addition all projects use Rubocop Rules to maintain a shared rubocop configuration. Updates to the shared configurations are done in phobos/shared repo, where you can also find instructions on how to apply the new settings to the Phobos projects.

Acknowledgements

Thanks to Sebastian Norde for the awesome logo!

Author: Phobos
Source Code: https://github.com/phobos/phobos 
License: Apache-2.0 license

#ruby #kafka 

router.asus.com | asus router login | How to Install Asus router

There are two ways to upgrade the firmware version of your ASUS router, either you choose an upgrade online method or you choose the upgrade manual method. In the upgrade online method, you can directly perform the update process through the router.asus.com window. In the manual method, first, you need to download an available firmware for your router then you have to upload it into the web interface of your ASUS router

#router.asus.com #asus router login

5 Pocket-Friendly Essentials You All Need to Create A Home Gym

“Why should I create a home gym? I am fit and fine then why I need a home gym setup?”

During this pandemic, Thousands of people are working from home, and In such a situation, health has become the priority of all of them. Not only working employees but the health of other family members are important. The easiest way to maintain your health and fitness is to create a home gym.

A home gym is a remedy that can save the cost of your heavy gym membership. If you have a spare room then you are a lucky person where you can set up a home gym. In this blog, I will let you know about the 5 essentials that you all need to create a home gym.

Why Create Home Gym?

Save your time to go the gym
Save the money on your gym membership
One time investment
Keep your body fit and maintained
Helps to maintain hygiene
Helps to lose belly fat
No time-bound and more.

In our busy lives, a home gym could be a boon for all of us, and in this corona war, Eazyro has come up with a set of home gym equipment and home gym machines.

5 Essentials to Create A Home Gym

Dumbbells

Dumbbells play a very important role in the gym. Whether you want to lose weight or want to strengthen your muscles, dumbbells are one of the most ingenious parts of equipment you can add to a home gym. Dumbbells set with a rack has come up in a variety of weight, you can choose as per the need of your body weight.

Barbell

With a barbell set, your dumbbells and barbell sets will get complete. A barbell weight set helps to gain strength in your muscles. The combination of dumbbells and barbell make your home gym complete.

Electric Treadmill

From ancient time, walk and running both are considered as the best exercise that keeps your brain and heart-healthy. Through electric treadmills, you can run and walk in your own house, it overcomes the stress of weather conditions and makes your morning healthy.

Skipping Rope

With skipping rope, we all have our childhood memories. This is not surprising that skipping rope is a fantastic cardio and coordination tool. It will give an experience of a full-body workout. It helps to stabilize your legs, hands, mind, upper body for jumping.

Pull Up Bar

Pull-ups are an excellent way to strengthen your upper body and keep it more healthy. My personal trainer and other professional trainers always recommend pulling bars in the gym essentials.

Conclusion

A home gym is a place that is a one-time and long-time investment. I think people should care about their physical fitness during this pandemic. If you are looking to buy home gym equipment, exercise machines for home, or cardio machines for home, but only at Eayro which is the best platform that has home gym types of equipment available at affordable prices.

#home gym equipment #home gym machine #exercise machine for home #home gym equipment for sale #cardio machines for home

Cannot start Microsoft Office Outlook

On this site, you’ll see working methods to repair the “can’t start Microsoft Outlook” issue. Additionally, these methods can enable you to get up your Outlook and running again without any mistakes.

Now, let us see how it is possible to fix and prevent a much worse situation when you can’t start Outlook. But first, we’re beginning from the reason and symptoms of the mistake.

Recover your Outlook with Outlook PST Recovery.

Which are the causes and symptom of the “Don’t start Microsoft Outlook” mistake?

The most important symptom of the matter is quite clear and readily identifiable. After you click on Outlook you’ll discover a dialogue box appears and can be hanging for a little while, then you receive the “can’t start Microsoft view. cannot open the outlook window. The set of connections can’t be opened” error.

Can’t start Microsoft Outlook

In case the file has corrupted then you are going to discover that its dimensions become kb.

Additionally, there’s absolutely no specific cause for this mistake, but all versions of MS Outlook from 2003 into Outlook 2019 might be impacted. Anyhow, whatever the motive is, the result is the same – you can’t start Outlook. . And the answers for this query are given below.

Workarounds to Solve “Don’t start Microsoft Outlook” problem

Now you understand the reasons why causes “can’t start Microsoft outlook. Cannot open the view window. The collection of folders cannot be opened” problem. Therefore, let us see how to have them repaired. Below there are 2 workarounds that fix this situation.

1. Recover the Navigation Pane configuration file

Typically it’s the corrupt Navigation Pane settings file that limits Microsoft Outlook from the beginning, so the first thing you have to do would be to regain it. Here is how you can do this task:

Click on the Start button.

Following that, Compose the"outlook.exe /resetnavpane" control and click on OK.

If you discover any difficulty and unable to recoup the Navigation pane settings document, then attempt to manually delete the XML file which stores the navigation pane configurations. To do this, go using the next measures:

It’ll open the folder in which MS Outlook Setup files are saved.

Cannot start Microsoft Outlook

2. Repair your Outlook data files with the help of Scanpst.exe.

Then default Outlook data file PST may be damaged or deleted, that’s the reason you can’t start Outlook. The document Outlook.pst isn’t a personal folders file"

To do so, do the Actions listed below:

Below you’ll discover Scanpst.exe from the listing. Double click it.

Additionally, you can go via Start and kind scanpst.exe from the Search box.

Following that, you’ll discover a window click the Browse button to choose your default Outlook.pst file.

After a couple of minutes, your document is going to be fixed.

Hopefully, your document got fixed. If not Then You Need to attempt the alternative provided below:

The majority of the time it fixes the documents. However, if the corruption is intense then this instrument fails. In these situations, you want to utilize PST File Retrieval designed by Mailconvertertools. A novice user can utilize this tool and fix their own Outlook PST files. It’s the very best way to recuperate and fix Outlook PST files and it simplifies all the constraints of the Inbox Repair Tool.

Conclusion

This technical manual is all about how to resolve “can’t start Microsoft outlook. Cannot open the view window. The collection of folders cannot be opened” I am hoping that your issue has been solved. When there’s any difficulty regarding any measure then don’t hesitate to contact.

#cannot open the outlook window #the set of folders cannot be opened outlook #outlook the set of folders cannot be opened #the set of folders cannot be opened outlook 2016 #outlook the information store cannot be opened #outlook information store could not be opened