No, I meant I can't remeber if telnet is enabled cause SSH is
You don't need to search for U-boot in GPL source or anywhere else as its in the root directory of the filesystem
Code:
root@Linksys00489:~# ls /
bin lib proc sbin uboot209.bin www
dev mnt rom sys usr
etc overlay root tmp var
root@Linksys00489:~#
Yeah, i wonder if u can choose which devices can use the vpn client,
I like dd-wrt for that.
True same car, same engine, but perhaps status post dyno for max power?
you're not alone! i could really use that kind of discretion from within the router. netflix chooses to deny access when vpn is used for my smart tv. so now, i do it on networked 'puters - when i can remember. _________________ asus rt-ac86u stock: 3.0.0.4.384_45149
wrt3200acm: r34578 {sunset}
"why nibble when u can take a byte."
No, I meant I can't remeber if telnet is enabled cause SSH is
You don't need to search for U-boot in GPL source or anywhere else as its in the root directory of the filesystem
Code:
root@Linksys00489:~# ls /
bin lib proc sbin uboot209.bin www
dev mnt rom sys usr
etc overlay root tmp var
root@Linksys00489:~#
Official updates are ok without modifying the U-boot.
But if you want to try it then after the firmware boots login via SSH or preferably via serial to openwrt with root user and issue:
Code:
mtd write /uboot209.bin u-boot
reboot
Then in U-boot console issue:
Code:
resetenv
reset
Login to U-boot console once more to enable serial output:
There is no need to switch to WRT32X bootloader You are not missing out on anything. _________________ Main HW:
Netgear R7800 @ DD-DWRT r50274 (Router+AP)
- Wireguard client
over the firmware I provided and you will get future updates automatically. _________________ Main HW:
Netgear R7800 @ DD-DWRT r50274 (Router+AP)
- Wireguard client
The geniuses out there are really impressive. Now patiently waiting for a solution that does not involve serial.
I don't think you will get one. You can't open the front door without first getting through the backdoor.
What are geniuses for ...?
Flattery is nice and inteliboy and aprilthemoo, for sure, are skilled craftsmen (and women).
But the nature of what is being change while in the u-boot env, can only be changed there. Firmware flashing just flashes into the defined partitions spaces as defined in the env. So without the groundwork being laid (work in u-boot), you can't just flash the firmware on top. Square peg in a round hole.
I assume the autoupdates wont keel over?