Agreed. Zero problem with the ue300’s
Using UE300 here too, works great. Has the popular RTL8153 chipset, so driver is kmod-usb-net-rtl8152 as is we describe on the table of hardware page.
Poke for life
2 Likes
Some really nice commits for Rpi4 added to master branch this week. Kernel 5.15 (great since that's what RPi OS 64-bit uses too), new eeprom, improved scheduler, etc. Wulfy's new build he snuck out hopefully includes all that too, going to install it in the next couple days.
4 Likes
Quoted from github:
############################## 7.1.13 - k5.15test - r19686
kernel was updated to 5.15 test build, i have to tested this yet so
wait for a week / few days if you don't have dd backups or general
confidence based on other sources...
-uploaded as current but i'm aware of a few mostly minimal? places
where my/our logix does not accomodate it... for this week its mostly
for any brave souls whom are eager to test the new kernel and
investigate core function / quirks / performance etc.
a) on building kmod pwm was not available
b) hmmm... userspace seems alot more snappy
c) tailroom bug (rare) still present
d) um... my additional usb mount is spitting errors on (last build)
upgrade... looks like some sort of semi-newish brute ps kill
/ term... and probably not so big a deal for most?
... just noting here for a time reference...
It's working ok in my case.
1 Like
Hi, did you tests mwan3 ? Mine wasn't working properly.
hi, i use mwan3 in backup mode and i have no problems
my mwan3
config globals 'globals'
option mmx_mask '0x3F00'
config member 'wan_m1_w3'
option metric '1'
option weight '3'
option interface 'WAN'
config member 'wan_m2_w3'
option metric '2'
option weight '3'
option interface 'WAN'
config member 'wanb_m1_w2'
option metric '1'
option weight '2'
option interface 'WANB'
config member 'wanb_m2_w2'
option metric '2'
option weight '2'
option interface 'WANB'
config policy 'wan_only'
list use_member 'wan_m1_w3'
option last_resort 'unreachable'
config policy 'wanb_only'
list use_member 'wanb_m1_w2'
option last_resort 'unreachable'
config policy 'balanced'
list use_member 'wan_m1_w3'
list use_member 'wanb_m1_w2'
option last_resort 'unreachable'
config policy 'wan_wanb'
list use_member 'wan_m1_w3'
list use_member 'wanb_m2_w2'
option last_resort 'unreachable'
config policy 'wanb_wan'
list use_member 'wan_m2_w3'
list use_member 'wanb_m1_w2'
option last_resort 'unreachable'
config rule 'default_rule_v4'
option dest_ip '0.0.0.0/0'
option family 'ipv4'
option proto 'all'
option sticky '0'
option use_policy 'wan_wanb'
config interface 'WAN'
option enabled '1'
option initial_state 'online'
option family 'ipv4'
list track_ip '8.8.8.8'
option track_method 'ping'
option reliability '1'
option count '1'
option size '56'
option max_ttl '60'
option timeout '4'
option interval '10'
option failure_interval '5'
option recovery_interval '5'
option down '5'
option up '5'
config interface 'WANB'
option initial_state 'online'
option family 'ipv4'
list track_ip '8.8.8.8'
option track_method 'ping'
option reliability '1'
option count '1'
option size '56'
option max_ttl '60'
option timeout '4'
option failure_interval '5'
option recovery_interval '5'
option down '5'
option up '5'
option interval '300'
option enabled '1'
well setting 2 wan, with weight 50-50 and loadbalance. main wan1 work getting traffic but wan2 not traffic activity. but if wan1 stopped wan2 works normallya, load-balance become fail-over ?
Yes, if wanA is down the traffic is redirect to wanB, fail-over is ok
Can you tests with load balance sir?
I have tests with load balance and fail-over is ok.
thanks you. mine aren't works. i can try flash again.
Just flashed to latest one. And works fine now.
1 Like
Poke for alive
2 Likes
Had to return to 5.7.50-3-r19602.
In 7.1.13-3-r19686 I could not edit firewall traffic rules with Luci.
can anyone give me link to his latest build or the last build.
Hi, find everything at the top of the page
1 Like
I am having a strange issue, after power failure wan pppoe gets some private IP in the 10.... range and I have to restart wan interface or reboot pi couple of times for it to get public IP.
Something wrong from ISP side? or issue with pi4?
is this still getting update from wulfy?
They've always been posted here:
https://rpi4.wulfy23.info/builds/
Watch out with the recent 22.03 based builds though, they are quite buggy, which is the reason why a newer rc hasn't been released since rc1. The OpenWrt devs have a lot of fixes hitting master so it looks promising.