Asus Router Remote Log Server Issues



30-10-2016, 01:12 AM #

  1. Asus Router Remote Log Server Issues Working
  2. Asus Router Remote Log Server Issues Settings
1
Senior Member
Asus Router Remote Log Server Issues

Asus Router Remote Log Server Issues Working

. Default gateway Primary Router: (Modem/Router combo) coaxial input from the ISP, 192.168.0.1. Second Router: Asus AC-1300 ( connected toPrimary router through ethernet cable) 192.168.50.xx. Win 10 pc (remote desktop target) connected to Second Router through ethernet port. Restore the system to its factory default settings by pressing the “Restore” or 'Reset' button at the back of router for more than 5 seconds when the power light is flickering. When successfully logged in, you'll see a screen similar as the one shown below.

Asus Router Remote Log Server Issues

The Lease Table on the Bell Hub 2000 shows the Asus router address as the only leased one. I access the Bell Hub 2000, from inside my network, using 192.168.2.1. I haven’t figured out how to access the Bell Hub 2000 remotely. My Asus router is connected to one of the Wan ports on the Bell Hub 2000.


Posts: 710
ASUS Router App - Remote access
Just bought a Asus router RT-AC58U and I thought the router app is pretty cool, I can be away from home and still see and control the network at home for my family members. But after trying it out, I was disappointed that the router app only works when my device is connected to the router network.
I read on Asus website that I can manage the network anytime anywhere, so am i doing it wrong or I misunderstand what that means?
Any bros here can help?
    • [ ... ]
      How to install Entware on a router
      How to install a DLNA server
      How to enable a swap file
      How to install a mini web server
      How to send an email via router
      How to install a BitTorrent server
      How to install a web server
      How to install a PXE server
      How to install an LDAP server
      How to manage LOG files on a router
      How to install a Syslog server on a router
      How to send a WOL message to run a script
      How to install the Python interpreter
      How to install a NUT server on a router
      How to schedule jobs on a router
      How to clear the disk cache on a router
  • Blog

    • Nov 08, 2020 - 7:03 pm
      Many websites will stop working on older Android versions in 2021

    • Oct 02, 2020 - 3:34 am
      The Android 11 Privacy and Security Features You Should Know | WIRED

    • Mar 14, 2020 - 5:01 am
      Magisk may no longer be able to hide bootloader unlocking from apps

    • Dec 27, 2019 - 12:32 am
      Sony can’t build smartphone camera sensors fast enough | Engadget

    • Jul 13, 2019 - 7:01 pm
      A spy reportedly used an AI-generated profile picture to connect with sources on LinkedIn – The Ve...

  • Gallery

    • Oct 03, 2020 - 6:37 pm
      Wake On LAN Utility

    • Oct 03, 2020 - 6:26 pm
      App Manager

    • Oct 03, 2020 - 5:31 pm
      Toggle Status Widget

    • Oct 03, 2020 - 5:27 pm
      SSID WiFi Manager

    • Dec 15, 2019 - 7:36 pm
      My Computer


AsusAsus Router Remote Log Server Issues

In this page I describe how to install an additional Syslog server on a router (Asus RT-AC56U) - we use an Entware package, so please refer to this page on how to install Entware on a router.
Let's start with assumption that there are some network devices, such as VOIP phones, that do not have an internal LOG, but rely on a remote Syslog server. On a router such as the Asus RT-AC56U, an additional Syslog server can be installed so that it can be used with any network device. Note that we install an additional 'syslog', as we do not touch the router's 'syslog' server. So we will use the Entware package called 'syslog-ng'.


How to install 'syslog-ng' package

Asus router remote log server

In order to install the 'syslog-ng' daemon with the Entware packages, we need to execute the following command :
opkg install syslog-ng
The above-mentioned package contains several files, the most important are the '/opt/sbin/syslog-ng' daemon, the '/opt/etc/syslog-ng.conf' configuration file and the start/stop script '/opt/etc/init.d/S01syslog-ng'. We create a backup copy of the configuration file '/opt/etc/syslog-ng.conf'.
The following is the sample content of the above-mentioned configuration file '/opt/etc/syslog-ng.conf' :

Please referto this page for further details about configuration file 'syslog-ng.conf'. The above example is mostly used to replace the router's 'syslog' daemon, while we need an additional 'syslog', without having to touch the router's native 'syslog'. Therefore we will create another configuration file.


How to setup the configuration file of 'syslog-ng' daemon

The following is another 'syslog-ng.conf' configuration file that let us have a remote LOG server for a Cisco managed switch.

In the above-mentioned configuration file we have passed parameters to the 'syslog-ng' daemon in order to 'listen' to a router port and all that arrives on that port we write it to a LOG file. Specifically we have:

  • in section 'source' we have setup as source the same IP address of the router, protocol UDP, and port 25000;
  • in section 'destination' we have setup as destination the file '/opt/var/log/cisco.log';
  • in section 'log' we have setup as connection the LOG file specified by section 'source' and section 'destination';

Inside section 'options' the additional options dedicated to the 'syslog-ng' daemon are included, specifically:

  • for options 'chain_hostnames(no)' and 'keep_hostname(yes)' please refer tofollowing website;
  • with option 'create_dirs(yes)' we enable the creation of directories for the destination files;
  • with option 'flush_lines(0)' the daemon will act on every message received without creating any type of buffer;
  • with option 'log_fifo_size(256)' we set the number of messages to be stored on the output queue;
  • with option 'log_msg_size(1024)' we set the maximum message length in bytes;
  • with option 'stats_freq(0)' we set the daemon to collect statistics only between the 'source' and the 'destination';
  • we use option 'use_fqdn(no)' as we have used the option 'keep_hostname(yes)';
  • with options 'dir-owner(nobody)' and 'dir-group(nobody)' we set the default owner and group for the new created folders;
  • with options 'owner(nobody)' and 'group(nobody)' we set the default owner and group of destination files;
  • with option 'perm(0666)' we set the access permissions of the destination files;
  • with option 'keep-timestamp(yes)' we set the daemon to accept the date values received from the sender;
  • with option 'time-zone('Europe/Rome')' we set the daemon to convert the date values received from the sender according to the provided timezone.

In the above configuration file, the identifiers 'src_cisco' and 'log_cisco' are unique and must be used for a single sending device. Obviously we can manage multiple sending devices, using multiple identifiers, as in the following sample configuration file in which we have included, in addition to the identifiers for the above-mentioned Cisco switch, also the identifiers for two VOIP phones:


How to execute 'syslog-ng' daemon

To execute the 'syslog-ng' daemon, just run the command '/opt/etc/init.d/S01syslog-ng start'.


How to configure the remote 'syslog-ng' daemon on network devices

On network devices, simply go to the 'syslog' tab, often called 'Remote Log Servers' (or whatever), and set the IP address of the Router, where the 'syslog-ng' daemon is installed, and the UDP port used in the configuration file of the 'syslog-ng' daemon, inside the 'source' section.


Asus Router Remote Log Server Issues Settings

How to manage the LOG file created by 'syslog-ng' daemon

Keep in mind that the LOG file created by the 'syslog-ng' daemon can reach a considerable size. For a correct management of the LOG file, refer to the page 'How to manage LOG files on a router' on this website, keeping in mind that the LOG file path is that one set on the 'syslog-ng' daemon configuration file inside section 'destination'.