Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Avner

Pages: 1 ... 3 4 [5] 6
61
Users / zwave motion sensor fails to log activity events
« on: April 03, 2011, 05:24:40 am »
Hello,

I have 2 zwave devices in my system:
1. Lamp module - HA-03WD
2. Motion detector - HSM100
I added the 2 devices and both are showing on the floorplan.

Issuing command to the lamp module (e.g. light ON/OFF) works correctly. The lamp responds and the events, which include reponse information (log levels 36,40,41)
are logged in the log file (see example below)

However, I can not see activity events from the motion detector.
Issuing commands to the motion sensor device, triggers a one line response in the log file, which is not clear for me (see the two examples below)
Physically pressing the blue button in the motion sensor, triggers a respond with log levels 36,40,41

I see the signature (0x1 0x4 0x1 0x13 0x1 0xe8) that fits the ZDP200 lamp signature in LinuxMCE wiki page: http://wiki.linuxmce.org/index.php/ZWave_API
To simplify the logging I deleted the lamp device, but still seeing events with the signature "0x1 0x4 0x1 0x13 0x1 0xe8", which I thought indicate a lamp, so I'm confused here.


I am looking for help on the following 2 problems:
1. How to interpret the zwave log file.
2. How to log events from the motion sensor.


Thanks,
Avner



--------------------------------------------------------------------------
Details / examples
--------------------------------------------------------------------------

--------------------------------------------------------------------------
Lamp module example (works Ok)
--------------------------------------------------------------------------

