[qubes-users] Re: Connected to wifi but no ping

2017-11-09 Thread brutellealexandre
On Thursday, 9 November 2017 16:05:14 UTC+1, brutelle...@gmail.com  wrote:
> On Thursday, 9 November 2017 12:28:34 UTC+1, blacklight  wrote:
> > On Thursday, 9 November 2017 04:26:27 UTC, Quewbie_Newbie  wrote:
> > > Hello, 
> > > 
> > > I'm despaired about ever re-opening a web page again on this system ! I 
> > > must have changed something by mistake in the settings and screwed up my 
> > > network configuration. 
> > > 
> > > I think I have re-etablished the global settings alright :
> > > 
> > > UpdateVM = Firewall
> > > ClockVM = Sys-net
> > > Default net = Firewall
> > > 
> > > Can't ping on sys-net even though my wifi connection established 
> > > succesfully...
> > > 
> > > Firmware on the template Fedora a/o sys-net aren't (and can't) be 
> > > installed. 
> > > 
> > > Did the basic troubleshooting methods to reload automatically the wifi 
> > > drivers...
> > > 
> > > Also saw the possibility of permissive PCI but I have the feeling this is 
> > > not the thing to do in my situation (wifi was working find after several 
> > > reboots) and I honestly think I must have changed some basic setting by 
> > > mistake or something...
> > > 
> > > Template for sys-net is Fedora23 and my machine is a Lenovox220.
> > > 
> > > Any help welcome !
> > 
> > did you check if the block icmp requests are unchecked in the firewall 
> > settings of your vms?
> 
> I did and the "allow ICMP" criteria was uncheck for every single VM. So I 
> went now and checked it in order to allow for each of them... Will see how it 
> turns out !

Thank you Blacklight. This actually allowed to do the Fedora update and install 
the update (including firmwares). I hope this network set up will stay stable ! 
I know this is unrevelant to this topic perhaps but it is not recommended to 
not update to higher versions of Fedora (the template is running 23) ? Could I 
have other problems if I don't upgrade ?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/f0352265-f02c-4fb1-a08b-d1f1e4c3b5ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Connected to wifi but no ping

2017-11-09 Thread brutellealexandre
On Thursday, 9 November 2017 12:28:34 UTC+1, blacklight  wrote:
> On Thursday, 9 November 2017 04:26:27 UTC, Quewbie_Newbie  wrote:
> > Hello, 
> > 
> > I'm despaired about ever re-opening a web page again on this system ! I 
> > must have changed something by mistake in the settings and screwed up my 
> > network configuration. 
> > 
> > I think I have re-etablished the global settings alright :
> > 
> > UpdateVM = Firewall
> > ClockVM = Sys-net
> > Default net = Firewall
> > 
> > Can't ping on sys-net even though my wifi connection established 
> > succesfully...
> > 
> > Firmware on the template Fedora a/o sys-net aren't (and can't) be 
> > installed. 
> > 
> > Did the basic troubleshooting methods to reload automatically the wifi 
> > drivers...
> > 
> > Also saw the possibility of permissive PCI but I have the feeling this is 
> > not the thing to do in my situation (wifi was working find after several 
> > reboots) and I honestly think I must have changed some basic setting by 
> > mistake or something...
> > 
> > Template for sys-net is Fedora23 and my machine is a Lenovox220.
> > 
> > Any help welcome !
> 
> did you check if the block icmp requests are unchecked in the firewall 
> settings of your vms?

I did and the "allow ICMP" criteria was uncheck for every single VM. So I went 
now and checked it in order to allow for each of them... Will see how it turns 
out !

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/04c0d52a-8d07-479b-979d-658d1491f9fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Connected to wifi but no ping

2017-11-09 Thread blacklight
On Thursday, 9 November 2017 04:26:27 UTC, Quewbie_Newbie  wrote:
> Hello, 
> 
> I'm despaired about ever re-opening a web page again on this system ! I must 
> have changed something by mistake in the settings and screwed up my network 
> configuration. 
> 
> I think I have re-etablished the global settings alright :
> 
> UpdateVM = Firewall
> ClockVM = Sys-net
> Default net = Firewall
> 
> Can't ping on sys-net even though my wifi connection established 
> succesfully...
> 
> Firmware on the template Fedora a/o sys-net aren't (and can't) be installed. 
> 
> Did the basic troubleshooting methods to reload automatically the wifi 
> drivers...
> 
> Also saw the possibility of permissive PCI but I have the feeling this is not 
> the thing to do in my situation (wifi was working find after several reboots) 
> and I honestly think I must have changed some basic setting by mistake or 
> something...
> 
> Template for sys-net is Fedora23 and my machine is a Lenovox220.
> 
> Any help welcome !

did you check if the block icmp requests are unchecked in the firewall settings 
of your vms?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b8c02715-4e48-4b04-9247-0904b55e2c09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.