expired Posted by xlnc • Sep 3, 2024
Sep 3, 2024 11:10 PM
Item 1 of 1
expired Posted by xlnc • Sep 3, 2024
Sep 3, 2024 11:10 PM
Linksys LN1301 Tri-Band AX4200 WiFi 6 Wireless Router
+ Free Shipping$20
$25
20% offAmazon
Visit AmazonGood Deal
Bad Deal
Save
Share
Top Comments
Mind you that I only have 100Mbps Spectrum internet but I do stream/direct play 4k videos from a Plex media server to several Amazon Firestick 4k devices without issue. Overall IMO you would be hard pressed to find such relatively decent hardware for so cheap; especially a Mesh network.
It wasn't all smooth at first mind you. I kept getting disconnects; especially with the streaming IP cameras. But I discovered by disabling Express Forwarding all my streaming issues went away. (CA>Connectivity>Administration>Express Forwarding)
I'm guessing that Cisco's/Linksys' proprietary Express Forwarding routing protocol was causing havoc with the IP cams streaming capabilities. Also, disabling Node Steering seemed to make things more stable as well; mesh nodes no longer disconnect from the router when Node Steering is disabled. (CA>Wi-Fi Settings>Advanced>Node Steering)
Of course, user experience can vary so feel free to experiment. if the routers are giving you problems, try turning these features off and see if it works
It's not a deal if you never receive it.
1,236 Comments
Sign up for a Slickdeals account to remove this ad.
Has anyone had success using NTFS filesystems on an external USB? I can get EXT4 and FAT32 filesystem to automatically mount, but cannot get NTFS to work, even manually. The DD-WRT v3.0-r58389 distribution includes the "ntfs3.ko" module, and can recognize that the partition has an NTFS filesytem (as seen in the /tmp/disk/sda text files), but just gives a "No such device" error when mounting. The device is there--I can read it with a "dd"--it just will not mount.
Anyone have luck with DD-WRT & USB & NTFS?
It turns out the ntfs3.ko module is not autoloading on mount like it should, so the workaround is to create a startup script that loads the module and mounts the partition(s). It basically takes two steps:
1. Enable JFFS2 support in the Adminstration section of the web gui (and then reboot the router).
2. Create a script called "/jffs/etc/config/ntfs.startup" that loads the module and mounts the partition (and then reboot the router). At a most basic level it would look something like this:
- You will have to create the subdirectories in the /jffs difrectory.
- The name of the script *has* to end with ".startup".
- The "6.6.51-rt29" directory is the kernel release number of DD-WRT. Yours may differ.
- I created a mount-point directory that would not conflict with the automount's names such as "sda1".
- The sleep is required before the mount because it takes a moment for the driver to load.
- Here I mount "sda2", but your partitions may vary. You need to know what partition(s) you want to mount.
The good news is that the drive actually achieves USB 3.0 speeds making the SMB share as fast as any NAS drive out there.
Edit: This problem is fixed in later releases (at least by r59171).
Hope that helps.
It turns out the ntfs3.ko module is not autoloading on mount like it should, so the workaround is to create a startup script that loads the module and mounts the partition(s). It basically takes two steps:
1. Enable JFFS2 support in the Adminstration section of the web gui (and then reboot the router).
2. Create a script called "/jffs/etc/config/ntfs.startup" that loads the module and mounts the partition (and then reboot the router). At a most basic level it would look something like this:
- You will have to create the subdirectories in the /jffs difrectory.
- The name of the script *has* to end with ".startup".
- The "6.6.51-rt29" directory is the kernel release number of DD-WRT. Yours may differ.
- I created a mount-point directory that would not conflict with the automount's names such as "sda1".
- The sleep is required before the mount because it takes a moment for the driver to load.
- Here I mount "sda2", but your partitions may vary. You need to know what partition(s) you want to mount.
The good news is that the drive actually achieves USB 3.0 speeds making the SMB share as fast as any NAS drive out there.
Fantastic, repped!
Sign up for a Slickdeals account to remove this ad.
I have a spare unit so on this one I first selected setup wired node then done then apply. If didn't seem to work, so I did the meshed setup again this time selecting setup wired node and setup wireless node, etc. I also made sure to disconnect from the WAN and wait for the node to get back to blue before moving. It has been several hours now, and this new child node is still showing as wired
I set the additional mesh APs up from the website/CA section.
All that said, did you try power cycling the mesh nodes to see if that reset the backhaul?
By now, I spent a lot more hours on this than the money I saved not buying a real mesh!
Sign up for a Slickdeals account to remove this ad.
Internet is full of instructions to unbrick linksys routers.
you can use any tftp server
try renaming the firmware to tortuga.img
also to flash firmware use command
run flashimg
and
run flashimg2
run both to flash both partitions.
this command was hard to find, i spend a sleepless night to find the right command.
update_both_images/flash_pri_image do not work on this.
Do you have links on the TFTP unbrick process? What TFTP client did you use?