Another interesting piece of data is that when I reconfigure to the modem->router->core->internal network (i.e. working) state, I call dhclient -r to release followed by dhclient to renew dhcp info.  After that, I can access the internet from the core, but I still have the same problem with PCs on the internal network.  They only start working after a full reboot of the core.

colinjones--

Here's the information you requested.  This issue doesn't seem to be going away, so any advice would definitely be appreciated, though I just don't see anything unusual in this data.

I'm not quite sure I understand the MTU suggestions.  Should I decrease MTU size on eth1 (internal) or eth0 (external)?

Code:

linuxmce@dcerouter:~$ sudo ifconfig
eth0      Link encap:Ethernet  HWaddr 00:15:17:22:3f:8c
          inet addr:76.88.197.XXX  Bcast:255.255.255.255  Mask:255.255.248.0
          UP BROADCAST RUNNING MULTICAST  MTU:576  Metric:1
          RX packets:128870 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21197 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:15284361 (15.2 MB)  TX bytes:3252505 (3.2 MB)
          Memory:c2820000-c2840000

eth1      Link encap:Ethernet  HWaddr 00:15:17:22:3f:8d
          inet addr:192.168.80.1  Bcast:192.168.80.255  Mask:255.255.255.0
          inet6 addr: fe80::215:17ff:fe22:3f8d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:16570 errors:0 dropped:0 overruns:0 frame:0
          TX packets:104093 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2085853 (2.0 MB)  TX bytes:4663577 (4.6 MB)
          Memory:c2800000-c2820000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:83145 errors:0 dropped:0 overruns:0 frame:0
          TX packets:83145 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10946905 (10.9 MB)  TX bytes:10946905 (10.9 MB)

note: Last Byte of IP address edited for posting

linuxmce@dcerouter:~$ cat /etc/resolv.conf
domain bak.rr.com
search bak.rr.com
nameserver 76.85.229.110
nameserver 76.85.229.111
linuxmce@dcerouter:~$


linuxmce@dcerouter:~$ sudo route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.80.0    0.0.0.0         255.255.255.0   U     0      0        0 eth1
76.88.192.0     0.0.0.0         255.255.248.0   U     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 eth0
0.0.0.0         76.88.192.1     0.0.0.0         UG    100    0        0 eth0

linuxmce@dcerouter:~$ netstat -ree
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface    MSS   Window irtt
192.168.80.0    *               255.255.255.0   U     0      0        0 eth1     0     0      0
76.88.192.0     *               255.255.248.0   U     0      0        0 eth0     0     0      0
link-local      *               255.255.0.0     U     1000   0        0 eth0     0     0      0
default         cpe-76-88-192-1 0.0.0.0         UG    100    0        0 eth0     0     0      0

Thanks a lot for the help so far, gang.

Thanks for the info, gang.

colinjones:
Http access works fine from the core, even in both configurations (internal network working, internal network not working), which makes me a bit worried that maybe it's not an ISP issue.  I can print out DNS information and routing tables when I get back in front of the PC, but he DNS information looked good for both the core and the clients in that DNS and gateway information seemed valid.  The only protocols I've tried so far are http and ping, though it looks like whatever protocol Yahoo IM is using is also affected.
 
I appreciate your advice.

I'm having an issue with my 0810 setup that makes no sense whatsover and is yet again driving me crazy.
I installed 0810  successfully in the network configuration  cable modem->router->core->internal network.  In this configuration, everything seems to be working OK.

However, I tried removing the router to give me: cable modem->core->internal network.  In this configuration, I can access the net from the core without a problem, but I can't access http at all from any PCs on the internal network.  I can ping lmce.org without a problem, however.  Switching back to the 1st configuration fixes things consistently. Switching back to the second configuration breaks things consistently.

I captured some data with wireshark.  This is a request for linuxmce.org from firefox on a windows PC on the internal network

looking at the external NIC (IP: 192.168.1.108):

No.     Time        Source                Destination           Protocol Info
      1 0.000000    192.168.1.108         193.200.113.133       TCP      49281 > http [SYN] Seq=0 Win=8192 Len=0 MSS=1456 WS=2
      2 0.175891    193.200.113.133       192.168.1.108         TCP      http > 49281 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460 WS=7
      3 0.176709    192.168.1.108         193.200.113.133       TCP      49281 > http [ACK] Seq=1 Ack=1 Win=66976 Len=0

now the http get call

      4 0.177002    192.168.1.108         193.200.113.133       HTTP     GET / HTTP/1.1

the ack

      5 0.356041    193.200.113.133       192.168.1.108         TCP      http > 49281 [ACK] Seq=1 Ack=420 Win=6912 Len=0

and data...
 
     6 0.369530    193.200.113.133       192.168.1.108         TCP      [TCP segment of a reassembled PDU]
     7 0.369780    193.200.113.133       192.168.1.108         TCP      [TCP segment of a reassembled PDU]
....

I see this correct behavior when I use wireshark on eth1 (internal NIC) as well.

But when I connect the core directly to the modem, I get a new IP address of  76.83.118.XX
same request:   (XX is the last byte of my IP address)

