• March 29, 2024, 01:34:57 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: DIR-890L - Connected Clients and Syslog  (Read 5922 times)

JavaWeasel

  • Level 1 Member
  • *
  • Posts: 3
DIR-890L - Connected Clients and Syslog
« on: September 17, 2015, 02:41:09 AM »

I received the DIR-890L (HW:A1) today.

I updated the firmware to 1.08 already and have done multiple factory resets.
Region: US

After slogging through the setup, during which it set itself to many and various IP addresses that had nothing to do with my existing network, I finally got it to work. This took multiple factory resets and sniffing for the router on the network with nmap.

The problems I'm seeing are:
1) Syslog:
a) is there a way to include the hostname in the syslog messages?
Our syslog server is receiving messages from several machines, and I can guess that the following messages are from the DIR-890, but they're buried. It would be nice to be able to grep on the device's host name.
-----------
Sep 17 02:02:42 Got new client [D0:A6:37:85:F6:04] associated from BAND24G-1.1 (2.4 Ghz)
Sep 17 02:02:47 Got new client [D0:A6:37:85:F6:04] associated from BAND5G-1.1 (5 Ghz)
-----------
b) Is there a way to add the assigned IP and Client name to the above syslog messages?  When a client disappears from the network, there is no record of what IP was connected and what device name it was and when.

2) Connected Clients:
a) I cannot edit any names. I've tried Opera, FF, IE, Safari, and Chrome, on Mac, Windows, and iOS. I can enter a name, but it doesn't "take".
b) Wireless Clients that are assigned a fixed IP on the client don't ever show up, even if they are actively connected to the router. I've got two wireless cameras that are not seen in the "Connected Clients" list, even though they are actively transmitting.
c) There is no record of recent clients.
d) The "Connected Clients" also includes all the hard-wired, fixed IP desktop machines and servers that live on the network. I don't really want to see those machines in the list.

Thanks for any help.
« Last Edit: September 17, 2015, 02:46:07 AM by JavaWeasel »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: DIR-890L - Connected Clients and Syslog
« Reply #1 on: September 17, 2015, 06:49:33 AM »

Link>Welcome!

  • Are you wired or wireless connected to the router?
  • Was a Factory Reset performed before and after any firmware updates then set up from scratch?
  Link> >FW Update Process

Internet Service Provider and Modem Configurations
  • What ISP Service do you have? Cable or DSL?
  • What ISP Modem Mfr. and model # do you have?

"After slogging through the setup, during which it set itself to many and various IP addresses that had nothing to do with my existing network, I finally got it to work." - How do you mean? Do you use a different IP address pool other than 192.168.0.#?

"I cannot edit any names. I've tried Opera, FF, IE, Safari, and Chrome, on Mac, Windows, and iOS. I can enter a name, but it doesn't "take". - What versions of Mac and Windows are you using? What versions of Browsers? I have been able to edit host names and make them stick.

Is this being used at home or for a business?
The syslog server provides basic information since this is a home class router. I don't think any more advanced logging was intended by D-link since there isn't a lot of use of it by home class users.


Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

JavaWeasel

  • Level 1 Member
  • *
  • Posts: 3
Re: DIR-890L - Connected Clients and Syslog
« Reply #2 on: September 21, 2015, 12:28:01 AM »

Hello FurryNutz,

Thanks for digging into this.

Are you wired or wireless connected to the router?
Both. "Connected Client" thing happens on either method.
Was a Factory Reset performed before and after any firmware updates then set up from scratch?
Yes. Five times.

What ISP Service do you have? Cable or DSL?
What ISP Modem Mfr. and model # do you have?

N/A...it's set up in AP mode.

How do you mean? Do you use a different IP address pool other than 192.168.0.#
No, our existing network is 192.168.0.x.  Since we already have a wired router/firewall assigned to 192.168.0.1, the DIR890L fell back to using a couple of IPs from the DHCP pool, as I would expect. However, after one of the resets, it assigned itself an IP from its "guest network"  (192.168.7.1),  and twice it assigned itself "192.168.100.1".  ...And our DHCP server doesn't even serve that network. I needed nmap to find that IP.

What versions of Mac and Windows are you using? What versions of Browsers? I have been able to edit host names and make them stick.
OS:  OSX Yosemite, iOS 8.4, Windows 7 SP1, and Linux FC22. The browers: IE11, FF 40.0.2, Chrome 45.0.2454.93, Opera 32, Safari whatever-comes-with-Yosemite-and-iOS. After trying multiple times on multiple OS and browser combos, I was only able to get one of the client names to change, and when I logged in again about an hour later, it was back to "UNKNOWN". It still showed the same MAC number.  I still can't figure out why it faithfully lists all the static, wired machines on the network and only about half of the connected wifi clients.

Is this being used at home or for a business?
Home with an attached office.
The syslog server provides basic information since this is a home class router. I don't think any more advanced logging was intended by D-link since there isn't a lot of use of it by home class users.
I understand.   ...But on the other hand (playing devil's advocate here) how many home users have access to a remote syslog server anyway? It doesn't seem the kind of thing a home user is likely to have sitting around. It seems that a 500-line text file on the unit itself would be more practical.

Thanks!
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: DIR-890L - Connected Clients and Syslog
« Reply #3 on: September 21, 2015, 07:28:25 AM »

I think when AP mode is selected on the 890L it defaults to 192.168.0.50, Once you reach this, then you can set up a new IP address or look at the main host routers DHCP client table to see if it was assigned something else if connected.

Ya, D-Link seems to go after the set it and forget it users so having some features or less in keeping things simplified seems to be how D-Link wants some of there products.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

JavaWeasel

  • Level 1 Member
  • *
  • Posts: 3
Re: DIR-890L - Connected Clients and Syslog
« Reply #4 on: September 23, 2015, 11:27:12 AM »

Ah well...at least it's up and running and it's fast.   

...now if it were only possible to set up a guest net in AP mode...

Thanks for the insight.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: DIR-890L - Connected Clients and Syslog
« Reply #5 on: September 23, 2015, 12:24:41 PM »

Guest Zone is only supported in Router mode as it requires the use of the WAN port.

Enjoy.  ;)
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.