avner@dcerouter:~/tmp1$ tail -f /var/log/pluto/37_ZWave.log
36      04/01/11 0:00:03.602     Received command for child <0xb690cb90>
36      04/01/11 0:00:03.602     ON RECEIVED FOR CHILD 2/0 <0xb690cb90>
40      04/01/11 0:00:03.614     Sending job 0x830dee8 (cb 207) - 0x1 0xa 0x0 0x13 0x2 0x3 0x20 0x1 0xff 0x5 0xcf 0xf3 (#\n#### #####) <0xb790eb90>
41      04/01/11 0:00:03.621     0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0xb790eb90>
41      04/01/11 0:00:03.665     0x1 0x5 0x0 0x13 0xcf 0x0 0x26 (######&) <0xb790eb90>


--------------------------------------------------------------------------
Motion detector examples
--------------------------------------------------------------------------


Two examples of sending commands to the motion detector and the response.

1. Sending command "Set Polling State" to motion sensor (device 44)
   /usr/pluto/bin/MessageSend localhost 0 44 1 966 2 "" 5 "" 220 "" 225 "" 239 ""
   
   avner@dcerouter:~/tmp1$ tail -f /var/log/pluto/37_ZWave.log
   36      03/31/11 23:57:25.726    Received command for child <0xb690cb90>


2. Sending command "WAKE UP" to motion sensor (device 44)
   /usr/pluto/bin/MessageSend localhost 0 44 1 840 48 "" 239 ""
   
   avner@dcerouter:~/tmp1$ tail -f /var/log/pluto/37_ZWave.log
   36      04/01/11 0:07:32.881     Received command for child <0xb690cb90>


When physically pressing on the blue button in the motion sensor, I can see the following in the log file
41      04/02/11 20:15:37.811           0x1 0x14 0x0 0x49 0x84 0x3 0xe 0x4 0x21 0x1 0x60 0x31 0x70 0x84 0x85 0x80 0x72 0x77 0x86 0xef 0x20 0xe3 (###I####!#`1p###rw## #) <0xb796bb90>
36      04/02/11 20:15:37.812           FUNC_ID_ZW_APPLICATION_UPDATE:UPDATE_STATE_NODE_INFO_RECEIVED received from node 3 -  <0xb796bb90>
36      04/02/11 20:15:37.812           GENERIC_TYPE_SENSOR_MULTILEVEL <0xb796bb90>
41      04/02/11 20:15:38.797           0x1 0x8 0x0 0x4 0x0 0x3 0x2 0x84 0x7 0x71 (#########q) <0xb796bb90>
36      04/02/11 20:15:38.798           FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb796bb90>
36      04/02/11 20:15:38.798           COMMAND_CLASS_WAKE_UP -  <0xb796bb90>
36      04/02/11 20:15:38.798           Running wakeupHandler for node 3 <0xb796bb90>
36      04/02/11 20:15:38.798           Got unicast wakeup from node 3, doing WAKE_UP_NO_MORE_INFORMATION <0xb796bb90>
40      04/02/11 20:15:38.896           Sending job 0x86b5160 (cb 183) - 0x1 0x9 0x0 0x13 0x3 0x2 0x80 0x2 0x9c 0xb7 0x4d (##########M) <0xb796bb90>
41      04/02/11 20:15:38.903           0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0xb796bb90>
41      04/02/11 20:15:38.923           0x1 0x5 0x0 0x13 0xb7 0x0 0x5e (######^) <0xb796bb90>
40      04/02/11 20:15:39.024           Sending job 0x86b5380 (cb 184) - 0x1 0x9 0x0 0x13 0x3 0x2 0x84 0x8 0x5 0xb8 0xd5 (###########) <0xb796bb90>
41      04/02/11 20:15:39.031           0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0xb796bb90>
41      04/02/11 20:15:39.072           0x1 0x5 0x0 0x13 0xb8 0x0 0x51 (######Q) <0xb796bb90>

62
Users / zwave device support for HA03 lamp module and ZRR150W Split Duplex Receptacle
« on: January 02, 2011, 06:58:52 pm »
Hello,

I want to test linuxmce with zwave. I found the following candidate zwave devices for initial testing:
   Z-Wave PC Starter Kit - ZS (HomeSeer)  (http://store.homeseer.com/store/Z-Wave-PC-Starter-Kit---ZS-HomeSeer-P783C3.aspx) which includes HA03 lamp module
   ZRR150W - Z-Wave Split Duplex Receptacle (ACT HomePro)
http://store.homeseer.com/store/ZRR150W---Z-Wave-Split-Duplex-Receptacle-ACT-HomePro-P528C123.aspx

I didn't find the above devices in the list of supported zwave devices (http://wiki.linuxmce.org/index.php/Category:ZWave).
Does linuxmce supports these zwave devices?

Regards,
Avner

63
Users / Re: DVB Cards info needed for Templates
« on: September 09, 2010, 01:09:16 am »
Quote from: MANDINGO on January 05, 2010, 08:18:28 pm
;D

Current Cards that are now in the system are !!!

WinTV-PVR-150
...
WinTV-HVR-1850
WinTV-HVR-1950
WinTV-HVR-2250
...
 ;D

I will be adding more later today but i need those mentioned tested and i still need alot of vendor id's so please keep the card info comming
as mention before there will be a deb supplied with the templates when complete that will handle the driver issue for some of the cards. 
There will be a final change on the cards once a bug has been fixed for the mythtv plugin...

Mandingo

Mandingo,
Hauppauge WinTV-HVR-1850 is not in the system, at least not for me. LinuxMCE fails to load the cx23885 driver that the card uses. I also tried loading the prebuilt drivers and to build them from source. Both attempts failed. Please see  http://forum.linuxmce.org/index.php?topic=10649.0

64
Installation issues / Re: HVR-1850 error during boot after apt-get install v4l2-modules drivers installed
« on: September 09, 2010, 12:59:41 am »
pyrilampes,
Did you try building the drivers as instructed in: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-1800 ?
Look at your kernel messages. You should see some messages related to loading the v4l2 drivers.
Do:
Code: [Select]
dmesg and look for messages related to cx23885 (this is the driver that the card uses) or other error messages.
I have the same Hauppauge 1850 card and also getting errors when the drivers are loading.
The kernel we are using (2.6.27-17-generic) should support the drivers out of the box. After getting errors, I tried adding the prebuilt drivers and also building the drivers from source - all trials without success (see: http://forum.linuxmce.org/index.php?topic=10649.0)

br, Avner

65
Installation issues / Re: Failure to operate TV capture card: Hauppauge WinTV-HVR 1850
« on: September 06, 2010, 08:56:07 am »
I posted a question in: http://www.linuxquestions.org/questions/showthread.php?p=4089215#post4089215
One reply was asuggestion to upgrade the kernel to 2.6.30. Can we do that in LinuxMCE 8.10 ?

Avner


66
Installation issues / Re: Failure to operate TV capture card: Hauppauge WinTV-HVR 1850
« on: September 05, 2010, 02:09:49 am »
Has anyone been able to check this problem yet?
In the current state of LinuxMCE, building the drivers (cx23885 / tuner) from source fails to compile, and the prebuilt drivers give error at load time.
I posted a request in the video4linux-list for help on how to resolve the compilation error when building the drivers from source on a 2.6.27-17-generic kernel.
I will check and update this thread with any relevant info. Otherwise, should we remove the Hauppauge 1850 card from the list of supported cards in: http://wiki.linuxmce.org/index.php/Capture_Cards

Regards,
Avner

67
Installation issues / Failure to operate TV capture card: Hauppauge WinTV-HVR 1850
« on: August 29, 2010, 01:02:30 am »
Hello,

I recently acquired a Hauppauge 1850 video card, since it is included in the list of Capture Devices that are listed as supported by LinuxMCE in: http://wiki.linuxmce.org/index.php/Capture_Cards
I am trying to install the video card into my Hybrid LinuxMCE core, unsuccessfully. I cannot see any picture from the card (I verified that the video card is working correctly under OS Windows)

Since I'm not sure what is the card type, I tried configuring, in the setup of mythtv, the Capture Card Setup / Card Type as:
1.   Analog V4L capture card
2.   DVB DTV capture card (v3.x)
All combinations ended unsuccessfully. I keep getting a grey window with no image (I tried connecting the DCT700 set-top box, through composite, analog, and ATSC into the 1850 video card).
To eliminate complications, I am trying to use the video card using a stand alone application such as tvtime, xawtv, scantv. I am getting similar failure to see an image. (For example, tvtime shows the message "No inputs avialble Cannot open capture device /dev/video0". Right clicking on Input configuration / Change video source doesn't give any options)

I installed the drivers for the card, according to the instructions in:
http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-1800

Building the drivers from source, according to the section "Making it Work" fails with error.
Code: [Select]
cd v4l-dvb
makeGives compilation the following error:
Code: [Select]
avner@dcerouter:~$ cd v4l-dvb/
avner@dcerouter:~/v4l-dvb$ make
make -C /home/avner/v4l-dvb/v4l
make[1]: Entering directory `/home/avner/v4l-dvb/v4l'
creating symbolic links...
make -C firmware prep
make[2]: Entering directory `/home/avner/v4l-dvb/v4l/firmware'
make[2]: Leaving directory `/home/avner/v4l-dvb/v4l/firmware'
make -C firmware
make[2]: Entering directory `/home/avner/v4l-dvb/v4l/firmware'
make[2]: Nothing to be done for `default'.
make[2]: Leaving directory `/home/avner/v4l-dvb/v4l/firmware'
Kernel build directory is /lib/modules/2.6.27-17-generic/build
make -C /lib/modules/2.6.27-17-generic/build SUBDIRS=/home/avner/v4l-dvb/v4l modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.27-17-generic'
CC [M] /home/avner/v4l-dvb/v4l/dvb_demux.o
/home/avner/v4l-dvb/v4l/dvb_demux.c: In function 'dvbdmx_write':
/home/avner/v4l-dvb/v4l/dvb_demux.c:1137: error: implicit declaration of function 'memdup_user'
/home/avner/v4l-dvb/v4l/dvb_demux.c:1137: warning: assignment makes pointer from integer without a cast
make[3]: *** [/home/avner/v4l-dvb/v4l/dvb_demux.o] Error 1
make[2]: *** [_module_/home/avner/v4l-dvb/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.27-17-generic'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/avner/v4l-dvb/v4l'
make: *** [all] Error 2
I then downloaded the prebuilt firmware and created the files: v4l-cx23885-avcore-01.fw and v4l-cx23885-enc.fw. Then I loaded the drivers using:
Code: [Select]
modprobe cx23885
modprobe tuner
In dmesg I see the following output:

Code: [Select]
[   17.696559] cx23885 driver version 0.0.2 loaded
[   17.696766] cx23885 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[   17.697103] CORE cx23885[0]: subsystem: 0070:8541, board: Hauppauge WinTV-HVR1850 [card=24,autodetected]
[   18.023353] tveeprom 0-0050: Hauppauge model 85021, rev C5F5, serial# 6418425
[   18.023360] tveeprom 0-0050: MAC address is f7b0bd91
[   18.023364] tveeprom 0-0050: tuner model is NXP 18271C2 (idx 155, type 54)
[   18.023368] tveeprom 0-0050: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88)
[   18.023373] tveeprom 0-0050: audio processor is CX23888 (idx 40)
[   18.023376] tveeprom 0-0050: decoder processor is CX23888 (idx 34)
[   18.023380] tveeprom 0-0050: has radio, has IR receiver, has no IR transmitter
[   18.023385] cx23885[0]: hauppauge eeprom: model=85021
[   18.075129] cx25840 2-0044: cx23888 A/V decoder found @ 0x88 (cx23885[0])
[   18.094106] firmware: requesting v4l-cx23885-avcore-01.fw
[   20.652675] cx25840 2-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes)
[   20.658952] cx23885[0]: registered device video0 [mpeg]
[   20.658957] cx23885_dvb_register() allocating 1 frontend(s)
[   20.658960] cx23885[0]: cx23885 based dvb card
[   20.763471] tda18271 0-0060: creating new instance
[   20.765478] TDA18271HD/C2 detected @ 0-0060
[   20.996721] DVB: registering new adapter (cx23885[0])
[   20.996727] DVB: registering adapter 0 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...
[   20.997486] cx23885_dev_checkrevision() Hardware revision = 0xd0
[   20.997499] cx23885[0]/0: found at 0000:02:00.0, rev: 4, irq: 18, latency: 0, mmio: 0xbbc00000
[   20.997511] cx23885 0000:02:00.0: setting latency timer to 64
[   21.032019] Registered IR keymap rc-hauppauge-new
[   21.032189] input: cx23885 IR (Hauppauge WinTV-HVR as /devices/pci0000:00/0000:00:1c.2/0000:02:00.0/input/input7
[   21.037190] BUG: unable to handle kernel NULL pointer dereference at 00000000
[   21.037200] IP: [<f8be8879>] :ir_core:__ir_input_register+0x269/0x300
[   21.037214] *pde = 00000000
[   21.037222] Oops: 0000 [#1] SMP
[   21.037229] Modules linked in: rc_hauppauge_new tda18271 s5h1411 cx25840 serio_raw psmouse evdev cx23885(+) cx2341x v4l2_common pcspkr videodev v4l1_compat videobuf_dma_sg videobuf_dvb snd_hda_codec_cmedia dvb_core videobuf_core ir_common ir_core btcx_risc tveeprom nvidia(P) snd_hda_intel snd_hda_codec i2c_core snd_hwdep snd_pcm snd_seq snd_timer snd_seq_device parport_pc parport snd iTCO_wdt button iTCO_vendor_support soundcore shpchp pci_hotplug snd_page_alloc intel_agp agpgart ipv6 ext3 jbd mbcache sd_mod crc_t10dif sr_mod cdrom sg usbhid hid ata_piix pata_acpi ata_generic libata tulip scsi_mod dock sky2 uhci_hcd usbcore floppy raid10 raid456 async_xor async_memcpy async_tx xor raid1 raid0 multipath linear md_mod thermal processor fan nbd fbcon tileblit font bitblit softcursor fuse
[   21.037364]
[   21.037370] Pid: 2802, comm: modprobe Tainted: P          (2.6.27-17-generic #1)
[   21.037375] EIP: 0060:[<f8be8879>] EFLAGS: 00010246 CPU: 1
[   21.037382] EIP is at __ir_input_register+0x269/0x300 [ir_core]
[   21.037385] EAX: 00000000 EBX: 00000000 ECX: c0486ab4 EDX: f7ac7800
[   21.037388] ESI: f8cbb348 EDI: f712e800 EBP: f7b0bd5c ESP: f7b0bd2c
[   21.037390]  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
[   21.037394] Process modprobe (pid: 2802, ti=f7b0a000 task=f781b240 task.ti=f7b0a000)
[   21.037396] Stack: 00000074 00000000 f8d178cd c037e40b 00000000 f7ac7938 f7ac7800 00000246
[   21.037406]        f7ac7954 f8d0f2e0 f7b93000 f8cbb348 f7b0bdc0 f8d0e58e f8d178cd 00000000
[   21.037415]        f8d178b1 f71224f4 f7ac6418 f7ac6438 f712e800 f7ac6400 c049d680 00000004
[   21.037425] Call Trace:
[   21.037431]  [<c037e40b>] ? printk+0x1d/0x22
[   21.037440]  [<f8d0f2e0>] ? cx23888_ir_rx_s_parameters+0x0/0x2e0 [cx23885]
[   21.037458]  [<f8d0e58e>] ? cx23885_input_init+0x21e/0x330 [cx23885]
[   21.037475]  [<f8d11ad0>] ? cx23885_initdev+0x270/0xbf1 [cx23885]
[   21.037492]  [<c02649ee>] ? pci_device_probe+0x5e/0x80
[   21.037503]  [<c02c5439>] ? really_probe+0x59/0x190
[   21.037510]  [<c0263fa6>] ? pci_match_device+0xc6/0xd0
[   21.037527]  [<c02c55b3>] ? driver_probe_device+0x43/0x60
[   21.037533]  [<c02c5649>] ? __driver_attach+0x79/0x80
[   21.037540]  [<c02c4d13>] ? bus_for_each_dev+0x53/0x80
[   21.037545]  [<c0264930>] ? pci_device_remove+0x0/0x40
[   21.037551]  [<c02c52ee>] ? driver_attach+0x1e/0x20
[   21.037555]  [<c02c55d0>] ? __driver_attach+0x0/0x80
[   21.037560]  [<c02c46af>] ? bus_add_driver+0x1cf/0x250
[   21.037570]  [<c0264930>] ? pci_device_remove+0x0/0x40
[   21.037575]  [<c02c581e>] ? driver_register+0x6e/0x150
[   21.037585]  [<f8868000>] ? cx23885_init+0x0/0x45 [cx23885]
[   21.037597]  [<c0264c1f>] ? __pci_register_driver+0x4f/0x90
[   21.037603]  [<f8868000>] ? cx23885_init+0x0/0x45 [cx23885]
[   21.037612]  [<f8868043>] ? cx23885_init+0x43/0x45 [cx23885]
[   21.037622]  [<c0101120>] ? _stext+0x30/0x160
[   21.037628]  [<c012b65e>] ? try_to_wake_up+0xde/0x290
[   21.037637]  [<c014c914>] ? __blocking_notifier_call_chain+0x14/0x70
[   21.037650]  [<c015c5a8>] ? sys_init_module+0x88/0x1b0
[   21.037657]  [<c019187a>] ? sys_mmap_pgoff+0x7a/0x160
[   21.037663]  [<c0103f7b>] ? sysenter_do_call+0x12/0x2f
[   21.037668]  =======================
[   21.037670] Code: e8 ad 4d 5c c7 e9 de fd ff ff 8b 55 ec 8b 45 f0 e8 5d 7e 79 c7 89 f8 e8 f6 83 6e c7 85 c0 89 c3 78 bf 8b 55 e8 8b 82 5c 01 00 00 <83> 38 01 74 3a a1 00 cf be f8 31 db 85 c0 0f 8e a9 fd ff ff 8b
[   21.037723] EIP: [<f8be8879>] __ir_input_register+0x269/0x300 [ir_core] SS:ESP 0068:f7b0bd2c
[   21.037732] ---[ end trace 5aec1bfd58a8395d ]---

...

signature = 0xeedefb64, cmd = STOP_CAPTURE
[  444.083448] Firmware and/or mailbox pointer not initialized or corrupted, signature = 0xeedefb64, cmd = PING_FW
[  444.083562] firmware: requesting v4l-cx23885-enc.fw
I notice the line:
Quote
BUG: unable to handle kernel NULL pointer dereference at 00000000.
and the stack trace just after loading the cx23885 driver.
Does it indicate a problem with the driver?
Any help is greatly appreciated

Regards,
Avner

68
Installation issues / Re: How to keep LinuxMCE up-to-date with updates
« on: August 25, 2010, 06:47:41 am »
Phenigma,


I do get updates. However, I notice that your changes to apt prefernce:
 
Code: [Select]
sudo echo 'Package: mythtv mythtv-frontend mythtv-backend mythtv-common mythtv-database mythtv-transcode-utils mythweb libmythtv-perl libmyth python-myth mythtv-themes mythplugins mytharchive mytharchive-data mythbrowser mythgallery mythgame mythmovies mythmusic mythnetvison mythnetvision-data mythnews mythvideo mythweather mythzoneminder myth-doc 
Pin: origin deb.linuxmce.org
Pin-Priority: 1001
'  | sudo tee /etc/apt/preferences
remove the lower section as mentioned in http://forum.linuxmce.org/index.php?topic=10309.0

Code: [Select]
# If our local package uses the same version as elsewhere, we take the one we have locally.
Package: *
Pin: origin
Pin-Priority: 600
Is the lower section still needed?
 
Regards,
Avner


69
Installation issues / Re: How to keep LinuxMCE up-to-date with updates
« on: August 23, 2010, 07:42:11 am »

Using the commands above with slight variation (see code below), removed the avenard repository and enabled to do incremental upgrades:
Code: [Select]
sudo cp /etc/apt/sources.list /etc/apt/sources.list.orig
sudo sed -e '/deb-cache/d' -i /etc/apt/sources.list
sudo sed -e '1ideb file:\/usr\/pluto\/deb-cache .\/' -i /etc/apt/sources.list
sudo sudo sed -e '/avenard/d' -e /etc/apt/sources.list

70
Installation issues / Re: How to keep LinuxMCE up-to-date with updates
« on: August 20, 2010, 07:19:51 am »
I should mention that I do have Internet connection. The first installation updates the packages. What I'm referring to is the lack of incremental updates

Avner

71
Installation issues / How to keep LinuxMCE up-to-date with updates
« on: August 20, 2010, 07:03:45 am »

Hello,

I have installed LinuxMCE-810 beta as instructed in: http://wiki.linuxmce.org/index.php/Installing_0810
According to the section in the above wiki page: "Keeping Up-to-date with updates"
Code: [Select]
sudo apt-get update
sudo apt-get upgrade
should update to the latest and greatest
However, the version I have is: Version 2.0.0.44.09112922522 (Sun Nove 29 13:36:43 2009) (I get the version detalis from the LinuxMCE button in the Orbitter) The date is from almost one year ago !!!. When I do
Code: [Select]
sudo apt-get update
sudo apt-get upgrade
I don't see anything updated.
I assume that the list of DVD snapshots contains incremental changes. How can I update these changes through the network?
Also, is there a way to remove the avenard repo so I don't get the error message every time I do sudo apt-get update?

Regards,
Avner

72
Installation issues / Re: configure linksys router toa switch
« on: August 05, 2010, 04:19:56 am »
Finally, I was able to make the WRT54G connected to eth1 in the Core  :)
I over sited the instruction in step 5 to connect the WRT54G to the core through the LAN port not the WAN port.
After connecting the WRT54G to one of the 4 LAN ports, I can now access the WRT54G management web page (at 192.168.80.130) and ping it.
I can also ping PC1 that is connected to another LAN port on the WRT54G

Thanks Techstyle for helping me with this problem

P.S.
Now my PC1 (Windows machine) cannot connect to the Internet when it is connected both to the external network via wireless and to
the internal network (via wired connection to the WRT54G, which is wired to eth1 in the Core)  ???

ipconfig shows:
Code: [Select]
C:\Windows\system32>ipconfig

Windows IP Configuration


Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : Moshkovitz
   Link-local IPv6 Address . . . . . : fe80::c48:de15:4b6:a34c%11
   IPv4 Address. . . . . . . . . . . : 10.0.1.2
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.0.1.1

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::bd61:d2fb:230e:4c1e%10
   IPv4 Address. . . . . . . . . . . : 192.168.80.140
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.80.131
                                       192.168.80.1

If I disconnect the wire connection, it can access the Internet fine.

73
Installation issues / Re: configure linksys router toa switch
« on: August 05, 2010, 03:51:06 am »
Update:

When I take out the WRT54G and wire PC1 directly to eth1, I can access the WebAdmin page and also ping 192.168.80.1 from PC1
From the core side I can see PC1 and ping it (at 192.168.80.140)
So the problem is with the connection to the WRT54G. I tested the WRT54G and it is fully functional outside linuxMCE system.

Another observation is that eth1 returns with no data avilable (in both cases, when the WRT54G and when PC1 is connected to eth1)
Code: [Select]
ethtool eth1
Setting for eth1:
No data avialable

ethtool -i eth1
driver: tulip
version 1.1.15
firmware-version:
bus-info: 0000:01:0a:0
Avner

74
Installation issues / Re: configure linksys router toa switch
« on: August 05, 2010, 03:09:24 am »
Ok, I reinstalled linuxMCE with 2 cards and I still get the same problem.
I configure the WRT54G by connecting it to the external router (Time capsule / Air  port)

After I change the IP address of WRT54G to 192.168.80.130 (step 3) I can not access the WRT54G anymore.
When the WRT54G is still connected to the external router, I can connect to it from PC1 at 198.168.80.130, but only if I wire the WRT54G to PC1
(In wireless connection, I can connect to the WRT54G network but cannot access the router)

However, when I connect the WRT54G to eth1 on PC2 (the Core) I cannot access or ping the WRT54G.

I tried restarting eth1:
Code: [Select]
sudo ifdown eth1
sudo ifup eth1
eth1 shows up in ifconfig:
Code: [Select]
...
eth1 Link encap:Ethernet HWaddr 00:80:c6:ee:11:73
inet addr:192.168.80.1 Bcast:192.168.80.255 Mask:255.255.255.0
inet6 addr: fe80::280:c6ff:feee:1173/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3850 errors:0 dropped:0 overruns:0 frame:0
TX packets:9232 errors:115957 dropped:0 overruns:0 carrier:115957
collisions:0 txqueuelen:1000
RX bytes:245158 (245.1 KB) TX bytes:414561 (414.5 KB)
Interrupt:21 Base address:0xb800
...

Code: [Select]
ping 198.168.80.130hangs

Code: [Select]
ip neigh showresults in:
Code: [Select]
...
192.168.80.130 dev eth1 FAILED
...
Any help would be greatly appreciated
Avner

75
Installation issues / Re: configure linksys router toa switch
« on: August 02, 2010, 09:42:42 am »

Techstyle, thanks for the quick response.
To answer your questions:

Quote
1.  Can anything connected to the WRT54G access the internet or Web admin?
2.  Can the core access the internet?
3.  If you connect a PC on the internal network to Eth1 directly, can you access the internet now?

1. I connected PC1 directly to the WRT54G. PC1 cannot access the internet. It also cannot connect to the Web admin
2. The core can access the internet
3. I connected PC1 directly to the external interface. It cannot access the internet

So I'm guessing that the problem is with eth1.

I setup eth1 according to the instructions in:
http://wiki.linuxmce.org/index.php/Single_to_Double_NIC
and in:
http://linuxmce.wordpress.com/2007/10/03/hack-5-howto-modify-network-configuration/

When I do ifconfig on the core, I'm getting the following:

Code: [Select]
avner@dcerouter:~$ sudo ifconfig
[sudo] password for avner:
eth0 Link encap:Ethernet HWaddr 00:13:d4:29:17:e7
inet addr:10.0.1.12 Bcast:10.0.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:d4ff:fe29:17e7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:88890 errors:0 dropped:0 overruns:0 frame:0
TX packets:98965 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:102072129 (102.0 MB) TX bytes:10176103 (10.1 MB)
Interrupt:17

eth1 Link encap:Ethernet HWaddr 00:80:c6:ee:11:73
inet addr:192.168.80.1 Bcast:192.168.80.255 Mask:255.255.255.0
inet6 addr: fe80::280:c6ff:feee:1173/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:46 errors:0 dropped:0 overruns:0 frame:0
TX packets:29689 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:17070 (17.0 KB) TX bytes:1257465 (1.2 MB)
Interrupt:21 Base address:0xb800

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:47088 errors:0 dropped:0 overruns:0 frame:0
TX packets:47088 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11076519 (11.0 MB) TX bytes:11076519 (11.0 MB)

Avner

Pages: 1 ... 3 4 [5] 6