Print

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

[FurryNutz]

Im curious as to why there are numberous entries about my Mac Laptop connecting to the 4500 when I'm just chatting online and browsing during this time frame? No wireless house phones are in use. I did notice after about and hour of using my LT, I got a disconnection from the 4500 and it finally reconnected in about a minute. Wireless still needs some work? Using B08 FW.

[INFO]   Tue Dec 08 13:46:27 2009   Airport One N: Wireless system with MAC address 0021E9E1CDCB secured and linked
[INFO]   Tue Dec 08 13:46:21 2009   Airport One N: Wireless system with MAC address 0021E9E1CDCB associated
[INFO]   Tue Dec 08 13:46:21 2009   Above message repeated 1 times

[INFO]   Tue Dec 08 13:34:38 2009   Administrator logout
[INFO]   Tue Dec 08 13:26:56 2009   Airport One N: Wireless system with MAC address 0021E9E1CDCB secured and linked
[INFO]   Tue Dec 08 13:26:56 2009   Airport One N: Wireless system with MAC address 0021E9E1CDCB associated
[INFO]   Tue Dec 08 13:26:56 2009   Above message repeated 1 times

[INFO]   Tue Dec 08 13:17:51 2009   Administrator logout
[INFO]   Tue Dec 08 13:16:33 2009   Airport One N: Wireless system with MAC address 0021E9E1CDCB secured and linked
[INFO]   Tue Dec 08 13:16:33 2009   Airport One N: Wireless system with MAC address 0021E9E1CDCB associated
[INFO]   Tue Dec 08 13:16:33 2009   Above message repeated 1 times
[INFO]   Tue Dec 08 13:06:39 2009   Airport One N: Wireless system with MAC address 0021E9E1CDCB secured and linked
[INFO]   Tue Dec 08 13:06:39 2009   Airport One N: Wireless system with MAC address 0021E9E1CDCB associated
[INFO]   Tue Dec 08 13:06:39 2009   Above message repeated 1 times


[INFO]   Tue Dec 08 13:02:17 2009   Airport One N: Wireless system with MAC address 0021E9E1CDCB secured and linked
[INFO]   Tue Dec 08 13:02:11 2009   Airport One N: Wireless system with MAC address 0021E9E1CDCB associated
[INFO]   Tue Dec 08 13:02:11 2009   Above message repeated 1 times
[INFO]   Tue Dec 08 13:01:25 2009   Airport One N: Wireless system with MAC address 0021E9E1CDCB secured and linked
[INFO]   Tue Dec 08 13:01:12 2009   Airport One N: Wireless system with MAC address 0021E9E1CDCB associated
[INFO]   Tue Dec 08 13:01:12 2009   Above message repeated 1 times
[INFO]   Tue Dec 08 11:45:21 2009   Airport One N: Wireless system with MAC address 0021E9E1CDCB secured and linked
[INFO]   Tue Dec 08 11:45:21 2009   Airport One N: Wireless system with MAC address 0021E9E1CDCB associated
[INFO]   Tue Dec 08 11:45:21 2009   Above message repeated 1 times

[consealer]

Have been using the DGL4500 A1 - 121 Beta 03, has been working fine for me for at least 2 week, haven't had any restarts, i will move to the beta08 now that i know its out.  its nice to see that dlink has taken notice to our pissing and moaning, Sincere thanks to the people working on this project.  seems like its all up hill from here.

[shayking]

so far so good,

B03 Uptime has been 18 hours compared to 20min-2hrs with 1.21NA official.
sorry no status for B08

DGL4500 A1: Default settings with wlan name/wpa2 & computer time adjusted.

LAN1 = HTPC1 Win7 x64
LAN2 = HTPC2 Win7 x86
LAN3 = Test sys Hackintosh/XP/7
LAN4 = HDHomerun UPNP dual ATSC Tuner
WLAN1= Laptop G
WLAN2= Ipod Touch,HTPC1 Remote,ORB (atsc tv stream)

note: when i first purchased this A1 unit, fw1.02 did not work at all, just enough to get to the latest fw (1.1x).
I updated to 1.21NA for what ever reason late summer, all of a sudden late november/dec the dgl45 went loopy.

all is good with B03

ty
sk

[deezomaxima]

I'm on 8 days, 6 hours uptime and no lockups. Much more stable than 1.21NA prod FW.

[FurryNutz]

What FW are you using? Beta ?

[deezomaxima]

Yes, beta. 1.21NA Beta 08.

[FurryNutz]

Same here, looking good. Hope they get wireless more stable. 

[FurryNutz]

Try reading the thread fully and you might get the point. We are trying to provide Dlink with some ping information regarding the Wireless connection to the 4500. Are you using the 4500 for wireless? I presume that if your not then it's not to worry yourself. Thanks but I'll pass the on stale cookies. I have fresh ones from everyones mom. Have a great week and Merry Christmas.

[FurryNutz]

Thats ok, not worried, The post doesn't concern you. And I never said I was the know.

[deezomaxima]

Try looking at my screen shot again before you open your mouth again. Like I said the router and firmware when this was taken wasn't available to the public. It was posted here because I didn't have write access for some reason when they gave me ftp access. You trolling the dlink forums doesn't mean you are in the "know".

I wish I still lived at home and my mom baked me cookies...  

Dude, slow your roll. Everyone here is trying to provide feedback so we can get this **** taken care of. Fuzzy has been helpful so what's all the hateration about? Keep it on topic before this thread gets locked up and people get banned. All the extra talk is not helping anyone.

[deezomaxima]

Me slow my roll? You obviously have no clue on what is going on in the background to resolve the issues with the firmware. Not only myself but others volunteer their time to capture data with special dgl4500's. Any improvements in the latest firmware were not because FurryNuts has trolled the fourm. Please enlighten me on what FurryNuts has done. I wasn't aware he was able to capture/log and help the devs at dlink.

His post stating that his macbook worked fine has no bearing into troubleshooting any technical problems and is in no way helpful. Like I told him, know what you are talking about before you open your mouth.

Happy Holidays...

I'm not going to enlighten you on anything and I do know what I'm talking about. Seems like you have a personal issue just because Fuzzy posts in every thread. That's his business and not yours. Matter of fact, if Lycan thinks it's a problem, it's for him to say, not you.

I'm having the same problems with my router in which you don't know how to fix either. The intelligent folk here are trying to help these Dlink folks out with data and you're here trying to flame people.

It would be really nice of Dlink to just ban you from the site and let you deal with your issue on your own. Deal with your own emotional issues outside of this forum because we don't really care what you're going thru. We're here to help figure out this router issue.

Happy Holidays? You don't even seem like a happy person.

[FurryNutz]

Well I'm going to leave all the information up to people at Dlink and WILL continue to post any information I feel may or may not help Dlink in there development of there products. IMO, your not qualified to judge who's postings may or may not be of any help. However feel free to do as you wish. I don't have to pay any attention and thus my discussion on regarding this with you is closed. Any information continuing will be directed to Dlink.  Have a great day.

[deezomaxima]

We're here trying to provide feedback to help Dlink fix the issue, period. If I knew what was going on and expertise in writing firmware, the issue would be fixed already.

[Lycan]

Wow. OK. Thats enough of that.

Knock it off. All of you.

I'm locking this thread as it's reached a rediclous length and people are no longer working together.

There are other feedback links. Work there and keep it clean.