Hello.
I've got a strange problem.
In my house there's a LAN with a router (192.168.0.66)
and four pcs (192.168.0.1-4)
DHCP is enabled and working (tested with notebook)

Now the Problem:
I told Mythtv to use the IP 192.168.0.5, the Gateway (....0.66)
and my usual DNS Servers.
It integrates great into the LAN (Filesharing via Samba, pinging in every direction, Webmin)

But as soon as I try to ping the Gateway, the DNS Server or anything outside I get a time out.
I've tried everything I could think of: three different network cards, adding the IP's manually, by DHCP and more - I'm simply not able to ping the Router/Net.

what could be the reason for this problems.
In the "netcardconfig" module there are 2 Cards: eth0, and sit0 and I've got no idea what sit0 might be, but I also tried to supply it with the right IPs by DHCP in case it might be needed, but it didn't help

Sb got an idea what might be the reason/solution for this problem (I urgently have to upgrade XMLTV from CVS or my EPG won't work....
damm German EPG )

Thanks a lot in advance

Sounds to me like your gateway IP on your Myth system is incorrectly set.

I found a solution that works for me:

After booting I have to do
"pump -i eth0"
and afterwards set the IP via Netcardconfig to 192.168.0.5

thats the only way it was possible for me to get it running

someone got any idea how I could automate these 2 steps so that they are done automatically every time I boot

Thanks

I had the same problem with my Gigabyte Nforce 6150 motherboard.

Two connectors

eth0 = Onboard Ethernet in my case forceware
sit0 = Onboard Firewire controller in my case VIA

When I was using R5C7 I always had to run netcard config in order to get ethernet working. I experimented with changing the modules.conf file and placing forceware on the list before firewire. However, that really was not the perfect solution. It would still break. Luckily enogh R5D1 was released so I decided to run the upgrade. For me that did the trick and eliminated the problem. In reality R5D1 fixed all of the problems with my board and it's drivers....