So what is it about the K3C that makes it so no one wants to deal with it? There's a guy at OpenWRT who made some progress but there seems to be a wall they run into regarding a lack of source code distribution...?
I unfortunately purchased two of these things last year and what I thought was an excellent price, unfortunately I haven't managed to get them to work consistently for over 24 hours.
It just starts dropping connection every 5 minutes once it's been plugged in for a while...
So now I have 2 plastic bricks collecting dust I wish I could use.
I believe they can be used as APs at the very east but I'm too much of a novice to really know how to set that up.
https://forum.openwrt.org/t/phicomm-k3c-router/9864
Joined: 21 Jan 2017 Posts: 1783 Location: Illinois Moderator
Posted: Tue Apr 14, 2020 17:18 Post subject:
You're not going to find support for this router because it's a unicorn in terms of the chipsets being used in it. Intel based, so there aren't any open source drivers and code available to port it over.
Ebay time, sell both and buy a Netgear R7800.
You got hosed, genuinely sorry for that. Sometimes you have to get schooled by the hard knocks to learn about things in life... it sucks when you pay twice.
Now you know about DD-WRT and will know to look for routers that are supported to fix the craptastic support these router mfg's have...Remember, their goal is profit, so to sell you something new every few years... they have no incentive to make shit work right. _________________ FORUM RULES
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Tue Apr 14, 2020 17:43 Post subject:
It's very proprietary, and unfortunately, the only firmware that even halfway supports it is the OpenWRT community builds you linked. http://k3c.paldier.com/openwrt/ <-- last one is over a year old. I thought I had finally downloaded all the GPL tarballs from Phicomm, but I guess not. Their site will not respond, so that is pretty much a pointer to no such luck. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
and what of my question concerning ASUS's Blue Cave product? Is it likely that the firmware would be compatible?
As for the halfway support of OpenWRT, do you know to what extent the community build would work, if at all?
Lastly, the option to use the router as an AP to communicate to my primary router, how would I go about doing that?
Even though I bought them for like... Half the price they are selling them now, seems like a lot of lost value for something that's just a software problem =\
Of course if I can't use them I'll of course try and get rid of them but feels pretty shitty to be handing off my problem to someone else lol
Outside of that, we can beat around this all we want, the only result will be a padlock on this thread unless a donation or the proper homework is done. BrainSlayer perfers a device in hand so he can test prior to releasing official support. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
If you re-read my previous post in this thread (as well as the rest of the thread), there is *no* source code available for these devices to be used. So, a fullflash dump and serial boot log at the very minimum, or donated device(s) required. Also, this is not an X86 CPU, it is MIPS, which we do not have a sub-forum section to cover it correctly, but since it's Intel...
I'm willing to donate 1 of mine, just unsure of the process to do so. It seems the contact e-mail to reach before sending a device was removed...?
I'm also unsure of what I should do with the commercial invoice...? Attach it to the e-mail? Include it in the package? Tape it to the outside of the package?
What's the reason I have to take the device out of its original packaging?