Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[GeoRyu]

WARNING
PLEASE READ EVERYTHING FIRST BEFORE REPLYING.

Hey hey, I'm new to the forums here. But I happen to see that there is a lot of complaints about this particular product. And I wanted to just throw in my 2 cents.

The Router Works Fine.

I had no problem running both 2.4 and 5.0 Bandwidth. With WiFi password and without. It does it's job. The 2.4Ghz Range Plus works. I have set up the router on the 2nd floor at the highest it can go. And everyone get's full bars all over the house. I even get 4-5 bars outside in my car on my phone.

With that said,
     The only issue I have with this thing is a damn new netbook I got for Christmas with a Mac Address starting with 0C-EE-E6-XX-XX-XX. The Router finds the Mac Address invalid. In which I can come to understand cause seeing a Mac Address starting like that is completely new to me. Every Mac Address I have, started with 00 except the netbook. So now, I spent days trying to find firmware updates, patches, anything! I even attempted to spoof the Mac Address on the netbook but Microsoft has a bug on Windows 7. (I have the Starter Edition that came with the netbook)
 
Just to note:
Windows 7 Mac Spoofing works with WIRED Connection. But it does not work with WIRELESS Connection. I used 3rd Party Tools: SMAC and etc... I attempted Registry Edits, I changed even the value key to the "Orginal Mac Address" and it just wont change [New Strings/Network Address Edits included]. I have been banging my head about this for a week now. The Internets has many answers but they did not work. So Spoofing the Mac Address is out of the question. Until Microsoft fixes this bug.

Anyway: Did D-Link release any sort of beta update/driver/firmware or anything to resolve this at all? Oh hell, is there a modded firmware to force the Router to take this stupid paradox of a Mac Address?

Currently: I have the Router's WiFi Password-ed with Default Factory Settings {Hardware Version: B1       Firmware Version: 2.02NA}. But I hate it, my family is PC illiterate and life was easy with a simple Mac Filter setup. If anyone can please help with this matter? I'll try my best to co-operate with whatever that is needed.

P.S. I used the search to find a topic about this but did not find it. No flaming please. I'm here for answers, not jerks.

[Edit: Grammar ]

[jprafter]

I have the exact same issue, my new HP has a MAC starting with 90, all others are 00.

[stephanp]

Same Problem here as well.  Spoke with Technical Support the other day and the rep told me MAC Filtering does not work with addresses not starting with 00:  They recognize that this is an increasing problem with newer Windows 7 PCs.  I was told to keep a lookout for a Firmware update, but, no release schedule was specified.  I hope they fix this soon.  I replaced a 5-year old Linksys router that could handle MAC filtering with an address starting with 1C:  I am disappointed that D-Link hasn't worked this out. 

[rickm1350]

actually, it's not a Windows 7 issue.  The MAC address is set by the network adapter manufacturer.

[GeoRyu]

Well, it's an issue that needs to be addressed. I can't spoof to get around this. The only way around it that I found, is to buy a separate USB Wireless Adapter that has a mac starting at 00 and use that on the netbook. WTF is that all about? Now I'm forced to buy another wireless device just to make it work with the damn router? C'mon man. I'm sure it's not that difficult to just simple have the router read new mac network addresses. Shouldn't even require a hardware change, simply software/firmware. A patch that can be executed very quickly.

I run games on PC all the time, patches only takes long when Devs become either lazy or are trying to fix hundreds of other things and make it one big ol' package. Which can cause more problems but that's me. I'd rather fix things incrementally.

I hope there's a fix soon.

[ttstts]

This is a problem not just for PCs but also for iPhones and iTouch devices that are currently shipping with MAC addresses starting with 64.  Dlink has been notified and claim that a fix is pending.  Hopefully that will be soon, as I will otherwise need to return this new router while that option remains available.

[Dan Meis]

This is not just a problem with new PCs -- our older Xerox Phaser 860DX and WorkCentre C2424 printers have mfr's preambles of "08:00:11", and an old Amiga 2000 NIC has a preamble of "ae:00:00" (Ariadne, I think).  We're talking as far back as early-early nineties here people, 10BASE2 was king and some 10BASE5 was still out there.

