Recent Posts

Pages: 1 2 3 [4] 5 6 ... 10
31
Users / Re: EIB/KNX configuration
« Last post by girlaldo on December 29, 2016, 11:54:18 pm »
I did the change of eibaddr to 0.0.1 but nothing changed as a result.
The eib address from ETS4 of my IP interface is 1.1.255 (if as eibaddr is meant the knx address of the IPS/S2.1 IP Interface,MDRC device that let me to connect to knx network with ETS4).
You have been so kind and you spent a lot of time trying helping me.
I'll buy you a coffee anyway and as last thing I 'd like you to do for me is to put a post reply when a new " lmce 14.04 i386 iso " file completed with eibd package will be ready and working.
Thank you so much
32
Users / Re: EIB/KNX configuration
« Last post by posde on December 29, 2016, 06:42:55 pm »
I am really a bit at a loss here. Could you, just for giggles, please change your GA to 0.0.1, please, and see if that does make a difference. And please continue to run eibd via sudo, or as root.
33
Users / Re: Filename View in Orbiter
« Last post by maverick0815 on December 29, 2016, 06:27:00 pm »
thanks, I will give this a try and report back...perhaps even within this year :-)
34
Users / Re: EIB/KNX configuration
« Last post by girlaldo on December 29, 2016, 05:58:04 pm »
If I run it as root it doesn't reply nothing but the process does not run

aldo@dcerouter:~$ sudo /usr/bin/eibd --no-tunnel-client-queuing -D -T -R -S -i -u --eibaddr=1.1.255 --daemon=/var/log/eibd.log ipt:192.168.80.137
[sudo] password for aldo:
aldo@dcerouter:~$ ps -aux | grep eib
aldo     10347  0.0  0.0   4696  2040 pts/21   S+   17:52   0:00 grep --color=auto eib
aldo@dcerouter:~$ cat /var/log/eibd.log
cat: /var/log/eibd.log: No such file or directory
aldo@dcerouter:~$

anyway it is executable by anybody

aldo@dcerouter:~$ ls -al /usr/bin/eib*
-rwxr-xr-x 1 root root 397148 dic 11  2015 /usr/bin/eibd
-rwxr-xr-x 1 root root  38416 dic 11  2015 /usr/bin/eibnetdescribe
-rwxr-xr-x 1 root root  38420 dic 11  2015 /usr/bin/eibnetsearch

35
Users / Re: EIB/KNX configuration
« Last post by posde on December 29, 2016, 05:25:44 pm »
Oh, one more thing: execute eibd as root, ie. sudo eibd...
36
Users / Re: EIB/KNX configuration
« Last post by posde on December 29, 2016, 05:24:31 pm »
Does the logfile  /var/log/eibd.log  show anything of interest?
37
Users / Re: EIB/KNX configuration
« Last post by girlaldo on December 29, 2016, 04:27:50 pm »
I can't understand why 224.0.23.12 should be searched inside my network.
Anyway I changed the routing table and I restarted eibd but the result was the same:
Segmentation fault

aldo@dcerouter:~$ sudo route delete 224.0.23.12 dev eth0
aldo@dcerouter:~$ sudo route add 224.0.23.12 dev eth1
aldo@dcerouter:~$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         10.0.2.2        0.0.0.0         UG    0      0        0 eth0
10.0.2.0        *               255.255.255.0   U     0      0        0 eth0
link-local      *               255.255.0.0     U     1000   0        0 eth1
192.168.80.0    *               255.255.255.0   U     0      0        0 eth1
224.0.23.12     *               255.255.255.255 UH    0      0        0 eth1
aldo@dcerouter:~$ /usr/bin/eibd --no-tunnel-client-queuing -D -T -R -S -i -u --eibaddr=1.1.255 --daemon=/var/log/eibd.log ipt:192.168.80.137
Segmentation fault
38
Users / Re: EIB/KNX configuration
« Last post by posde on December 29, 2016, 04:11:39 pm »
The route is a broadcast route that is needed for KNX/IP to work.
39
Users / Re: EIB/KNX configuration
« Last post by girlaldo on December 29, 2016, 04:04:49 pm »
eth0 is connected to the external network where 224.0.23.12 is, while eth1 is connected to my internal network where the subnet 192.168.80.0 is.
I can't ping 224.0.23.12 but I think nobody can while I can ping google dns
aldo@dcerouter:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=63 time=115 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=63 time=56.9 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=63 time=55.0 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=63 time=53.3 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=63 time=54.3 ms

and I can ping my knx/ip device:
aldo@dcerouter:~$ ping 192.168.80.137
PING 192.168.80.137 (192.168.80.137) 56(84) bytes of data.
64 bytes from 192.168.80.137: icmp_seq=1 ttl=128 time=2.84 ms
64 bytes from 192.168.80.137: icmp_seq=2 ttl=128 time=1.75 ms
64 bytes from 192.168.80.137: icmp_seq=3 ttl=128 time=1.79 ms
64 bytes from 192.168.80.137: icmp_seq=4 ttl=128 time=1.70 ms
64 bytes from 192.168.80.137: icmp_seq=5 ttl=128 time=1.74 ms

here are the interfaces
aldo@dcerouter:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 08:00:27:9c:bb:97 
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:963527 errors:0 dropped:0 overruns:0 frame:0
          TX packets:530814 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:744585766 (744.5 MB)  TX bytes:80129911 (80.1 MB)

eth1      Link encap:Ethernet  HWaddr 08:00:27:78:71:f1 
          inet addr:192.168.80.1  Bcast:192.168.80.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:522962 errors:0 dropped:0 overruns:0 frame:0
          TX packets:941368 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:62990564 (62.9 MB)  TX bytes:1320045366 (1.3 GB
40
Users / Re: EIB/KNX configuration
« Last post by posde on December 29, 2016, 02:36:49 pm »
The route should be to the network where you KNX/IP device is, ie. eth1 in your case.
Pages: 1 2 3 [4] 5 6 ... 10