yes all available... you can search in luci > system > software (or similar)
note: they are probably all from the 'packages' repo (except maybe tproxy)... for which I use the official path/url (aka they are not really specific to any repo of mine)
1 Like
That's good, so just need iptables-mod-tproxy to make sure openclash run well. Do you any reference or feeds for those packages?
when you install them it shows you the repo it downloads from...
there is also pkgdata... which is of limited use...
openwrt-pkgdataget.sh ruby
1 Like
Since tproxy shown in tproxy pkgdata it's not supported latest rc release?
I don't know if this solution work for me Force install
no it(pkgdata hence limited use) just shows the last known stable... ( 19.07.x )...
it will be available in 21.02 and master(snapshot/us) as can be seen when you search for it in opkg/software...
1 Like
Thank you for the explanation.
1 Like
if you are on an old build you may need to do the above... as most of the old core|base|luci custom repos were removed from github due to the openssl_1.1.1l bug/bump...
all that were left up (@github) are;
r17311-7057e05485 #bug
r17390-9baca41064 #bug
r17443-90e167abaa #new
i got problem when placing tmux in rc.local via luCI
tmux new-session -d -s mysession && tmux send-keys -t mysession "/usr/bin/binary --log-level panic -c /etc/program/config.json client
"
it's says duplicate session: mysession. and I'm trying to run 4 tmux sessions.
solved
i had to remove from rc.local(luCI) then place it in rc.local through terminal
1 Like
Hey there wulfy, decided to start clean from current build and currently getting myself back up.
I was wondering, what was the filesystem used for the mSD Card partitions? I'm trying to mount the backup but seem to be hitting a snag if the form of:
sudo mount -v -o offset=802816 -t squashfs /home/toasterdev/Rpi2.img /mnt/rpi
mount: /mnt/rpi: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Is there anything else I might be missing?
1 Like
- partition 1 = boot= vfat
- partition 2 = rootfs = ext4
rpi4.64-snapshot-26719-3.5.7-2-r17443-ext4-fac.img.gz 2021-08-28 09:01 78M
rpi4.64-snapshot-26719-3.5.7-2-r17443-ext4-sys.img.gz 2021-08-28 09:02 78
### [root@dca632 /usbstick 43°]# block info
/dev/mmcblk0p1: UUID="E448-F3FE" LABEL="boot" VERSION="FAT16" MOUNT="/boot" TYPE="vfat"
/dev/mmcblk0p2: UUID="ff313567-e9f1-5a5d-9895-3ba130b4a864" LABEL="rootfs" VERSION="1.0" MOUNT="/" TYPE="ext4"
1 Like
Thanks!
Just managed to mount through using the sector start and multiplying by 512, ended with the following command in case somebody needs it:
sudo mkdir /mnt/rpi
sudo mount -v -o offset=411041792 -t ext4 /home/toasterdev/Rpi2.img /mnt/rpi
1 Like
i generally use;
gunzip factory.img.gz
losetup -P -f factory.img
mount /dev/loop0p2 /somewhere
...
umount /somewhere
losetup -D
1 Like
Well, that looks nicer.
I'll keep it in my notes then, thanks!
1 Like
fyi... new (general openwrt) package has been created...
v2rayA
[root@dca632 /usbstick 43°]# opkg list | grep -i v2r
v2rayA - 1.5.1-1 - v2rayA is a V2Ray Linux client supporting global transparent proxy, compatible with SS, SSR, Trojan(trojan-go), PingTunnel protocols.
if more than 3 build users start using this... i'll look at building it in(still massive 23M+!) or making a separate variant... (if needed for firstboot and all the other stuff needed is available easily)
1 Like
Well, I tried v2rayA couples of days ago on other firmware bases on sulingGG, It's worth trying it. Since v2rayA much easier to install.
Check this v2rayA openwrt
But since new released update/latest already included WebUI in binary file so you may make adjustments for it
owh i understood now, you mean it's already published to the official OpenWrt, right?
1 Like
@anon50098793 sir i just tried via opkg install v2rayA but it's seem the service doesn't start properly
1 Like
wish I could help more but I don't know the service...
usually it's a mix of setting up the /etc/config/v2raya config file correct and checking logread to see what else it wants... i.e.
uci set v2raya.config.enabled='1'
uci set v2raya.config.verbose='1'
uci commit v2raya
/etc/init.d/v2raya restart
#logread #check for key errors
do you success until accessing web ui 192.168.1.1:2017 ?
debug-v2raya-startup-mgmt-port
hmmmm.... just enabling starts with 443 no 2017...
v2raya 14219 root 3u IPv6 1219504 0t0 TCP WANIPv6REMOVED:443 (ESTABLISHED)
v2raya 14219 root 9u IPv4 1219892 0t0 TCP WANIPv4REMOVED:53118->13.236.14.80:443 (ESTABLISHED)
cmdline shows 2017...
14219 root 4815m S /usr/bin/v2raya --address 0.0.0.0:2017 --config /etc/v2raya --pluginlistenport 32346
may need to force it to use a specific lan address... ( or compare with other working command lines )
yeah... running it manually with a specific ip works
/usr/bin/v2raya --address 10.2.3.1:2017 --config /etc/v2raya --pluginlistenport 32346 &
so you have to change this line in /etc/config/v2raya
option address '0.0.0.0:2017'
and put in your proper lanip
(better make a separate thread if any other issues)
that's work! i thought i need to edit in init.d v2raya since the last time I did it manually, and now it has its own config. thank you. sorry for oot, it really needs to open new thread.
1 Like