# Cannot get UDP driver to work **URL:** \ **Category:** Ignition\ **Created:** [April 14, 2011, 2:52pm UTC](https://forum.inductiveautomation.com/t/cannot-get-udp-driver-to-work/2868 "2011-04-14T14:52:15Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Brett\_Yeomans](https://avatars.discourse-cdn.com/v4/letter/b/35a633/32.png) [@Brett\_Yeomans](https://forum.inductiveautomation.com/u/Brett_Yeomans)\ **Post date:** [April 14, 2011, 2:52pm UTC](https://forum.inductiveautomation.com/t/cannot-get-udp-driver-to-work/2868/1 "2011-04-14T14:52:15Z")
I’m trying to get a serial-Ethernet device into Igntion as UDP. The settings seem minimal but I cannot get it function. The same device works in TCP. When I run wireshark I believe I can see the UDP from the converter but immediately I get a ICMP “Destination unreachable (port unreachable)” message, type 3, code 3. I do not have Windows firewall on. Can anyone help with this please. ---
**Author:** ![Travis.Cox](https://avatars.discourse-cdn.com/v4/letter/t/b9bd4f/32.png) [@Travis.Cox](https://forum.inductiveautomation.com/u/Travis.Cox)\ **Post date:** [April 14, 2011, 4:14pm UTC](https://forum.inductiveautomation.com/t/cannot-get-udp-driver-to-work/2868/2 "2011-04-14T16:14:17Z")
Is the device configured to send UDP packets to the Ignition server? ---
**Author:** ![Brett\_Yeomans](https://avatars.discourse-cdn.com/v4/letter/b/35a633/32.png) [@Brett\_Yeomans](https://forum.inductiveautomation.com/u/Brett_Yeomans)\ **Post date:** [April 14, 2011, 4:31pm UTC](https://forum.inductiveautomation.com/t/cannot-get-udp-driver-to-work/2868/3 "2011-04-14T16:31:22Z")
I believe so. Wireshark picks up the UDP going from converter to laptop, then the error message is laptop to converter. It may be something silly but I’ve spent around 4 hours on this without any success. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 14, 2011, 5:06pm UTC](https://forum.inductiveautomation.com/t/cannot-get-udp-driver-to-work/2868/4 "2011-04-14T17:06:15Z")
Do you have the multicast option set to false? ---
**Author:** ![Brett\_Yeomans](https://avatars.discourse-cdn.com/v4/letter/b/35a633/32.png) [@Brett\_Yeomans](https://forum.inductiveautomation.com/u/Brett_Yeomans)\ **Post date:** [April 14, 2011, 9:06pm UTC](https://forum.inductiveautomation.com/t/cannot-get-udp-driver-to-work/2868/5 "2011-04-14T21:06:21Z")
Yes I have had the multicast set to false, I have also had both set to multicast and set the converter to xxx.xxx.xxx.255 Does wireshark indicate that the port is not open? Admittedly the device works in TCP and I believe Inductive Automation are working on a seperate issue that will let me carry on using TCP but I would like to get to the bottom of this. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 14, 2011, 9:23pm UTC](https://forum.inductiveautomation.com/t/cannot-get-udp-driver-to-work/2868/6 "2011-04-14T21:23:58Z")
When configuring it with multicast=false, what address are you using in the IP Address property? ---
**Author:** ![Brett\_Yeomans](https://avatars.discourse-cdn.com/v4/letter/b/35a633/32.png) [@Brett\_Yeomans](https://forum.inductiveautomation.com/u/Brett_Yeomans)\ **Post date:** [April 15, 2011, 9:09am UTC](https://forum.inductiveautomation.com/t/cannot-get-udp-driver-to-work/2868/7 "2011-04-15T09:09:52Z")
With multicast set to false I have IP address 192.168.127.2 Port 4001 (The Moxa device is set to SOcket, UDP, Destination 192.168.127.7 Prt 4001, local listen port 4000). I was hoping the Wireshark message indicated something to someone who knows about these things, it show UDP coming from the converter but the port being unreachable??? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 15, 2011, 3:43pm UTC](https://forum.inductiveautomation.com/t/cannot-get-udp-driver-to-work/2868/8 "2011-04-15T15:43:39Z")
Is 192.168.127.7 the address of the device or the address of the Ignition gateway? With multicast=false, the address should be that of the gateway. ---
**Author:** ![Brett\_Yeomans](https://avatars.discourse-cdn.com/v4/letter/b/35a633/32.png) [@Brett\_Yeomans](https://forum.inductiveautomation.com/u/Brett_Yeomans)\ **Post date:** [April 15, 2011, 4:16pm UTC](https://forum.inductiveautomation.com/t/cannot-get-udp-driver-to-work/2868/9 "2011-04-15T16:16:19Z")
192.168.127.7 is the gateway (laptop) 192.168.127.2 is the Moxa serial to Ethernet converter. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 15, 2011, 6:24pm UTC](https://forum.inductiveautomation.com/t/cannot-get-udp-driver-to-work/2868/10 "2011-04-15T18:24:42Z")
[quote=“Brett Yeomans”]192.168.127.7 is the gateway (laptop) 192.168.127.2 is the Moxa serial to Ethernet converter.[/quote] Well, go ahead and try setting the IP Address property to 192.168.127.7, multicast=false, and the device configured to broadcast 192.168.127.7.