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.
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
and the interfaces comprising virbr0.
-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
-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
I appreciate your efforts all the same.