• November 14, 2019, 10:26:34 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.

Pages: [1] 2 3 ... 10
 1 
 on: Today at 08:05:41 AM 
Started by Mr.Navy - Last post by GreenBay42
You beat me to it Mr Navy :) 

New version is available - BUT there may be an issue with push notifications not working (which they are looking in to)

 2 
 on: Today at 03:14:40 AM 
Started by Mr.Navy - Last post by Mr.Navy
Version 3.0.10 is available now - It is working again.

Thank you all for the support!

 3 
 on: November 13, 2019, 10:58:55 PM 
Started by journeyman - Last post by journeyman
Hi all,

I setup the above devices for port trunking. The following devices are connected to the DGS:
6 Workstation, Printer, 2 Ports for QNAP, Fritzbox. All Ports are set to Auto Speed.

Setup:
QNAP: Port Trunking / Managed Switch / 802.3ad dynamic / Mac+IP

DGS (Firmware 6.10.xxx) : The device was configured as described here: https://eu.dlink.com/uk/en/support/faq/switches/layer-2-gigabit/dgs-series/uk_dgs_1210_configure_link_aggregation_lacp

Unfortunately I only get a max download bandwidth of 30GB/s. And it takes minutes for the contents of a folder to be displayed.
Even the Internet connection via the DGS is extremely slow.
I tested the speed by connecting one device directly with the Fritzbox. Speed as expected.

Looks like the DGS slow down my network traffic.
What did I miss? Any Ideas? Is there a best practice for setting up such a switch?

Regards Lutz

 4 
 on: November 13, 2019, 01:17:27 PM 
Started by jvf - Last post by PacketTracer
Hi,

the PVID setting X of a port is for ingress traffic and defines the VLAN (=X) an incoming untagged ethernet frame will be assigned.
For egress traffic via that port this corresponds to the port being set to be an untagged member of the same PVID VLAN value X (a frame internally tagged with VLAN X will be sent untagged, when leaving the switch via a port that is an untagged member of VLAN X)

Both settings together correspond to a Cisco access port configured for VLAN X or to a Cisco trunk port configured for VLAN X to be the native VLAN:

Code: [Select]
interface e1/1
 description - access port for VLAN X
 switchport access vlan X
 switchport mode access

interface e1/2
 description - trunk port, native VLAN X
 switchport mode trunk
 switchport trunk native vlan X
 switchport trunk allowed vlan X,...

Any port can be an untagged  member of a single VLAN only.

But a port can be a tagged member of one or more VLANs. And tagged membership is symmetric, that is it covers both ingress and egress.
If a port is a tagged member of VLAN Y, egress frames will be sent tagged with VLAN Y and ingress frames are only accepted, if they are tagged with VLAN Y (otherwise they will be dropped).

For your scenario I'd suggest, that you configure the mustard ports at your Cisco switch to be trunk ports with native VLAN 1 as follows:

Code: [Select]
interface ...
 switchport mode trunk
 switchport trunk native vlan 1
 switchport trunk allowed vlan 1,90

The mustard ports at your DGS switches then must be configured as follows:

PVID = 1 (=default)
untagged member of VLAN 1 (=default)
tagged member of VLAN 90

The red ports must be configured as follows:

PVID = 90
untagged member of VLAN 90

The green ports must be configured as follows:

PVID = 1 (=default)
untagged member of VLAN 1 (=default)

PT

 5 
 on: November 13, 2019, 12:10:45 PM 
Started by dny - Last post by FurryNutz
Good then a reboot may have been all that was needed then. Use the factory reset as a last resort.

Enjoy.

 6 
 on: November 13, 2019, 11:51:19 AM 
Started by dny - Last post by dny
Thank you for your reply.

If by "region"you mean what part of the world, I am in California.  Factory reset was not performed.

I cold booted the DSL modem/source of wireless signal that the DAP-1650 was extending.  This latter maneuver worked and now the DAP is repeating the signal just like it had been before it decided not o.  Next time I will do this first.

 7 
 on: November 13, 2019, 11:41:23 AM 
Started by sewing1243 - Last post by FurryNutz
When DAP is in Extender mode, it's supposed to be using the same channels as the main host signal. This is normal operation.

I have a DIR-885L Router and and a DAP-1650 Extender.  I was running the DAP-1650 in bridged mode, but I ran some Cat-5E and connected all the wired devices directly to the router that were connected via the DAP-1650 and I switched  the 1650 to Extender mode to  improve the wireless signal in the back of the house.

Now no matter what I do the Extender insists on using the same RF channel as the router (manual channel selection or automatic). Is this the way it's designed to work or is it some kind of glitch (or setup error on my part). The SSID on both devices is different (the extender has the same SSID with the letters "ext" added to the end to differentiate between the two devices).

The internet seems to imply that using the same SSID on both is fine, but also use different channels if you do that.

Both devices have the latest version of firmware installed (DIR-885L Hardware Version: A1 Firmware Version: 1.21...DAP-1650 Hardware Version : A2 Firmware Version : 1.04)

Any input/help would be great.

 8 
 on: November 13, 2019, 11:40:17 AM 
Started by dny - Last post by FurryNutz
Link>Welcome!

  • What region are you located?
  • Was a Factory Reset performed before after any firmware updates then set up from scratch?

 9 
 on: November 13, 2019, 11:38:27 AM 
Started by kezzism - Last post by FurryNutz
The router management page will always be accessible from the LAN side. If it was disabled, you could not configure it.

 10 
 on: November 13, 2019, 11:24:12 AM 
Started by GreenBay42 - Last post by GreenBay42
On September 30, 2019, D-Link became aware of a 3rd Party security researcher that accused the DAP-1860 Hardware Rev. Ax of a command injection security flaw that may lead To unauthenticated remote code execution (RCE) security vulnerability.  The devices is deployed LAN-side or in-home and does not require internet services, this does reduce some risk since a malicious user or attack would have to be with-in physical proximity and be able to connect to the DAP-1860 WiFi signal that has WiFi encryption on as default.

As D-Link investigated, and validated the report, and in coordination with the 3rd Party we have release the following Beta Hot-Fix. We recommend always to keep up-to-date firmware which can be found at https://support.dlink.com/ProductInfo.aspx?m=DAP-1860

The Beta Hot-Fix has been through the required cyber-security testing and software quality assurance for the specific issue.  This releases has not been through a complete cycle, nor will it be released as a fully qualified software release.

FIRMWARE - ftp://FTP2.DLINK.COM/SECURITY_ADVISEMENTS/DAP-1860/REVA/DAP-1860_REVA_FIRMWARE_v1.04B03_HOTFIX.zip

SOURCE - https://supportannouncement.us.dlink.com/announcement/publication.aspx?name=SAP10135

Pages: [1] 2 3 ... 10