Routers and Linux friendliness throughout firmware upgrades.
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Routers and Linux friendliness throughout firmware upgrades.
I have a D0-Link DDIR-825 router. all works fine in Win XP, but not in Fedora, 32 or 64 bit.
Sometimes I can access the internet, but not my wired Gb. network and DIR-343 and DIR-323 NAS boxes.
When I bought this a few years abck, all was fine, however, more recently, not so. I am thinking a firmware upgrade may have messed up the Linux friendliness.
This is not related to remote firmware access or SSH. I am only trying to get my Linux machines to see my home network as do my windows machines, without having to spend a lot of time over it. In various blogs and on street comments I get echoes of dissatisfaction with D-Link's quality of support more recently.
Personally I also feel it has degenerated somewhat.
Since I believe there are many of this model out there, it would be nice to see some linux-related support for this problem.
This router also has a shareport. I wonder if Fedora has a shareport manager?
Shareport is not known to be the nicest or most stable of connections, but it can sometimes be convenient for jobs that are not so "mission critical."
In Win XP, I can support multiple devices through a downline powered hub, except that the cable I use from the shareport has been modified to insert a diode in the +5V. line to block the hub from backing power into the router when the router needs to be rebooted.
This works well, but you have to do your own hardware mod. I use the same with USB on motherboards for the comparable reason, and that also works well.
If I eventually have to replace the router, I would prefer to buy from a local Montreal Bricks and mortar store, rather than ordering in which adds multiple inconveniences.
Sometimes I can access the internet, but not my wired Gb. network and DIR-343 and DIR-323 NAS boxes.
Network configuration and conditions can be checked just like service configuration and system, service and router logs.
So what do you check when a connection goes bad and what does it show?
Quote:
Originally Posted by Bruce from Canada
This router also has a shareport. I wonder if Fedora has a shareport manager?
Your question should be if the protocol D-Link uses is proprietary or not. And from what I've read Shareport isn't even usable with Teh othEr oS unless you install their software...
* BTW it's better to split disparate questions off into separate threads. Exposure, efficiency and such.
Network configuration and conditions can be checked just like service configuration and system, service and router logs.
So what do you check when a connection goes bad and what does it show?
==============================================
Since you are a moderator, are you able to split this one and sentd the shareport issue to a new thread. I think you will be better able than I to choose a name and tags that will be better understood by most for that thread. Please R.S.V.P. if you are able too do so, with the verbatim name you have chosen.
I have the shareport working on 2 machines in WinXP. On one, I have used D-link's software, on the other, I have used SX Virtual Link. Both do the same thing, only the names and cosmetics vary.
When I have the time, I will search for a Linux version, but whether what I will find will be totally adherent to open source licensing standards or not remains to be seen.
If I find this feature has too many licensing encumberments, I would be inclined to build a hardware work-around from scratch. This will be a bit less convenient, but will remove any licensing issues.
Re router:
Much of the concern here is convenience related. Nobody wants to lose a lot of time with issues that feel like "manipulated convenience". This appears to be enough for some to treat the hardware as a "brick", inferring a black mark on the manufacturer's reputation and corporate image.
Currently I have attached a second router of a different make to the first one with a reverse wired cable. This will access the internet, but I have not had time to see if it will deal with the network and its Linux peers.
This was a router I had in stock and not being used. If this works, I will consider purchasing another high end router of a different brand from a retailer where I can return it no questions asked for about 15 days. In less than that I should be able to install it in place of the second router and see if it works or not. If not, little risked, especially with the consumer protection laws in Quebec. If so, I will keep the router once it has passed a second test installed as the primary router. Then the D-Link will be switched into second place art the end of a reverse wired connection to its WAN side.
It would be helpful to know/see the topology of your home network. From that, it would be easier to know what parts of the router have issues. Personally, I'd focus on the open standards aspect of networking and get that much working first. It could be a configuration issue. Firmware updates may be re-interpreting configuration settings in different ways, or just changed some back to defaults.
Another option is to reload the router with one of the Linux based router class distributions, such DD-WRT.
Recently I have purchased a variety of small and larger hardware with the intent to use them with Linux. In a number of cases I have, as a consumer, been disappointed. Too many of these devices do not come with(IMHO) Linux-fair compatibility-interoperability. I feel this is just too close to a monopoly from the "paid software and hardware market."
Where I live there is a short term government-imposed guarantee. For such items, I purchase from local storefront suppliers who are subject to this legislative protection. I then test the product within the few days, and if it dopes not work right off or very close, I return it, having noted the results of my investigation in my own independent support files.
Over time one gets some idea of what is truly "Linux-fair" and what is not. IMHO I am payiong the purchase, I feel I have a right as a consumer to a fair marketplace.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.