Project

General

Profile

Bug #5003

DVB inputs - local bind IP adress not recognized

Added by D. W. over 6 years ago. Updated over 6 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
DVB
Target version:
-
Start date:
2018-03-14
Due date:
% Done:

0%

Estimated time:
Found in version:
4.3-1155~gef96199
Affected Versions:

Description

Hi.

I use 2 DVB-S2 Sat-IP server with 4 tuners each as DVB inputs.
TVHeadend is running on my Netgear RN204.

This NAS has 2 NIC ports:
1. Port (x.x.x.1) is configured for all NAS actions (Sharing etc...) and Kodi HTSP access to TVHeadend.
2. Port (x.x.x.2) is just for the TVHeadend connection to the SAT-IP servers using UDP.

TVHeadend priority settings are:

Streaming live TV from Input 1.
Record everything from Input 2.

Both DVB inputs are bound to Port 2 (Local bind IP-adress: x.x.x.2)

Live TV via HTSP is requested by TVHeadend correctly from the SAT-IP server via Port 2.
Recordings are not correctly requested using Port 1.

So the second DVB input device seems to be bound to the wrong IP.

Maybe there's something to fix ?

Thanks, solut.

History

#1

Updated by Jaroslav Kysela over 6 years ago

The explanation is not very clear to me. I don't understand what you're trying to do. Note that there's '-b or --bindaddr' argument for the tvheadend process (see 'tvheadend --help') for HTTP/HTSP clients.

#2

Updated by D. W. over 6 years ago

There is an option "Local bind ip adress" for the DVB-Inputs.
I think this is to be used to define which local availlable ethernet adapter (IP) is used for communicating with the (in my case) SAT-IP server.

I just want to use a specific ethernet adapter for UDP communication only.
The other TCP stuff shall be on another ethernet adapter.

So I configured the adress "x.x.x.2" as the local bind ip adress for both DVB Inputs.
But on input 2 this is not regocnized, it uses the local ethernet adapter with IP "x.x.x.1" during recordings.

#3

Updated by Jaroslav Kysela over 6 years ago

I doubt that this does not work only for one satip client. You can configure bind address per server or per tuner (input):

$ grep satip_frontend_bindaddr src/input/mpegts/satip/satip_frontend.c
satip_frontend_bindaddr( satip_frontend_t *lfe )
                             satip_frontend_bindaddr(lfe));
                        satip_frontend_bindaddr(lfe), lfe->sf_udp_rtp_port,
                               satip_frontend_bindaddr(lfe));
#4

Updated by D. W. over 6 years ago

I'm confused, I checked the traffic with nload and all data was running over x.x.x.1.
Checking with ss dst x.x.x.1 gave no sockets, all sockets correctly bound on x.x.x.2.
After reinstalling nload it's showing the dvb traffic is going all over x.x.x.2.

Maybe my problems have been related to an older nic bonding configuration...

I'm sorry for wasting your time - you can close the ticket.

#5

Updated by Jaroslav Kysela over 6 years ago

  • Status changed from New to Invalid

Also available in: Atom PDF