# Issue with java.net module import in Ignition V 8.1.5

**URL:** <https://forum.inductiveautomation.com/t/issue-with-java-net-module-import-in-ignition-v-8-1-5/59496>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [May 12, 2022, 9:51am UTC](https://forum.inductiveautomation.com/t/issue-with-java-net-module-import-in-ignition-v-8-1-5/59496 "2022-05-12T09:51:16Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 13, 2022, 8:12am UTC](https://forum.inductiveautomation.com/t/issue-with-java-net-module-import-in-ignition-v-8-1-5/59496/4 "2022-05-13T08:12:33Z")

</div>

If on Linux and not running as root, use of any ping-like raw packet requires the `CAP_NET_RAW` capability (privilege). You can specify that in the SystemD service file (or override) with the `AmbientCapabilities=CAP_NET_RAW` setting. You can specify multiple capabilities with whitespace. I recommend `AmbientCapabilities=CAP_NET_BIND_SERVICE CAP_NET_RAW`.

---

_[View the full topic](https://forum.inductiveautomation.com/t/issue-with-java-net-module-import-in-ignition-v-8-1-5/59496)._
