Messages

Thanks Enzo! You my friend are an absolute legend!
I got it working, i needed to add the 'Allow Options' in advanced settings in the firewall rules.

This topic can be closed!

Hi All,

I got an issue where i don't get the IPTV working from the dutch provider TriNed.
Television is now included in the subscription at this location.
However, we are experiencing an issue: the TV decoders display an error message with code s815 when watching live TV.

We've already configured IGMP and related settings on-site, but it seems that something still isn't quite right. Could it be that specific IP addresses need to be whitelisted, or is there something else we should be aware of?

Replay and the TV guide are working fine — the issue seems to occur only with live TV.

The only thing that we got back from the provider is 'then it must be your router', yeah sure thanks for that feedback.

The settings on the interface are all on DHCP, and extra settings i made are on the lease requirements.
Send options: dhcp-class-identifier "IPTV_RG".
Request options: subnet-mask, routers, classless-routes.

The IGMP Proxy is been downloaded and is been set as:
Upstream: 0.0.0.0/1
Downstream: 192.168.1.0/24 (i have seen the tv box in the DHCP lease so thats okay).

On the firewall rules the interfaces i got the settings:
That the igptvdhcp can reach anything.
That igptvWAN can reach anything.

The gateway for the IPTV says:

IPTV_WAN_DHCP 
10.0.0.1
RTT: 6.6 ms
RTTd: 0.2 ms
Loss: 0.0 %

Do i miss anything, i have yet try to get a good log file from the activity and read it in wireshark, but maybe a sharpminded one sees my misconfiguration.

Thanks for all the answers, mates!

I figured out what was causing the strange behavior in our network.

We have Ruckus Access Points that receive their IP addresses via DHCP lease. The strange thing is, not all of our Access Points appear in the DHCP table.

So the so-called "abandoned" IP addresses are actually just Ruckus Access Points that don't show up in the DHCP lease table. After I made some changes to the DHCP settings to allow for more leases, the issue hasn't occurred again.

This topic can be closed!

Hi All,

I turned off: ignore client uid and because we have a lot of apple endpoints on the client site, i also disabled the mac adres change option on the apple endpoints.

It looks a little bit more stable right now, and i will update the routers to the latest version next week, i will keep you posted!

Hi Cookie,

Thanks for your reply, forgot to post the lease times, but they are set at:
Default: 900.
Maximum: 1800.

Weird thing is that only one device as shown in the attachment claims multiple ip adresses, so no idea why this happens.
And you can see that the lease is only active for like 1 second or so, but the router doesn't automatically remove the leases.

The only dhcpserver in the network is the OPNsense and this happens at more customers where we have an OPNsense running but not all our customers so it's a funky thingy.

Hi All,

Long time no post, but I'm back again! 😊
I'm experiencing some strange behavior on multiple routers.

One of the routers is running OPNsense 24.7.12_4-amd64, and it will be updated soon (not sure if this issue has already been fixed in a newer version).
It's always at least one device that claims a lot of DHCP adresses, sometimes there are more devices that get multiple adresses and then our DHCP-pool gets full :(.

Here's the DHCP log for one of the leases:

2025-04-16T09:57:23   Error   dhcpd   Abandoning IP address 192.168.6.100: pinged before offer   
2025-04-16T09:57:23   Debug   dhcpd   ICMP Echo reply while lease 192.168.6.100 valid.   
2025-04-16T09:57:23   Error   dhcpd   Reclaiming abandoned lease 192.168.6.100.   
2025-04-16T09:54:56   Error   dhcpd   Abandoning IP address 192.168.6.100: pinged before offer   
2025-04-16T09:54:56   Debug   dhcpd   ICMP Echo reply while lease 192.168.6.100 valid.   
2025-04-16T09:54:56   Error   dhcpd   Reclaiming abandoned lease 192.168.6.100.

Is anyone else seeing this weird behavior as well?

Hi Anakein,

What are your firewall rules voor your openVPN interface?
You need to put an rule in that says your vpn network (when following the default setup i think it is 10.8.6.*) can look in de destination network, and if you want to let it connect trough your wan you need to give it some more speficied settings.

Hi Spetrillo,

I know sometimes MacOS computers are very annoying with holding their local DNS cache, did you try to clear caches on your workstation?

And what happens when you ping from the router itself?
You can find the ping option under Interfaces -> Ping, and then don't forget to select your range in the source address.

Hi Everbody,

I'm new here and i am really happy that there is such a big community, i was looking trough the forum but couldn't find the right answer (sorry if it is somewhere and i didn't find it)..

I have the following question;

I have a wireless network lets call this 'Office' and i have the range 192.168.2.x assigned to it.
Now in that network i have 250 connected clients and well you get the point the pool is full, but i have more clients that need to connect to the same 'Office' wireless network. Is there a possibility that you hook up a second DHCP pool so that when you connect trough wireless network Office and pool 192.168.2.x is full you get an address in the 192.168.3.x range?

I hope someone has the answer:)!

Thanks in advance!