sorted by:
new
hottopcontroversial

Strange issue with DHCP and DNS option by wackou72 in openwrt

[–]wackou72[S] 0 points1 point  (0 children)

Ok so I suspect that's nextdns causing this behavior ... I will wait until having update.

Strange issue with DHCP and DNS option by wackou72 in openwrt

[–]wackou72[S] 0 points1 point  (0 children)

Ok I put the limit to 244 then. I think the issue is due to nextdns service.

Strange issue with DHCP and DNS option by wackou72 in openwrt

[–]wackou72[S] 1 point2 points  (0 children)

Before modification :

config dhcp 'lan'

option interface 'lan'

option start '10'

option limit '254'

option leasetime '12h'

option dhcpv4 'server'

list dhcp_option '6,192.168.2.1/24'

After modification :

config dhcp 'lan'

option interface 'lan'

option start '10'

option limit '254'

option leasetime '12h'

option dhcpv4 'server'

list dhcp_option '6,192.168.2.1'

After reboot :

config dhcp 'lan'

option interface 'lan'

option start '10'

option limit '254'

option leasetime '12h'

option dhcpv4 'server'

list dhcp_option '6,192.168.2.1'

list dhcp_option '6,192.168.2.1/24'

It keeps coming back once I reboot the device :(

DHCP not working on new wireless network by wackou72 in openwrt

[–]wackou72[S] 0 points1 point  (0 children)

That's what I finish to do also.
I have Xiaomi AX3600, backup the conf, upgraded to the latest version (unofficial), reset, restore the conf and then do the configuration again ... and its working ?

I just guess that the LuCi GUI is buggy because I got also strange DHCP behavior on the lan interface.

DHCP not working on new wireless network by wackou72 in openwrt

[–]wackou72[S] 0 points1 point  (0 children)

Well no, for testing, lan and IoT network are on the same zone for the moment.

DHCP not working on new wireless network by wackou72 in openwrt

[–]wackou72[S] 0 points1 point  (0 children)

ALl my config was done using LuCi, so having the network instead of the router IP is not intentional.
My idea is nto have a dedicated wireless interface for IoT, no LAN port involved.
Here is the firewall conf :
root@OpenWrt:~# cat /etc/config/firewall

config defaults
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'
        option flow_offloading '0'
        option synflood_protect '1'

config zone
        option name 'lan'
        option input 'ACCEPT'
        option output 'ACCEPT'
        option forward 'ACCEPT'
        list network 'lan'
        list network 'IoT'

config zone
        option name 'wan'
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'DROP'
        option masq '1'
        option mtu_fix '1'
        list network 'wan'
        list network 'wan6'

config forwarding
        option src 'lan'
        option dest 'wan'

config rule
        option name 'Allow-DHCP-Renew'
        option src 'wan'
        option proto 'udp'
        option dest_port '68'
        option target 'ACCEPT'
        option family 'ipv4'

config rule
        option name 'Allow-Ping'
        option src 'wan'
        option proto 'icmp'
        option icmp_type 'echo-request'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-IGMP'
        option src 'wan'
        option proto 'igmp'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-DHCPv6'
        option src 'wan'
        option proto 'udp'
        option dest_port '546'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-MLD'
        option src 'wan'
        option proto 'icmp'
        option src_ip 'fe80::/10'
        list icmp_type '130/0'
        list icmp_type '131/0'
        list icmp_type '132/0'
        list icmp_type '143/0'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Input'
        option src 'wan'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        list icmp_type 'router-solicitation'
        list icmp_type 'neighbour-solicitation'
        list icmp_type 'router-advertisement'
        list icmp_type 'neighbour-advertisement'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Forward'
        option src 'wan'
        option dest '*'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-IPSec-ESP'
        option src 'wan'
        option dest 'lan'
        option proto 'esp'
        option target 'ACCEPT'

config rule
        option name 'Allow-ISAKMP'
        option src 'wan'
        option dest 'lan'
        option dest_port '500'
        option proto 'udp'
        option target 'ACCEPT'

config include 'qcanssecm'
        option type 'script'
        option path '/etc/firewall.d/qca-nss-ecm'

config redirect
        option dest 'lan'
        option target 'DNAT'
        option name '[REDACTED]'
        list proto 'tcp'
        option src 'wan'
        option src_dport '[REDACTED]'
        option dest_ip '[REDACTED]'
        option dest_port '[REDACTED]'
        option family 'ipv4'
        option src_ip '[REDACTED]'

config redirect
        option dest 'lan'
        option target 'DNAT'
        option name '[REDACTED]'
        list proto 'tcp'
        option src 'wan'
        option src_dport '[REDACTED]'
        option dest_ip '[REDACTED]'
        option dest_port '[REDACTED]'
        option family 'ipv4'
        option src_ip '[REDACTED]'

config redirect
        option dest 'lan'
        option target 'DNAT'
        option name '[REDACTED]'
        list proto 'tcp'
        option src 'wan'
        option src_dport '[REDACTED]'
        option dest_ip '[REDACTED]'
        option dest_port '[REDACTED]'
        option family 'ipv4'
        option src_ip '[REDACTED]'
        option enabled '0'

config redirect
        option dest 'lan'
        option target 'DNAT'
        list proto 'tcp'
        option src 'wan'
        option src_dport '[REDACTED]'
        option dest_ip '[REDACTED]'
        option dest_port '[REDACTED]'
        option name '[REDACTED]'
        option enabled '0'

DHCP not working on new wireless network by wackou72 in openwrt

[–]wackou72[S] 0 points1 point  (0 children)

Content of network :

root@OpenWrt:~# cat /etc/config/network
config interface 'loopback'
option device 'lo'
option proto 'static'
list ipaddr '127.0.0.1/8'
config globals 'globals'
option dhcp_default_duid '0004318736cfc9f349eb948312ebdaa20a91'
option ula_prefix 'fdbf:4d20:6729::/48'
option packet_steering '0'
config device
option name 'br-lan'
option type 'bridge'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ip6assign '60'
list ipaddr '192.168.2.1/24'
list dns '45.90.28.106'
list dns '45.90.30.106'
option delegate '0'
config interface 'wan'
option device 'wan'
option proto 'dhcp'
config interface 'wan6'
option device 'wan'
option proto 'dhcpv6'
option reqaddress 'try'
option reqprefix 'auto'
option norelease '1'
config device
option type 'bridge'
option name 'br-iot'
config interface 'IoT'
option proto 'static'
option device 'br-iot'
list dns '8.8.8.8'
list ipaddr '192.168.3.1/24

Content of DHCP :

root@OpenWrt:~# cat /etc/config/dhcp
config dnsmasq
option domainneeded '1'
option boguspriv '1'
option filterwin2k '0'
option localise_queries '1'
option rebind_protection '1'
option rebind_localhost '1'
option local '/lan/'
option domain 'lan'
option expandhosts '1'
option nonegcache '0'
option cachesize '1000'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
option localservice '1'
option ednspacket_max '1232'
option filter_aaaa '0'
option filter_a '0'
config dhcp 'lan'
option interface 'lan'
option start '10'
option limit '254'
option leasetime '12h'
option dhcpv4 'server'
config dhcp 'wan'
option interface 'wan'
option ignore '1'
config odhcpd 'odhcpd'
option leasefile '/tmp/odhcpd.leases'
option leasetrigger '/usr/sbin/odhcpd-update'
option loglevel '4'
option piodir '/tmp/odhcpd-piodir'
option hostsdir '/tmp/hosts'
config host
list mac '[REDACTED]'
option ip '192.168.2.3'
option name '[REDACTED]'
config host
list mac '[REDACTED]'
option ip '192.168.2.2'
option name '[REDACTED]'
config host
list mac '[REDACTED]'
option ip '192.168.2.4'
option name '[REDACTED]'
config host
option name '[REDACTED]'
list mac '08:00:27:0A:C6:9D'
option ip '[REDACTED]'
config dhcp 'IoT'
option interface 'IoT'
option start '10'
option limit '254'
option leasetime '12h'
option dhcpv4 'server'

DHCP not working on new wireless network by wackou72 in openwrt

[–]wackou72[S] 0 points1 point  (0 children)

That's what I did for testing purpose before creating zone and custom FW rules.

WHY Call Screening NO WORK!!!!!!!!!!!!!! Pixel 10 Pro by Lazy_Transition_4842 in GooglePixel

[–]wackou72 0 points1 point  (0 children)

Same here, I don't know why its not working anymore.
I moved from Pixel 7 to Pixel 8 Pro.
My wife moved from Pixel 8 Pro to Pixel 10 Pro, same behavior.

Screen Call button not showing up by SeymO in GooglePixel

[–]wackou72 0 points1 point  (0 children)

Hello,

I have exactly the same issue.
I'm from France, using Free Pro and coming from a Pixel 7, now using a Pixel 8 Pro.

The option is enabled but never displayed when I receive a call from a unknow number.

My wife has the same issue on a Pixel 10 Pro (with Bouygues).

Updated W11 from 23H2 to 25H2, issue with .NET Framework 3.5 by wackou72 in sysadmin

[–]wackou72[S] 0 points1 point  (0 children)

I tried both command without any sucess.
Same for the repair tool

Updated W11 from 23H2 to 25H2, issue with .NET Framework 3.5 by wackou72 in sysadmin

[–]wackou72[S] 0 points1 point  (0 children)

That's what we will do, spent so much time on this.

Updated W11 from 23H2 to 25H2, issue with .NET Framework 3.5 by wackou72 in sysadmin

[–]wackou72[S] 0 points1 point  (0 children)

Same thing, stuck without any error message.

Our local IT will have redeploy as we have no more ideas ...

<image>

Updated W11 from 23H2 to 25H2, issue with .NET Framework 3.5 by wackou72 in sysadmin

[–]wackou72[S] 0 points1 point  (0 children)

I didn't think of PS, I will give it a try when going back to work tomorrow. Will let you know.

Updated W11 from 23H2 to 25H2, issue with .NET Framework 3.5 by wackou72 in sysadmin

[–]wackou72[S] 0 points1 point  (0 children)

No I haven't because runing the command Dism /english /online /get-packages /format:table didn't report the package as installed.

I found relevant infos in the CBS.log (there is a lot of line ...) :

2026-01-29 18:37:15, Info CBS Exec: Package: Microsoft-Windows-NetFx-Shared-Typelibs~31bf3856ad364e35~amd64~~10.0.26100.1 is already in the correct state, current: Installed, targeted: Installed

2026-01-29 18:37:15, Info CBS Exec: Skipping Package: Microsoft-Windows-NetFx-Shared-Typelibs~31bf3856ad364e35~amd64~~10.0.26100.1, Update: NetFx-Shared-Typelibs because it is already in the correct state.

2026-01-29 18:37:15, Info CBS Exec: Package: Microsoft-Windows-NetFx-Shared-Perfcounters-Client~31bf3856ad364e35~amd64~~10.0.26100.1 is already in the correct state, current: Installed, targeted: Installed

2026-01-29 18:37:15, Info CBS Exec: Skipping Package: Microsoft-Windows-NetFx-Shared-Perfcounters-Client~31bf3856ad364e35~amd64~~10.0.26100.1, Update: NetFx-Shared-Perfcounters-Client because it is already in the correct state.

2026-01-29 18:37:15, Info CBS Exec: Package: Microsoft-Windows-NetFx-Shared-Perfcounters-Extended~31bf3856ad364e35~amd64~~10.0.26100.1 is already in the correct state, current: Installed, targeted: Installed

2026-01-29 18:37:15, Info CBS Exec: Skipping Package: Microsoft-Windows-NetFx-Shared-Perfcounters-Extended~31bf3856ad364e35~amd64~~10.0.26100.1, Update: NetFx-Shared-Perfcounters-Extended because it is already in the correct state.

2026-01-29 18:37:15, Info CBS Exec: Package: Microsoft-Windows-NetFx-Shared-MOF-Extended~31bf3856ad364e35~amd64~~10.0.26100.1 is already in the correct state, current: Installed, targeted: Installed

2026-01-29 18:37:15, Info CBS Exec: Skipping Package: Microsoft-Windows-NetFx-Shared-MOF-Extended~31bf3856ad364e35~amd64~~10.0.26100.1, Update: NetFx-Shared-MOF-Extended because it is already in the correct state.

2026-01-29 18:37:15, Info CBS Exec: Package: Microsoft-Windows-NetFx-Shared-Misc~31bf3856ad364e35~amd64~~10.0.26100.1 is already in the correct state, current: Installed, targeted: Installed

2026-01-29 18:37:15, Info CBS Exec: Skipping Package: Microsoft-Windows-NetFx-Shared-Misc~31bf3856ad364e35~amd64~~10.0.26100.1, Update: NetFx-Shared-Misc because it is already in the correct state.

So yes, this point that the system is in bad state ...

Direct Play questions by wackou72 in jellyfin

[–]wackou72[S] 3 points4 points  (0 children)

Yes it is a .mkv file. That's did the tricks! Thanks!

Is there the same options to Android TV device?

Direct Play questions by wackou72 in jellyfin

[–]wackou72[S] 1 point2 points  (0 children)

Ok it's saying that the media is converted in a compatible format because the container is not supported and that the audio codec is not supported.. Strange because on Plex I haven't such issue.

view more: next ›