network support on 4.0 from EPEL

[Jerry Geis]

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

[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  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

[Jerry Geis]

On Wed, Apr 10, 2019 at 1:41 PM Luke Short  wrote:
> 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  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

Hi Luke,

thanks - actually have selinux disabled in the config file.
These are the packages installed from EPEL
wine-ms-sans-serif-fonts-4.0-2.el7.noarch
wine-cms-4.0-2.el7.x86_64
wine-filesystem-4.0-2.el7.noarch
wine-openal-4.0-2.el7.x86_64
wine-symbol-fonts-4.0-2.el7.noarch
wine-capi-4.0-2.el7.x86_64
wine-twain-4.0-2.el7.x86_64
wine-fixedsys-fonts-4.0-2.el7.noarch
wine-pulseaudio-4.0-2.el7.x86_64
wine-marlett-fonts-4.0-2.el7.noarch
wine-wingdings-fonts-4.0-2.el7.noarch
wine-desktop-4.0-2.el7.noarch
wine-courier-fonts-4.0-2.el7.noarch
wine-common-4.0-2.el7.noarch
wine-ldap-4.0-2.el7.x86_64
wine-small-fonts-4.0-2.el7.noarch
wine-tahoma-fonts-4.0-2.el7.noarch
wine-system-fonts-4.0-2.el7.noarch
wine-core-4.0-2.el7.x86_64
wine-systemd-4.0-2.el7.noarch
wine-alsa-4.0-2.el7.x86_64
wine-fonts-4.0-2.el7.noarch
wine-4.0-2.el7.x86_64

May take a couple to look at the dependency list. I'm on it.

Jerry

[Jerry Geis]

On Wed, Apr 10, 2019 at 1:41 PM Luke Short  wrote:
> 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  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

One package listed that I do not have is nss-mdns  ? That seems network
related.

yum provides "*/nss-mdns*"
results in nothing.

I am using CentOS 7 from EPEL.

Thoughts ?

Jerry

[Luke Short]

Hey Jerry,

My package list is currently biased towards Fedora so some packages may not
be available on RHEL/CentOS. My other recommendations would be to try using
a new/clean Wine prefix and different applications. If you continue to have
problems you may have better luck asking for help in the WineHQ Forums
https://forum.winehq.org/.

Sincerely,
    Luke Short

On Wed, Apr 10, 2019 at 1:57 PM Jerry Geis  wrote:
> On Wed, Apr 10, 2019 at 1:41 PM Luke Short  wrote:
> > 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  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
>
> One package listed that I do not have is nss-mdns  ? That seems network
> related.
>
> yum provides "*/nss-mdns*"
> results in nothing.
>
> I am using CentOS 7 from EPEL.
>
> Thoughts ?
>
> Jerry

[André Hentschel]

Am 10.04.19 um 20:03 schrieb Luke Short:
> On Wed, Apr 10, 2019 at 1:57 PM Jerry Geis <[e-mail] > wrote:
>     On Wed, Apr 10, 2019 at 1:41 PM Luke Short <[e-mail] > wrote:
>         On Wed, Apr 10, 2019 at 1:18 PM Jerry Geis <[e-mail] > 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

https://wiki.winehq.org/FAQ#Failed_to_use_ICMP_.28network_ping.29.2C_this_re...

[Jerry Geis]

Actually - has nothing to do with my application. Running the command:

wine iexplore.exe

pops up but no network activity.
Thoughts?

Jerry