<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000001">
<br>
<div class="moz-cite-prefix">On 3/20/2013 9:14 AM, Greg Woods wrote:<br>
</div>
<blockquote
cite="mid:1363788852.2152.6.camel@anathem.gregandeva.net"
type="cite">
<pre wrap="">On Wed, 2013-03-20 at 07:59 -0500, jzigpublic wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
On 3/19/2013 7:42 PM, Greg Woods wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I am running Fedora 18 on a dual-core Pentium 4 (i386 distro) if this
matters.
The problem is that the UDP driver does not seem to work. I have
followed the instructions at
<a class="moz-txt-link-freetext" href="http://www.mythtv.org/wiki/Hdhomerun#Setting_up_IR_Forwarding">http://www.mythtv.org/wiki/Hdhomerun#Setting_up_IR_Forwarding</a>
The HDHomerun does appear to be sending packets to port 5000 on the
target system, as confirmed by tcpdump.
If I start "lircd -H udp -d 5000" on the target system as instructed, it
appears to start, but it is not actually listening on the network.
</pre>
</blockquote>
</blockquote>
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">Just to confirm that the HDHR is still sending packets you can try
this:
At the console as root with lirc not running start mode2 with this
command:
mode2 -H udp -d 5000
</pre>
</blockquote>
<pre wrap="">
Thanks for the tip on mode2. At first this did not work. Then I took a
more careful look at the tcpdump output and realized that the 5000 I was
seeing was the source port on the HDHR. It was sending packets to port
4500 on the target system (lord knows what I was thinking when I set
this up). So I corrected the port number, and now mode2 does see the
button presses. So I fired up "lircd -H udp -d 5000", and now I can run
"irw" and see the button presses. But: lsof and netstat still do not
show lircd listening on port 5000! I am guessing that some in-kernel
driver is grabbing the packets and forwarding them internally to the
lircd process. I can't think of any other way that the packets could be
getting to lircd when lircd is not actually listening on the network.
Progress! Now I have to figure out how to connect the button presses to
the frontend, but at least I am partway there. Thanks for the help.
--Greg
</pre>
</blockquote>
To connect your remote to the frontend you need two files -
lircd.conf and lircrc. Where they go can be distribution specific.<br>
<br>
lircd.conf is remote specific and assigns human readable names to
the codes your particular remote generates, such as up_arrow,
down_arrow, etc.<br>
<br>
lircrc takes those human readable names and assigns them to
functions in Mythtv, Xine, mplayer, etc. The human readable names
in lircrc much match the human readable names defined in lircd.conf
exactly.<br>
<br>
Ziggy<br>
</body>
</html>