It's really surprising that D-Link designers didn't take this into account.  Evidently they didn't read the RFCs very well -- IEEE 802.x addresses beginning with octets other than "00" have been around for a long time.  (The first mention of "ETHERNET NUMBERS OF INTEREST" is found in RFC 820, January 1983, and lists initial octets 02, 06, and 08).

Also, the DIR-825 is not the only D-Link product to have this issue -- the new DIR-330 VPN router we just purchased is buggy as well in the DHCP server, and no new firmware yet (IIRC, our older DI-514, DI-524, and DI-628 didn't have the issue).

I'm really aggravated that I can't deploy the hardware until this is fixed; and since it's a such silly goof, I certainly expect the dev's to have this on the top of their list.  It should be a real simple fix -- just don't look at the initial octect at all.  If somebody typed it wrong, it can be fixed easily enough -- I don't know why they bothered with the extra code to check it in the first place.

[bookie56]

Hi guys

Well, took up this issue on the Ubuntu forums while dealing with a remote desktop issue with nomachine. I usually have the dhcp server setup on my DIR-825 and like to reserve ip addresses for servers like naslite which usually have a dedicated ip address....

Was just working with an issue to do with remote desktop, so I logged into my router for a butchers....d-link lists my customer's computer but because it has the P6T Deluxe V2 motherboard with two inbuilt network mac addrssses and that they both begin with e......... I can't reserve the address....and the even funnier thing is my router has given a time for my mac address which is in September 1927....I have checked all settings and clocks....LOL 1927 was probably a good year for something...

I hope they come up with a fix for this soon or I will have to recommend a pci network card instead!

bookie56

[iepeus]

Glad I found this thread because I'm having the same problem. If this does not get addressed within the next week or two I'll be returning this router.  Does anyone know if this issue effects all D-Link routers or just the DIR-825?  I thought I'll spend a little extra and get something nice that will do absolutely everything I would need to do and then I get it home, set it up, go to filter MAC's and bam totally irritating problem.  Ugh.   

[user11]

http://www.technitium.com/tmac/index.html is MAC address changer for Win7, although some say there is an limitation in Win7 requiring manually set MACs to start with 12:xx:xx:xx:xx:xx ?? I don't know why all the fuss over MAC filtering, WEP is even safer than a MAC filter, doesn't take but couple seconds to break through MAC vs. minutes for WEP. http://blogs.zdnet.com/Ou/index.php?p=43

[bookie56]

Hi user11 

Nice one! I will have a butcher's at technitium.

bookie56

[iepeus]

Thanks user11 for the info. I'll be moving away from MAC filtering based on your posted links and other sources. I just find it irritating that this issue exists. I will be holding on to this router, I streamed some HD movies last night and it worked like a charm.   

[DJAikou]

I hope they fix this soon! Not being able to use MAC filtering really sucks! Has anyone heard when the update is coming?

[atom88]

I just bought a brand new computer with an ASUS P533 PRO GB Ethernet built into the motherboard in it that won't work.  It has an ethernet MAC address that starts with 90:36:.....  It won't work either on the DHCP server reservation list!

COME ON D-LINK!  FIX YOUR BUGGY SOFTWARE AND RELEASE A PATCH ASAP! 

Why are you error checking for something other than a valid HEXADECIMAL string?  Surely you could release a patch of the firmware to solve this.  Perhaps there's a javascript function in the browser you're using to check this that could be faked out on the router's admin page?

It has a GigBit (1000 MB/sec) ethernet network card built into it.

It's based on the Marvell88E8056 PCIe Gigbit LAN controller

The operating system has nothing to do with the MAC address (as that's a hardware issue).  Perhaps Ubuntu has something to spoof the MAC address?

I have a triple boot: Ubuntu 9.10 Karmic Koala, Windows 7, & Win XP 64-bit.

In Ubuntu I do: "lspci" from the command prompt and get this:
Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)

[zahmed70]

I called the tech support, after jumping over the lower staff, I finally got the Senior level
support, he told me that they are aware of this issue, the new firmware in the Beta Testing and will be released soon..... Oh well