ConnectPort X2D and XIG Unstable

[Kingsley Hill]

Can I get some help with this?  PLEASE?  (this is a follow up to https://groups.google.com/forum/#!topic/xbee-internet-gateway/9LUXsikBZ8E but I received no response after posting the trace)

ConnectPort X2D with Firmware 2.17.1.0   (Version 82002549_F1 11/05/2013)

Sending nonsense to the ConnectPort X2D causes an infinitely repeating error.  This can also occur if a legitimate (http) request is sent but received out of order or missing some part of the initial address (e.g. ttp://www...)  The only way out is to reboot the ConnectPort. 

I have looked at the xig source and while I find the place in io_kernel where it occurs and where that is called from xmit I can't see how to fix it.  Plus I seem to be missing some libraries for Python to be able to build it in pydev with Eclipse.

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.03.06 20:43:08 =~=~=~=~=~=~=~=~=~=~=~=

#> python xig.py

xig - XBee Internet Gateway (XIG) v1.5.1 starting.
xig.io_kernel - XBee Version = 8067, Series = 8
xig.io_kernel - XBee reliable transmit enabled
xig.io_kernel - Enabling UDP listener on port 5649...
xig.io_kernel - XBee MTU = 256 bytes
xig - Loading and initializing configured session types...
xig - Loading ['HTTPSession'] from http...
xig - Loading ['iDigiDataAutostartSession', 'iDigiDataSession'] from idigi_data...
xig - Loading ['iDigiRCIAutostartSession', 'iDigiRCISession'] from idigi_rci...
xig - Formatting help text...
xig - Starting scheduler...
xig - XIG startup complete, all ready to serve requests.
xig.io_kernel - RECV: 11 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('xig://time\r')
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 1)
xig.xmit - X-API ZigBee TX Status (id = 1)
xig.xmit - GOOD: tx_status (id = 1)
xig.io_kernel - RECV: 39 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('http://www.flingbear.com/amIHere.html\r')
xig.http - successful GET of http://www.flingbear.com/amIHere.html
xig.http - connection closed by remote server
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 2)
xig.xmit - X-API ZigBee TX Status (id = 2)
xig.xmit - GOOD: tx_status (id = 2)
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('u')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('n')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('k')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('n')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('o')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('w')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('n')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('j')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('u')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('n')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('k')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('\r')
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1d4c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1d2c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1c4c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)

...thousands of these lines...  Then I sent ABORT

xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1dec>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1b2c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1e8c>)
xig.io_kernel - RECV: 12 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('xig://abort\r')
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1e8c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1d4c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)

...thousands more ...  Then I sent QUIT

xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1dac>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1bec>)
xig.io_kernel - RECV: 11 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('xig://quit\r')
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1bec>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
...
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1a8c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1f4c>)

ad infinitum...

The only way out is to reboot the ConnectPort X2D