Am 22.05.2016 um 06:19 schrieb info@rainerbertsch.de: Hi Chuck, thanks for the answer of my request. Yes, RTCM and server are on the same LAN-segment. we use a switch (or better we tried several different switches) .because wie now think that there is a networkproblem. We also tried it with 10 MB/s full duplex on both sides . Is there any other possibility to use in the configuration of RTCM oder server ? I tried ping tests but did not se any thin special. Am 22.05.2016 um 00:19 schrieb Chuck Henderson <rpt2@chuck.midlandsnetworking.com <mailto:rpt2@chuck.midlandsnetworking.com>>: Is the RTCM and the server on the same Ethernet LAN at the same location? Are you using an Ethernet switch or a hub? If you are using a switch then why are you not running everything full duplex? On Sat, May 21, 2016 at 3:02 PM, info@rainerbertsch.de <mailto:info@rainerbertsch.de> <info@rainerbertsch.de <mailto:info@rainerbertsch.de>> wrote: Hi there, Since November, we are trying to build a voting system. We need some help please ! Hardware: Supermicro Intel Atom D525 (we also tried a RaspberryPi and an other computer) Software: Since yesterday DIAL from Alllstar-Homepage (Before we tried it with ACID) RTCM from Micro Node, Mark, we have 4 of them and tried all of them Garmin GPS 18x LVC, also wie tried 4 of them. Error: More or less often the RTCM switch in the offline mode. When there is traffic very often. But not if at the same time there is a telnet connection from any computer to the RTCM. We suspect a networking problem between our asterisk-server and RTCM Network-Card is set to 10 MB / s half-duplex like in the RTCM. From tcpdump from server to rtcm we got: ——— snip ---------- GPSTime (cli0_yy): 05/05/16 12:48:01.000000000 SysTime: 05/05/16 12:48:01.040000 DrainTime: 05/05/16 12:48:01.000 Got GPS (cli0_yy): Lat: 4857.60N, Lon: 00915.01E, Elev: 214.4 sending KEEPALIVE (GPS) packet to client cli2_bprx digest bbb4c643 GPSTime (cli2_bprx): 05/05/16 12:48:01.000000000 SysTime: 05/05/16 12:48:01.300000 DrainTime: 05/05/16 12:48:01.240 Got GPS (cli2_bprx): Lat: 4853.16N, Lon: 00912.65E, Elev: 317.2 sending KEEPALIVE (GPS) packet to client cli0_yy digest 79d9c77d GPSTime (cli0_yy): 05/05/16 12:48:02.000000000 SysTime: 05/05/16 12:48:02.040000 DrainTime: 05/05/16 12:48:02.000 Got GPS (cli0_yy): Lat: 4857.60N, Lon: 00915.01E, Elev: 214.4 sending KEEPALIVE (GPS) packet to client cli2_bprx digest bbb4c643 [May 512:48:03]NOTICE[6559]:chan_voter.c:3632voter_reader:Voter lost master timing source!! sending packet challenge 200371797 digest 7749985d password BLAH sending packet challenge 200371797 digest 7749985d password BLAH sending packet challenge 200371797 digest bbb4c643 password BLAH GPSTime (cli2_bprx): 05/05/16 12:48:18.000000000 SysTime: 05/05/16 12:48:18.320000 DrainTime: 01/01/70 01:00:00.340 Got GPS (cli2_bprx): Lat: 4853.16N, Lon: 00912.65E, Elev: 317.2 -- Voter client cli0_yy disconnect (timeout) sending KEEPALIVE (GPS) packet to client cli2_bprx digest bbb4c643 ——— snip ---------- Konfiguration of the Ethernet-Card # ethtool eth0 Settings for eth0: Supported ports: [TP] Supported link modes: 10baseT / Half 10baseT / Full 100baseT / Half 100baseT / Full 1000baseT / Full Supported break frame use: No Supports auto-negotiation: Yes Advertised link modes: Not reported Advertised break frame use: No Advertised auto-negotiation: No Speed: 10Mb / s Duplex: Half Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: off MDI-X: off (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv sample link Does anyone have an idea what it may be ? Why there is no problem with telnet at the same time and how can we run the system without this workaround -- Rainer Bertsch DF3SY _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.