D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => WBR-2310 => Topic started by: bjrichus on October 19, 2008, 07:53:26 AM
-
After just a couple of days, my wireless just went away this morning.
It has been as long as two weeks before the wireless part of the router froze up or stopped it's transmitting and receiving - LED's all still blinking 'normally' - as per previous thread(s) on this fault.
This is with H/W revision A and Firmware 1.05. I have no idea what is going wrong. The clue to it not working was when my wife came into the room and said that one of our wireless PC's was not connected.
I rebooted the router (power off then on again) and everything wireless came back on again.
Perhaps one of our DLINK people here can give us an update on an ETA for when we might see a fix?
-
Hello bjrichus,
You mentioned that this happens on "one of our wireless PC's." Does this mean that other wireless computers connect just fine? Or do all of the wireless system have the same problem? It's important to note that if this occurs on just a single computer, it may in fact be that wireless adaptor giving you the problems. If that's the case, I would re-install the wireless adaptor or check to see if there is a driver update available for it.
Best of Luck,
Russell
-
Hello bjrichus,
You mentioned that this happens on "one of our wireless PC's." Does this mean that other wireless computers connect just fine? Or do all of the wireless system have the same problem? It's important to note that if this occurs on just a single computer, it may in fact be that wireless adaptor giving you the problems. If that's the case, I would re-install the wireless adaptor or check to see if there is a driver update available for it.
Best of Luck,
Russell
I have a five wireless devices connected (2 x PC's, my son's Xbox, a weather station and a web cam) and all lost the link to the router at the same time.
However, if you look at my previous posts and read all the messages lower down in this area of the forum for the last couple of months, you will see that this appears to be an identified screw-up (aka: bug) introduced on the part of DLINK with the 1.05 firmware. At least this release of the firmware is a hell of a lot better than the previous ones - but it's still not 100% right just yet.
Several other topics here confirm that many/most/all(?) of us find that the wireless now just goes away after some length of time. The LED's all appear to be functioning just fine and the wired connections are all still great, but there is a problem with there being no wireless connection.
Since I upgraded my firmware to 1.05, I had about 2 months of it working to spec - with this one exception of after about 12 or perhaps 14 days, the wireless just goes away. This report from me is because it was only a few (2 or perhaps 3??) days after the last power cycle reset of the router before the wireless died on me again.
Considering that we all seem to have this symptom (has anyone here with H/W rev A and 1.05 Firmware NOT had this?), and that it affected ALL my varied wireless devices, it would appear that this is not likely to be "my" set up, but generic to the router/firmware.
Does that make sense?
Regards.
-
Concur. Signal was lost to ALL (two of our PCs)
Not an adapter issue.
See my latest post at the top (jonesb).
-
Does the wireless signal return if you downgrade the firmware?
-
With 1.04 1nd 1.03, the signal did not go off but the ability for the remote PS to authenticate an IP address did - in other words no connectivity.
The wise owls at DLink Support told me to upgrade to firmware 1.05.
It is very clear to me from reading all the posts in this forum that the WBR 2310 has a serious issue with being able to STAY up for any length of time beyond a few days of continued power up.
There is the issue about which version, Revision A or Revision B we have. I believe I have Revision A, but am unsure if the other one is any better.
-
Does the wireless signal return if you downgrade the firmware?
Did you not read the older posts on here? Like the posts from five or six months ago?
The very reason WHY I upgraded to 1.05 was to fix the reboot problems in 1.04, 1.03, 1.02 and so on.
At least now the router no longer reboots, it's wireless just dies....
-
Hi all,
I don't seems to be having the same problem that you have... I have a wii + a pc connected by wireless and they both can get access to the web without any problem.. The only problem I have is that Windows does not seems to register the other computer every time ( I guess that is a config issue from my side )
I'm configured to send email log and I can see that :
- My wii is connecting each 2-5 min as usual
- My wireless computer gets renewed at proper time
configured with super G without turbo, TKIP personal
I have DHCP enabled and address are reserved... ( i`m also not hidding the ssid )
I don't even want to test the beta firmware because thing are running smoothly for me ( for now ) :)
---When you say.. wireless just dies... is it because you cant reach from one computer to the other or because the signal is lost on the `wireless` computer and it cant find your network ?
try activating the send log feature with all checks ... you may find someting that will help dlink guy to find your issue...
-
Did you not read the older posts on here? Like the posts from five or six months ago?
The very reason WHY I upgraded to 1.05 was to fix the reboot problems in 1.04, 1.03, 1.02 and so on.
At least now the router no longer reboots, it's wireless just dies....
Hello bjrichus,
I know I'm not quoting the reply you gave me, but it's still relevant.
I generally don't read old topics that a user made when reading the current problem (I'm fairly sure the same for Lycan as well). For that I must apologize. It does appear though you're having wireless problems. From what I've heard/dealt with this particular router and firmware there is no known issue that is wide-spread. I'm not trying to down play your issue as I really would like to help you though.
Try changing the wireless channel. You may be receiving random wireless interference that is taking down the network. You can change it to channel 1-11. You can also try changing the type of security you have. WPA2 -> WPA for example. Or just change to WEP, or vice versa. You can also change the MTU to 1472 from 1500. You can also change the RTS threshhold and Fragmentation down to 2300 from the default setting. These are all vary basic though. If your problem persists, It's probably something that may not be documented anywhere or a bit harder to probe out. From there you could start disconnectng computers one by one to see if the problem persists, set static IPs, change firewalls, Crash-Reset the router and install the firmware again, etc, etc.
Best of Luck,
Russell
-
I generally don't read old topics
You need to reread the older messages.
#1. The older versions of the firmware are really screwed-up in other ways than 1.05 is. For many of us here, the older firmware is effectively unusable.
#2. I am not alone in having this problem. It is confirmed by others here too.
All covered in the older messages.
that a user made when reading the current problem (I'm fairly sure the same for Lycan as well). For that I must apologize. It does appear though you're having wireless problems. From what I've heard/dealt with this particular router and firmware there is no known issue that is wide-spread. I'm not trying to down play your issue as I really would like to help you though.
Russell,
#1. Are you a DLINK employee?
#2. I take issue with your remarks about there being no widespread known issue. Quite unelated to my problem (a few months latter on, different batch, different retailer, different town), a friend tried to install another one of these routers at his apartment. Network Stumbler on my laptop shows that there were three other WiFi nets active in the area. All had different channels to the one we chose, he had a fixed IP, he used a variety of different encryption (thinking that might have been the problem), his router did the same as mine. He took it back to the store - to discover it was the third one the retailer had back from ticked-off users that week FOR THE SAME REASON.
#3. All your suggestions are ones we tried here on this forum... READ THE OLDER MESSAGES!
#4. I am a CCNA (Cisco Certified Network Administrator), a SCSA (Sun Certified System Administrator), and a SCNA (Sun Certified Network Administrator) and for a living I administer a network with about 100 Unix and PC servers on it. I work in a University where we have a bunch of Brocade and Cisco Catalyst gear... more 100/1000 Mb/sec copper as well as Fiber than I'd ever want to have to untangle on a dark weekend night! I used to think that DLINK gear was better than the cheaper Linksys gear and as we also have over 3,000 el-cheapo Linksys wireless routers for student WiFi access - I wanted to buy something a little better than that for my home..... Well, what a mistake that was.
#5. I also run a weather station at home for the MADIS network (Meteorological Assimilation Data Ingest System), co-funded by NASA that uploads to the Internet 24x7x365 ... my home network really does need to be operational ALL THE TIME.
I am nearly at the end of my patience with this router.
I don't want to start a flame war, but if you are not a support staff member at DLINK, and cannot come up with a better list of things to suggest, apart from turning off all the basic features of a router - like DHCP which by the way is already off here, I have been using static IP's for ages now - then please don't. as before, READ THE OLDER THREADS - we have all tried all the things you had suggested and they don't work; my view is rapidly becoming that this device is unfit for the market place.
-
Here is my latest solution to all this:
1) Reverted to Firmware 1.04 from 1.05
2) Gave DHCP reservations to my main PC (where the router is) and to the other two in the house using wireless. Each reservation required a router reset (Save Changes) - and the reservations appeared in the list - I used IP 192.168.0.100 for the main PC and 192.168.0.101 and 192.168.0.102 for the two wireless ones plus Mac addresses.
3) Changed the DHCP lease time from 180 to 9999.
So far so good; but we are just at 24 hours of up-time.
-
Russell,
#1. Are you a DLINK employee?
#2. I take issue with your remarks about there being no widespread known issue. Quite unelated to my problem (a few months latter on, different batch, different retailer, different town), a friend tried to install another one of these routers at his apartment. Network Stumbler on my laptop shows that there were three other WiFi nets active in the area. All had different channels to the one we chose, he had a fixed IP, he used a variety of different encryption (thinking that might have been the problem), his router did the same as mine. He took it back to the store - to discover it was the third one the retailer had back from ticked-off users that week FOR THE SAME REASON.
#3. All your suggestions are ones we tried here on this forum... READ THE OLDER MESSAGES!
#4. I am a CCNA (Cisco Certified Network Administrator), a SCSA (Sun Certified System Administrator), and a SCNA (Sun Certified Network Administrator) and for a living I administer a network with about 100 Unix and PC servers on it. I work in a University where we have a bunch of Brocade and Cisco Catalyst gear... more 100/1000 Mb/sec copper as well as Fiber than I'd ever want to have to untangle on a dark weekend night! I used to think that DLINK gear was better than the cheaper Linksys gear and as we also have over 3,000 el-cheapo Linksys wireless routers for student WiFi access - I wanted to buy something a little better than that for my home..... Well, what a mistake that was.
#5. I also run a weather station at home for the MADIS network (Meteorological Assimilation Data Ingest System), co-funded by NASA that uploads to the Internet 24x7x365 ... my home network really does need to be operational ALL THE TIME.
I am nearly at the end of my patience with this router.
I don't want to start a flame war, but if you are not a support staff member at DLINK, and cannot come up with a better list of things to suggest, apart from turning off all the basic features of a router - like DHCP which by the way is already off here, I have been using static IP's for ages now - then please don't. as before, READ THE OLDER THREADS - we have all tried all the things you had suggested and they don't work; my view is rapidly becoming that this device is unfit for the market place.
So all that IMPORTANT equipment and you use the LOWEST end hardware Dlink has to offer in the home class line?
I would think that a CCNA and SCSA would know better then to rely on HOME CLASS gateway device as a mission critical hardware.
Insulting people and brandishing certifications doens't impress anyone.
If the hardware is not operating in the manner that you desire return it.
As for reading older messages, have you seen the number of posts on this forum? Do you know how long it would take if every time someone needed to post to something people had to re-read an entire thread because you feel you shouldn't have to repeat yourself?
In the end it's YOU that needs help. In the future, when someone offers to help you, simply be polite and explain that you've tried those things and move on. Insulting the product and smashing people in the face with certs is a fast path to no where.
LOL Nasa is so hardup that they can't afford anything better then a WBR-2310?
-
LOL Nasa is so hardup that they can't afford anything better then a WBR-2310?
I did say that I was not looking for a flame war, but you replying with that kind of comment really does not do anything to HELP anyone, now does it?
Just look at: http://madis.noaa.gov/
I'll overlook your other comments.
The problem I have is that this router has not worked according to spec since I purchased it. I like to TRY and see problems through to resolution, and in my case (where I spend my own cash on equipment) it is kind of satisfying to resolve problems... my motivation is to get something that should work, up and running with all the advertised features functional - for more than a few days at a time. This would help DLINK as well as me...
If you guys are not really into that, well.... Linksys here I come.
-
From what I've heard/dealt with this particular router and firmware there is no known issue that is wide-spread. I'm not trying to down play your issue as I really would like to help you though.
Hi Russell,
I'm not sure what considered as being "wide-spread" over at D-Link HQ, but I believe that with as many people here posting about the exact same issue that just maybe, statistically speaking, many other people who don't post, do not know how to post, do not care to spend time posting, return the product immediately, or who simply drop the router off of their 5th floor apartment balcony and buy an Asus router instead because it's too light to use as an effective doorstop, it may be more than just a single anomaly or two.
With that said, I really do like the feature set and design of this router and I have recommended it to many friends, family and business clients, however, most of them are complaining to me that their routers (WBR-2310) are having issues as have been mentioned in the many previous posts. This:
#1 Makes me look st*pid for recommending this router.
#2 Costs me time & money (when I have to drive out to some place to fix it)
#3 Frustrates me (and everyone else here) that we have been waiting for months (years?) to have a stable WBR-2310(amazingly loyal customer base who is even offering to help you (D-LINK) to fix D-LINKS' problems.
I think that all we want is this router to meet (not even exceed) basic (advertised?) standards:
#1 It is stable
#2 Its features work they way they should (like the Wireless).
You mention that you would like to help us. People on this post have offered to help D-Link in fixing this router. Help us by letting us HELP YOU. Give us something to work with. Maybe the source code, more beta firmware, ways to hack the firmware, something..
If you really want to help, do something. Give us contact info to someone higher up, or regular updates on issues being worked on, or give us some better diagnostics tools, or ways to load custom firmware (if possible).
People on this forum are not st*pid or d*mb (like me for recommending this router). They are very intelligent, willing and capable to HELP D-LINK with this router. Don't give us random switches to change on the router that we already have tried. Either you are just trying to waste our collective time, or the features are BROKEN on this router and NEED TO BE FIXED.
My patience with this router is down to the wire here, and I don't think I'm alone (or am I?).
I will personally work with D-Link in my own IT lab, ON MY OWN TIME, to resolve this issue FOR FREE.
Cheers
*=u
-
So yea.. I lurk alot. My company has over 12 of these models. I'm running 1.05 with no issue what-so-ever. I've heard of no complaints the past 3-4 weeks or so.
I imagine they're looking into it. I'll refrain from giving my advice since you vultures like to take it out on people trying to help you. So with that, good luck :).
I'll continue to lurk now. :)
-
So yea.. I lurk alot. My company has over 12 of these models. I'm running 1.05 with no issue what-so-ever. I've heard of no complaints the past 3-4 weeks or so.
I imagine they're looking into it. I'll refrain from giving my advice since you vultures like to take it out on people trying to help you. So with that, good luck :).
I'll continue to lurk now. :)
Hi miamifootball,
Which hardware revision do you have? Does your company have any special configuration set on them? Please let us know so that we can start working to a more permanent solution.
Cheers
-
Which hardware revision do you have?
Hey Megabyte,
Hardware revisions - Now there's a potential for some upgrades, isn't it?
By the way, like you, I feel that until recently, we'd post our grumbles and in a few months, they'd bring out a new rev of the firmware that more or less fixed it and we'd all then move onto the next bug - we'd grumble about it, in a few months.... and so on.
Now we seem to be told to downgrade, disable features we have already paid for in both time and effort to debug and got working. What is going on here?
-
72 hours in now and all systems still up.
See reply 10 above for details of "fix".
Fingers crossed!
-
72 hours in now and all systems still up.
See reply 10 above for details of "fix".
Fingers crossed!
Mine worked fine on 1.05 for 10-12 days at a time with the same setup. Then after about three times of this kind of up time, it started losing wireless every few (2-4) days.
Good luck.
-
I've found that if I use "Bart's Stuff Test" http://www.nu2.nu/bst/ over the wireless, it dies in approximately 12 hours. It seems that the more load that is placed on the wireless, the faster it dies out (with 1.05x). When I was running the test, I was using BST from one wireless laptop to another wireless laptop. Maybe it is an overheating issue?
-
Maybe it is an overheating issue?
That's an interesting thought, now isn't it? :)
Mine is a little warm on the bottom, in the center behind the LED's for wired ports 1 and 2. Not what I'd cal 'hot'!!!
I've got it on it's end, in the stand with the antenna end of it facing up.
I'll have to watch out for the next 'freeze' of wireless and see if it is hot or just a little warm or what!!!
-
Does anyone know how to set the clock time in the WBR-2310?
I keep setting it and it soon defaults back to April 2002. This may be a contributer to the loss of wireless.
After setting, etc. a nice box appears saying "System Time is now .... (the current time)" but that does not hold beyond a few hours, if that.
Tks
-
Does anyone know how to set the clock time in the WBR-2310?
From the Helpful Hints on te right side of the screen:
"Time Settings:
If you plan on using the scheduling feature of this router, then making sure the time is correct is extremely important. Either enter the time manually by clicking the Copy Your Computers Time Settings button, or use the Automatic Time Configuration option to have your router synchronize with a time server on the Internet."
I have mine set to use ntp1.dlink.com - Tools/Time and about half way down the screen, in the "Automatic Time Configuration" block, don't forget to enable it and I have it set to 1 hour, which I presume is the interval it looks to update it's internal clock...
-
Thanks bjrichus for the time answer. Since I am not doing any scheduling, I assume the router can continue to think it is back in 2002, with no ill effects on our main issue here - that is to find settings which will keep the wireless turned on.
I can now report that mine has stayed up for seven days straight with the settings used at the beginning of this thread. Now we are moving into the twilight zone where failures have been reported with all firmwares. If I can make it to two full weeks, that will be a record here.
Will report back in a week.
tafn
-
As mentioned above, with the setup I have used, repeated below, the wireless failed overnight. The remote PCs saw the signal but could not find the IP addresses which were assigned.
This made about 12 days straight of up time. Everything returned as expected when the router was powered done and then up. I have noted today's cold reboot date and will try again without changing anything. My next report will not be until about 12 days from now assuming similar behaviour
+++++++++++++++++++++++++++++++++++++++
Setup follows:
1) Reverted to Firmware 1.04 from 1.05
2) Gave DHCP reservations to my main PC (where the router is hard wired) and to the other two in the house which use wireless. Each reservation required a router reset (Save Changes) - and the reservations appeared in the list - I used IP 192.168.0.100 for the main PC and 192.168.0.101 and 192.168.0.102 for the two wireless ones plus Mac addresses.
3) Changed the DHCP lease time from 180 to 9999.
++++++++++++++++++++++++++++++++++++++++++
-
I have found that rebooting the router (rather than pulling the power plug out and then pushing it back in) does just as well.
-
Wow, I came here looking for answers about connectivity issue with my WBR-2310, Rev A1 firmware 1.05. I'm surprised that people at DLink don't think this is widespread issue when there are at least 6 recent threads on this (this one, others from AwShuxs, Megabite, San Antonio, TheJackal, jonesb), plus the many users who posted on those threads.
And no, returning the router is not an option as it was bought more then 6 months ago. It works fine except for the annoying can't connect issue.
Firmware 1.05 has been out for more then a month, didn't someone at DLink get 5 min of their time to test and try to duplicate the problem?
-
As mentioned above, with the setup I have used, repeated below, the wireless failed overnight. The remote PCs saw the signal but could not find the IP addresses which were assigned.
Hi Jonesb,
I can confirm this exact same issue with the 1.04 firmware. It seems to be more of a DHCP server issue on the router than the wireless itself. Do you receive DHCP leases when connecting via LAN? If you assign as static IP address to your wireless computer, does it connect and communicate through the router? Whenever I have setup these routers with an external DHCP server, the router seems to be very stable, except for the usual issues with 1.04.
It almost seems that the 1.04 firmware had an "automatic reboot on wireless failure" feature that was disabled in 1.05. Under heavy load, the 1.04 seems to reboot, whereas the 1.05x just seems to drop the wireless.
I'll take one of these routers apart and see if there is a heat issue and maybe stick on a heatsink+fan and see if there is an improvement. I'll post back with results.
Cheers
[Adjusted Quote]
-
I have not tried a static IP address yet, mainly because my ISP uses dynamic IPs. Probably there is no relation with router installations is there??
So I am timing again my up-time to see it it stays for 12 days as before.
The main difference I saw between 1.04 and 1.05 was that 1.05 dropped the wireless signal completely after only a few days.
For 1.04 the signal stays indefinitely but the "connectivity" or ability of the remote PCs to find the IP address drops after a week or so.
One piece of good news. I was having conflicts with the wlanapi.dll file on one remote PC which has a DLink WPA-2320 adapter card (cause was SP3 for XP trashing the DLink file). Seeing no Forum about that I earlier today posted a call for help here. However, I later Googled the problem and found two ways to fix the issue. The first (and better) was to download an updated setup and drivers from DLink - which I did and the problem went away. Sooooo SOME of DLink's downloads actually work!
If only the newer WBR2310 firmware would .........
-
Just had to power cycle the router....
The wireless stopped - after just about 8 days - and I went to one of my wired PC's to do a soft reboot, but I couldn't get to the admin screens...
Power off and then on to the router and it's all 'up' again.
The router isn't all that hot on the bottom plate....
Most bizarre.
-
I have not tried a static IP address yet, mainly because my ISP uses dynamic IPs. Probably there is no relation with router installations is there??
Sorry, I meant a static IP address on your wireless computer that is connecting to the WBR-2310, not the WAN port on the router.
Cheers
[Update]
Sorry about the poor quality pic in this link. This is the only component that gets hot:
http://www.freeimagehosting.net/image.php?79e8a75089.jpg
-
I think that both of the wireless PC have "static IP addresses. Here is a repeat of my so-far most successful settings for the WBR-2310:
1) Reverted to Firmware 1.04 from 1.05
2) Gave DHCP reservations to my main PC (where the router is) and to the other two in the house using wireless. Each reservation required a router reset (Save Changes) - and the reservations appeared in the list - I used IP 192.168.0.100 for the main PC and 192.168.0.101 and 192.168.0.102 for the two wireless ones plus Mac addresses.
3) Changed the DHCP lease time from 180 to 9999.
So does this mean that each PC uses the same IP to connect, i.e. .....101 and .....102??
-
No, you are still using the DHCP server on the WBR-2310 to assign IP addresses to your wireless computers. Therefore, if the DHCP server on the router fails, your computers will not recieve IP addresses. What I've done in this case is either:
1. Setup a different DHCP server and disable the one on the WBR-2310 or
2. Set a static ip address on the wireless computer itself (start > settings > control panel > network connections > properties on "wireless network connection" > Internet Protocol (TCP/IP), properties)
-
1. Setup a different DHCP server and disable the one on the WBR-2310 or
2. Set a static ip address on the wireless computer itself (start > settings > control panel > network connections > properties on "wireless network connection" > Internet Protocol (TCP/IP), properties)
Megabite,
That's another interesting thought - that our problems are the DHCP server in the router.
While I don't have a problem setting up a DHCP server on Unix, I've never done it on Windows (XP to be exact). So I'm going to have a play with at least one of the packages pointed to form here:
http://techrepublic.com.com/5208-11189-0.html?forumID=82&threadID=177162&messageID=1801117
I'll let you know how it all goes....
::)
-
Just above, Megabyte said:
2. Set a static ip address on the wireless computer itself (start > settings > control panel > network connections > properties on "wireless network connection" > Internet Protocol (TCP/IP), properties)
Sounds good - and I checked my PCs that this could be done.
So, what static IP do I set. The one(s) I had assigned using DHCP on the master PC with the router?
Or can I set a static IP on the master PC first and then set the other two PCs to find that one using the Megabyte solution 2.
BTW folks, other boards in these threads are reporting some new firmware from a Russian web site to solve all this mess. Personally I'd be very leery of that.
-
So, here's what happened over the weekend during my testing of the router with the cover off:
Heat:
No noticeable heat issues anywhere inside the router except for VR1 and VR2 chips. Maybe these are Voltage Regulator chips? No idea.
Runtime:
Using BST, I sent about 50GB of data over the wireless, until I noticed it failed and the client lost its IP address. Without rebooting the router, I set a static IP address onto the wireless computer and continued to run BST, but this time it was running very slowly. Before the DHCP issue, I was getting ~1.5MB/s, now I was getting about 50KB/s. The admin page was still accessible and I could see that the router had NOT yet rebooted.
After leaving it run like this overnight, I noticed this morning that BST failed again, but this time I could not access or ping the router, although the wireless still said it was connected. Under closer examination, I noticed that the "heartbeat" LED as I call it, was on solid (the LED that is directly to the right of the power LED - circle with a triangle inside). The Wireless LED was still flashing and my WAN LED was flashing oddly (~6 quick flash, then steady on ~3-4 seconds, repeat). At this point, I could only SEE the SSID, but no longer connect at all.
I've let the router in this state for further investigation when I get home from work.
It seems that there is a two stage failure here:
1. DHCP Server failure
2. Catastrophic wireless failure.
I do not believe this is a heat related issue though (which is a good thing!), so maybe it is some sort of firmware bug still. I will try the same test with the DI-624 rev D firmware (maybe even the Russian one!) and see what happens.
Cheers
-
Hello;
Try that Russian Firmware.
I did and it stopped me from pulling out the rest of my hair trying to resolve all the problems that this router gave me.
If it doesn't work for you, flash the router back to a WBR
You'll find the DI-624 firmware here:
http://ftp.dlink.ru/pub/Router/DI-624/Firmware/Rev%20D/
(save the file that ends with ".bin".)