<p dir="ltr">Craig,</p>
<p dir="ltr">Which NIC is that? We had the same experience (no Gbit connection) on Shuttle computers. I don't have this information near my hands, but IIRC they had JMicron NICs. We never had issues with Intel motherboards.<br>
</p>
<p dir="ltr">Please excuse typos. Written with a touchscreen keyboard.</p>
<p dir="ltr">--<br>
Regards,<br>
Alexander Chemeris<br>
CEO/Founder Fairwaves LLC<br>
<a href="http://fairwaves.ru">http://fairwaves.ru</a></p>
<div class="gmail_quote">On Mar 15, 2013 11:26 PM, "Craig Reading" <<a href="mailto:craig.reading1@gmail.com">craig.reading1@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto"><div>Hi Alexander</div><div><br></div><div>I'll email the wireshark trace to you shortly. Yes I have been playing with network setup but can't remember the configuration when successful!</div><div>
<br></div><div>The openBTS server has a 1Gbit NIC but can't get it to negotiate anything other than 100Mbit even after updating drivers and much other 'playing' with cables hubs and switches!</div><div><br></div>
<div>Mr Amazon is bringing some new network components tomorrow which should help further my investigations.</div><div><br></div><div>This might well be one of these weird network issues you have seen that we might get to the bottom off.<br>
<br>Regards<div>Craig</div></div><div><br>On 15 Mar 2013, at 19:04, Alexander Chemeris <<a href="mailto:alexander.chemeris@gmail.com" target="_blank">alexander.chemeris@gmail.com</a>> wrote:<br><br></div><blockquote type="cite">
<div><p dir="ltr">Craig,</p>
<p dir="ltr">Could you please send a Wireshark capture of the start attempt? Send it to me directly if it's more then 100k.</p>
<p dir="ltr">This looks very much like a networking issue. Have you changed your network setup since it was working? May be connected it through a different switch? We found that some models of switches does not work well and introduce weird issues.</p>
<p dir="ltr">Is your network card 100Mbit or 1Gbit?</p>
<p dir="ltr">If it's an UmTRX issue indeed, we'll replace it. Our beta testers is our most precious asset.</p>
<p dir="ltr">Please excuse typos. Written with a touchscreen keyboard.</p>
<p dir="ltr">--<br>
Regards,<br>
Alexander Chemeris<br>
CEO/Founder Fairwaves LLC<br>
<a href="http://fairwaves.ru" target="_blank">http://fairwaves.ru</a></p>
<div class="gmail_quote">On Mar 15, 2013 10:07 PM, "Craig Reading" <<a href="mailto:craig.reading1@gmail.com" target="_blank">craig.reading1@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>Hi All,<br><br></div><div>After my initial success early in the week things seems to have gone pear shaped!<br><br></div><div>I cannot get OpenBTS to start reliably as per traces below. After a power cycle of the UmTRX I can normally get OpenBTS to start for a few seconds before the transceiver terminates again. ./transceiver starts and runs on its own OK but there is a lot less traffic in a wireshark trace compared to being started from OpenBTS.<br>
<br></div><div>When the transceiver starts from OpenBTS a Wireshark trace shows a lot of UDP packets.<br><br></div><div>Approx 460 x 36 byte UDP packets for the first 0.5 seconds<br></div><div>Then some variable length UDP packets all ACKed back with 36 bytes<br>
</div><div>After 0.8 from startup the UmTRX sends a 28 byte message:<br><br>14d0000700000005000000140000000000a6d5180000000000100100<br><br></div><div>After approx 1.0s from startup I then only get a few packets back from UmTRX<br>
</div><div>After 5s I get nothing back from UmTRX<br></div><div>After 6s I get an ICMP Port Unreachable<br></div><div><br>If I had more time I would look into the transceiver source code to figure out where things are stopping.<br>
<br>I suspect this might be a networking issue and have tried changing some Linux kernel buffer settings without success. I have also reset my OpenBTS database just in case I had an option in there causing this. I'll carry on checking out the network side of things but I am starting so suspect there might be an issue with the UmTRX.<br>
<br>Help!<br><br></div><div>Regards<br></div><div>Craig<br><br></div><div>>> Traces<br></div><div><br>ALERT 46937531359488 TRXManager.cpp:408:powerOn: POWERON failed with status -1<br>
transceiver: no process killed<br>linux; GNU C++ version 4.1.2 20080704 (Red Hat 4.1.2-52); Boost_104100; UHD_003.<br>004.000-93a49d0<br><br>terminate called after throwing an instance of 'uhd::runtime_error'<br>
what(): RuntimeError: no control response<br>
<b>EMERG 1101519168 OpenBTS.cpp:134:startTransceiver: Transceiver quit with status<br>6. Exiting.</b><br><br></div>or:<br><br>ALERT 47613775102208 TRXManager.cpp:408:powerOn: POWERON failed with status -1<br>transceiver: no process killed<br>
linux; GNU C++ version 4.1.2 20080704 (Red Hat 4.1.2-52); Boost_104100; UHD_003.<br>004.000-93a49d0<br><br>ALERT 47832442212256 UHDDevice.cpp:469:open: UHD make failed, device type=umtrx,<br>addr=192.168.1.10,name=UmTRX,serial=13<br>
ALERT 47832442212256 runTransceiver.cpp:95:main: Transceiver exiting...<br><br><b>EMERG 1104513344 OpenBTS.cpp:134:startTransceiver: Transceiver quit with status<br>256. Exiting.</b><br><br></div>
</blockquote></div>
</div></blockquote></div></blockquote></div>