No.     Time        Source                Destination           Protocol Info
      1 0.000000    76.83.118.XX          193.200.113.133       TCP      49173 > http [FIN, ACK] Seq=1 Ack=1 Win=16744 Len=0
      2 0.066986    76.83.118.XX          193.200.113.133       TCP      49176 > http [SYN] Seq=0 Win=8192 Len=0 MSS=1456 WS=2
      3 0.215705    193.200.113.133       76.83.118.XX          TCP      http > 49173 [ACK] Seq=2913 Ack=2 Win=54 Len=0
      4 0.244939    193.200.113.133       76.83.118.XX          TCP      http > 49176 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460 WS=7
      5 0.245589    76.83.118.XX          193.200.113.133       TCP      49176 > http [ACK] Seq=1 Ack=1 Win=66976 Len=0

now the http get

     6 0.246035    76.83.118.XX          193.200.113.133       HTTP     GET / HTTP/1.1

and the ack

     7 0.428837    193.200.113.133       76.83.118.XX          TCP      http > 49176 [ACK] Seq=1 Ack=369 Win=6912 Len=0

...and then nothing, no data.  Firefox is stuck at 'Waiting for reply.'  This happens with any website I try.  Does anyone have any idea what might be going on?  Could this be an issue with my provider?  Any help would be greatly appreciated as the WAF is quickly decreasing and I have a lot of work on this that I want to do.

I've got both insteon and zwave equipment to use.

Let me know how i can help.

Does this mean you're now officially a ruby/swig/libruby expert (amongst other things)?

I may be able to attend and support with some more hardware, squeezebox, gc100, etc.. Please let me know what you're planning.

-Peter

Just an update--

I'm running 0810 alpha1 now and I'm note seeing the network freeze issue.  I don't know if it's something that's not currently operational yet in 0810 or something that was fixed in either a Kubuntu or LMCE upgrade.  In any case, I'll have a good delta if things break in a future release of 0810.  This is a huge relief from the 0710 frustration.  Good job dev team, and thanks.

-PeteK

The problem with the method you're following is that it assumes that LMCE is in complete control of the TV, which is not true in real life.  In real life, someone may have come along and turned off the TV while LMCE thought it was on.   The next time you try to use it (for example by pressing the 'menu' button on the remote), you want LMCE to recognize it is off, turn it on, and wait for any required delay before proceeding with further commands (changing inputs, etc).

I'm not sure what the TV you're using does, but my Olevia responds to the 'power status' command with a status reply when it's on, but not when it's off.  So the correct functionality would be for the on command to:

Code:

Send a 'Power Status' command;
while (some_short_timeout)
   {
      if (TV replies with 'Power Status ON')
     {
          exit;
     }
 }
 Send 'TV On' command;
 Wait_for_timeout_period;   

There's a good implementation of a TV GSD here:

http://wiki.linuxmce.org/index.php/LG_42LB5D

I'm not very experienced at using ruby, so I still have to figure out how to do the above as a GSD, but I'll be doing so shortly

I am heading over to our local AV store to look at what devices they offer w/ eth or rs232 support for a new house so that it will all be controlled with LinuxMCE.
The wiki's section, http://wiki.linuxmce.org/index.php/Have_LinuxMCE_automatically_control_the_TV_and_Stereo suggests it's all automatic but not having any devices like this I am not sure what to expect or choose.

RS232 is obvious and detailed here in http://wiki.linuxmce.org/index.php/AV_Devices
Ethernet has me a bit curious, http://wiki.linuxmce.org/index.php/Plug%26play suggests it correlates by mac address so how does one perform the initial pairing? Do I need to know the mac address before hand?

Finally, does anyone have any reco's for manufactures to look for that have decent ethernet controlled devices?

Thanks!

Ethernet-controlled devices do use MAC address for identification.  This is set in the device template definition.  Typically, a range is set based on a manufacturer's assigned MAC address range.  This gets a bit tricky when using devices from manufacturers that make more than one device used with LMCE (Roku for example).  You can always tailor your range if you'd like, however.

tkmedia--

Thanks for the info, I was able to get the MD up and running!  I'm still having some issues with the screen resolution, however.   Selection 720p seems to actually set the unit to a lower resolution, though this may be a desktop size and not screen resolution issue.  I'm not sure what's going on yet, but I'll dig into it a bit more and see if I need to post a trac bug.

Zaerc--

Sorry about the post.  I thought all 0810 issues were going into the Dev forum.  I'll be a bit smarter about it next time.

-PeteK

Hi,

go into Edit A/V properties in template. you'll have a line like that :

Delays: Power: 2000 miliseconds, Mode: 1000 miliseconds, Other: 0.5 miliseconds [change/explain]

and there you can check what is your delay for power command...

HTH,

regards,

Bulek.

I would also advise him to check the commands themselves as some, such as the Denon receiver, have a pause in the ruby code for multi-step poweron.  It may be stackup of a couple of timing delays that's causing this.

Pete K

BuleK is correct.  The first command that is issued is an 'on' command, which will have a delay if the TV is in fact off and needs to power up fully before receiving further commands.  I would check the ruby code in the 'on' command for your device.  A better implementation would be for the 'on' command to check to see if the TV is on before issuing the command and delaying.

Hi gang--

I'm trying to get my MD up and running under 0810 so I can do some testing.  I'm having xorg.conf issues.  I believe this is due to the fact that I've got an ati embedded graphics chip on my core and an nvidia chip on the MD, so for example, there is no 'driver nv' line in the xorg.conf as referenced in the wiki. When I try to run currently, I get an 'out of range' warning on my monitor.

Does anyone have an example xorg.conf I can use?  Otherwise, I'm thinking of installing 0810 on the md, then copying the xorg.conf file.

Any help would be appreciated.

Thanks,
PeteK