On Wed, 2014-10-08 at 10:15 -0700, Geoffrey Leach wrote:
> Turns out that there's an undocumented feature on the HDTV tuner
> software. Said software looks for a connection in a particular range
> of addresses. Assigning the ethernet configuration an IP address in
> that range solves my problem.
I
On 10/07/2014 12:31:48 PM, Lars E. Pettersson wrote:
> On 10/07/14 17:58, Tim wrote:
> > Allegedly, on or about 07 October 2014, Lars E. Pettersson sent:
> >> 192.168.10.3 and 198.168.20.5 are on two different networks.
> >
> > That depends on network configuration (where your netmask is), and
> wh
On 10/07/14 17:58, Tim wrote:
Allegedly, on or about 07 October 2014, Lars E. Pettersson sent:
192.168.10.3 and 198.168.20.5 are on two different networks.
That depends on network configuration (where your netmask is), and what
hardware (if any) is between devices.
Yes, but 192.168.10.3 and
Allegedly, on or about 07 October 2014, Lars E. Pettersson sent:
> 192.168.10.3 and 198.168.20.5 are on two different networks.
That depends on network configuration (where your netmask is), and what
hardware (if any) is between devices.
With a netmask of 255.255.255.0 those are two different net
On 10/07/14 02:52, Geoffrey Leach wrote:
In the /etc/hosts used by each member of my little network, the system to which
the tuner is attached is 192.168.10.3, and the tuner itself is 198.168.20.5. I
can ping 198.168.20.5, but I have a sinking feeling that what I'm pinging is
the ethernet nic,
On 10/06/2014 01:41:13 PM, Lars E. Pettersson wrote:
> On 10/06/14 01:41, Geoffrey Leach wrote:
> > To recap. I have an ethernet port that's wired to a HDTV tuner that
> converts OTA HDTV to ma4 and streams it down the cable to a program
> that collects and stores it. All of this is known to work u
On 10/06/14 01:41, Geoffrey Leach wrote:
To recap. I have an ethernet port that's wired to a HDTV tuner that converts
OTA HDTV to ma4 and streams it down the cable to a program that collects and
stores it. All of this is known to work under Fedora 17. No so under Fedora 19.
FirewallD is stopp
10/06/2014 10:37 AM, Geoffrey Leach wrote:
On 10/06/2014 06:47:16 AM, Greg Woods wrote:
On Sun, Oct 5, 2014 at 5:41 PM, Geoffrey Leach
wrote:
The ethernet port has a ifcfg script with
HWADDR="E8:40:F2:05:DE:1C"
BOOTPROTO=none
IPADDR="198.168.20.5"
but is otherwise as created b
On Mon, Oct 6, 2014 at 11:37 AM, Geoffrey Leach wrote:
> On 10/06/2014 06:47:16 AM, Greg Woods wrote:
>
> > Don't you need "BOOTPROTO=static"?
> >
> Apparently "static" is not a defined value for BOOTPRO, and when an
> undefined term is used, it defaults to "none". One of the little bits of
> hig
On 10/06/2014 06:47:16 AM, Greg Woods wrote:
> On Sun, Oct 5, 2014 at 5:41 PM, Geoffrey Leach
> wrote:
>
> >
> > The ethernet port has a ifcfg script with
> > HWADDR="E8:40:F2:05:DE:1C"
> > BOOTPROTO=none
> > IPADDR="198.168.20.5"
> > but is otherwise as created by Anaconda.
> >
>
>
On Sun, Oct 5, 2014 at 5:41 PM, Geoffrey Leach wrote:
>
> The ethernet port has a ifcfg script with
> HWADDR="E8:40:F2:05:DE:1C"
> BOOTPROTO=none
> IPADDR="198.168.20.5"
> but is otherwise as created by Anaconda.
>
Don't you need "BOOTPROTO=static"?
--Greg
--
users mailing list
use
Sorry to be a bother, but ...
To recap. I have an ethernet port that's wired to a HDTV tuner that converts
OTA HDTV to ma4 and streams it down the cable to a program that collects and
stores it. All of this is known to work under Fedora 17. No so under Fedora 19.
FirewallD is stopped.
The eth
12 matches
Mail list logo
