network support on 4.0 from EPEL

[Luke Short]

Hey Jerry,

On RHEL/CentOS, there are SELinux rules to prevent non-root users from
using ping correctly. Try temporarily turning off SELiinux with `sudo
setenforce 0`. Alternatively, you may be missing additional dependencies. I
have an Ansible role I have created for installing Wine and the
suggested/recommended dependencies. You can find the full list of
dependencies that are recommended to install in the "wine_dependencies"
YAML dictionary here
<https://github.com/ekultails/ansible_role_wine/blob/extra_dependencies/vars/RedHat.yml>.
If you are familiar with Ansible automation and git, you can use the role
from that "extra_dependencies" branch to install Wine. Although unlikely,
it could be a packaging issue. The EPEL package was set to use Wine 1.8
(from 2016!) for the longest time and only recently got updated to 4.0. It
does not exactly align with the newer/upstream Fedora packages (which is
unlike most EPEL packages) that are tested since that distribution uses
wine-staging instead of wine-stable. Let us know if you find a solution
that works. Good luck!

Sincerely,
    Luke Short

On Wed, Apr 10, 2019 at 1:18 PM Jerry Geis <jerry.geis at gmail.com> wrote:

> I am using wine from EPEL on CentOS 7.
> My application is running - but I have no network access.
>
> Doing a ping of my address:
>
> wine ping 192.168.1.8
> 0009:err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this
> requires special permissions.
> Pinging 192.168.1.8 [192.168.1.8] with 32 bytes of data:
> PING: transmit failed. General failure.
> ^C0028:fixme:console:CONSOLE_DefaultHandler Terminating process 8 on event
> 0
>
>
> wine ipconfig /all
>
> looks all normal.
>
> Am I missing something to get network access ?
>
> What is my next step?
>
> Thanks
>
> Jerry
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20190410/a80f70c8/attachment.html>