Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#11166 closed Bug Report - General (Invalid)

Still problems with mythfrontend binding only to localhost

Reported by: dag@… Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: 0.25.2
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Still something fishy here: I have a setting where the backend address is definitely set to the external IP of that backend. Still my frontend insists on listening only to 127.0.0.1.

Proof from the log:

2012-10-10 12:14:27.648154 I  Loading sv translation for module mythzoneminder
2012-10-10 12:14:27.652469 I  Listening on TCP 127.0.0.1:6546
2012-10-10 12:14:27.815941 N  Found mainmenu.xml for theme 'Readability'
2012-10-10 12:14:28.147370 I  MythCoreContext: Connecting to backend server: 194.110.87.211:6543 (try 1 of 1)
2012-10-10 12:14:28.158288 I  Using protocol version 72

I do have a slightly "strange" backend with an alias for a non-proxied net, and the backend only listened to the alias+localhost (separate bug I guess) if I left the IP address of himself empty: My interfaces on the backend are:

  • eth0 194.110.87.211
  • eth0:1 10.0.0.10
  • lo 127.0.0.1

Interfaces on frontend the usual:

  • eth0 194.110.87.212
  • l0 127.0.0.1

Tell me if I can give more useful info!

Change History (2)

comment:1 Changed 7 years ago by Raymond Wagner

Resolution: Invalid
Status: newclosed

The unconfigured behavior is for mythfrontend to listen on all available addresses, however you ran mythtv-setup on the frontend machine, applying the default configuration of 127.0.0.1. Run mythtv-setup again, on the machine that your frontend runs on, and either blank that setting, or give it your eth0 address.

comment:2 Changed 7 years ago by dag@…

Thanks! Didn't realize that you had to run mythtv-setup on the frontend in question, but tried to run it on the backend. Clearing it out did NOT work though, still insisted on listening to localhost only. Setting the name of the frontend did not work either. Had to set the IP of eth0 explicitly, which is not so good as this is getting the address through DHCP...

Note: See TracTickets for help on using tickets.