I have the Oracle version of VBox (VirtualBox-5.0- 5.0.10_104061_fedora22-1.x86_64) and it usually doesn't give any issues, but now (under F23) my Windows 7 guest has no network access. I have the appropriate VBox extension installed, and have shutdown and restarted the guest VM, but to no avail.
My guest network is Bridged on virbr0.
Any hints would be appreciated.
poc
On 12/17/2015 12:55 PM, Patrick O'Callaghan wrote:
I have the Oracle version of VBox (VirtualBox-5.0- 5.0.10_104061_fedora22-1.x86_64) and it usually doesn't give any issues, but now (under F23) my Windows 7 guest has no network access. I have the appropriate VBox extension installed, and have shutdown and restarted the guest VM, but to no avail.
My guest network is Bridged on virbr0.
Any hints would be appreciated.
poc
Hey Patrick, with this post, you opened what I had experienced before - and it was always a pain to resolve.
At the time, it seemed to have to do with the iptables firewall rules, and routing permissions. Unfortunately, I do not recall how I resolved it.
ip forwarding on? did you disable netfilter on bridging in /etc/sysctl.conf?
---
Regards,
Kevin Martin
On Thu, Dec 17, 2015 at 2:08 PM, jd1008 jd1008@gmail.com wrote:
On 12/17/2015 12:55 PM, Patrick O'Callaghan wrote:
I have the Oracle version of VBox (VirtualBox-5.0- 5.0.10_104061_fedora22-1.x86_64) and it usually doesn't give any issues, but now (under F23) my Windows 7 guest has no network access. I have the appropriate VBox extension installed, and have shutdown and restarted the guest VM, but to no avail.
My guest network is Bridged on virbr0.
Any hints would be appreciated.
poc
Hey Patrick, with this post, you opened what I had experienced before - and it was always a pain to resolve.
At the time, it seemed to have to do with the iptables firewall rules, and routing permissions. Unfortunately, I do not recall how I resolved it.
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On Thu, 2015-12-17 at 14:15 -0600, kevin martin wrote:
ip forwarding on? did you disable netfilter on bridging in /etc/sysctl.conf?
I haven't touched either of these, ever, and my current F23 was updated from F22, which came from F21 etc. so any changes should have been visible in rpmnew files.
Of course if the whole iptables thing has changed after some update, how would I know?
poc
On Thu, 17 Dec 2015 20:22:47 +0000 Patrick O'Callaghan wrote:
Of course if the whole iptables thing has changed after some update, how would I know?
Well, somewhere in there the iptables stuff was "replaced" with firewalld. You might want to make sure firewalld is disabled and iptables is enabled so your iptables defs will actually take effect.
On Thu, 2015-12-17 at 15:51 -0500, Tom Horsley wrote:
On Thu, 17 Dec 2015 20:22:47 +0000 Patrick O'Callaghan wrote:
Of course if the whole iptables thing has changed after some update, how would I know?
Well, somewhere in there the iptables stuff was "replaced" with firewalld. You might want to make sure firewalld is disabled and iptables is enabled so your iptables defs will actually take effect.
I haven't edited any iptables rules and don't really want to start now. I'm fine with firewalld as long as it works.
poc
On Thu, 2015-12-17 at 13:08 -0700, jd1008 wrote:
On 12/17/2015 12:55 PM, Patrick O'Callaghan wrote:
I have the Oracle version of VBox (VirtualBox-5.0- 5.0.10_104061_fedora22-1.x86_64) and it usually doesn't give any issues, but now (under F23) my Windows 7 guest has no network access. I have the appropriate VBox extension installed, and have shutdown and restarted the guest VM, but to no avail.
My guest network is Bridged on virbr0.
Any hints would be appreciated.
poc
Hey Patrick, with this post, you opened what I had experienced before - and it was always a pain to resolve.
At the time, it seemed to have to do with the iptables firewall rules, and routing permissions. Unfortunately, I do not recall how I resolved it.
I did wonder if it was a firewall issue, but I haven't changed my settings recently. Not that that means anything necessarily.
poc
On 12/17/2015 01:15 PM, Patrick O'Callaghan wrote:
On Thu, 2015-12-17 at 13:08 -0700, jd1008 wrote:
On 12/17/2015 12:55 PM, Patrick O'Callaghan wrote:
I have the Oracle version of VBox (VirtualBox-5.0- 5.0.10_104061_fedora22-1.x86_64) and it usually doesn't give any issues, but now (under F23) my Windows 7 guest has no network access. I have the appropriate VBox extension installed, and have shutdown and restarted the guest VM, but to no avail.
My guest network is Bridged on virbr0.
Any hints would be appreciated.
poc
Hey Patrick, with this post, you opened what I had experienced before - and it was always a pain to resolve.
At the time, it seemed to have to do with the iptables firewall rules, and routing permissions. Unfortunately, I do not recall how I resolved it.
I did wonder if it was a firewall issue, but I haven't changed my settings recently. Not that that means anything necessarily.
poc
Hi Patrick, Once you enable ip forwarding: sudo echo 1 > /proc/sys/net/ipv4/ip_forward
edit the firewall rules to allow in and out from the interfaces virbr0 and the interfaces comprising virbr0. For example:
-A INPUT -i wlp2s0b1 -j ACCEPT . . . -A OUTPUT -i wlp2s0b1 -j ACCEPT
ditto for virbr0
However, you might want to add more restrictions to each rule, such as:
-A INPUT -i wlp2s0b1 -m state --state ESTABLISHED -j ACCEPT
Cheers,
JD
On Thu, 2015-12-17 at 13:43 -0700, jd1008 wrote:
On 12/17/2015 01:15 PM, Patrick O'Callaghan wrote:
On Thu, 2015-12-17 at 13:08 -0700, jd1008 wrote:
On 12/17/2015 12:55 PM, Patrick O'Callaghan wrote:
I have the Oracle version of VBox (VirtualBox-5.0- 5.0.10_104061_fedora22-1.x86_64) and it usually doesn't give any issues, but now (under F23) my Windows 7 guest has no network access. I have the appropriate VBox extension installed, and have shutdown and restarted the guest VM, but to no avail.
My guest network is Bridged on virbr0.
Any hints would be appreciated.
poc
Hey Patrick, with this post, you opened what I had experienced before - and it was always a pain to resolve.
At the time, it seemed to have to do with the iptables firewall rules, and routing permissions. Unfortunately, I do not recall how I resolved it.
I did wonder if it was a firewall issue, but I haven't changed my settings recently. Not that that means anything necessarily.
poc
Hi Patrick, Once you enable ip forwarding: sudo echo 1 > /proc/sys/net/ipv4/ip_forward
I checked and it's already enabled.
edit the firewall rules to allow in and out from the interfaces virbr0 and the interfaces comprising virbr0. For example:
-A INPUT -i wlp2s0b1 -j ACCEPT . . . -A OUTPUT -i wlp2s0b1 -j ACCEPT
ditto for virbr0
However, you might want to add more restrictions to each rule, such as:
-A INPUT -i wlp2s0b1 -m state --state ESTABLISHED -j ACCEPT
Thanks, but I solved it by changing from Bridged to NAT networking and it all started working. I may even have had it set that way before but I haven't looked at it literally in years so who knows how it got changed.
I appreciate your efforts all the same.
poc
On Thu, Dec 17, 2015 at 07:55:53PM +0000, Patrick O'Callaghan wrote:
I have the Oracle version of VBox (VirtualBox-5.0- 5.0.10_104061_fedora22-1.x86_64) and it usually doesn't give any issues, but now (under F23) my Windows 7 guest has no network access. I have the appropriate VBox extension installed, and have shutdown and restarted the guest VM, but to no avail.
My guest network is Bridged on virbr0.
I always use NAT, I've never figured out how to make a bridged network function in a VM on VBox.
On Thu, 17 Dec 2015 17:25:21 -0500 Fred Smith wrote:
I always use NAT, I've never figured out how to make a bridged network function in a VM on VBox.
You have to have a physical interface attached to the bridge as well as virtual ones. God alone only knows how you do that with NetworkManager, but with network, you just need to fiddle some of the definitions in the ifcfg files (the bridge definition gets all the physical interface info and the old physical interface config file points to the bridge).
-
Fred Smith -
JD -
kevin martin -
Patrick O'Callaghan -
Tom Horsley