← Back to team overview

gufw-developers team mailing list archive

[Bug 424631] [NEW] Gufw not allowing Qemu Guest's packets (tun/tap)

 

Public bug reported:

While set up a tun/tap network with Ubuntu as host and lfslivecd as
guest in Qemu, I got some problem. Here is the commands I used,

Ubuntu(host):
$ sudo qemu -cdrom lfslivecd -boot d -kernel-kqemu -m 512 -net nic -net tap &
$ sudo ifconfig tap0 192.168.10.1
$ sudo sysctl -w net.ipv4.ip_forward=1
$ sudo iptables -t nat -A POSTROUTING -j MASQUERADE

lfslivecd(guest):
$ ifconfig eth0 192.168.10.2
$ route add default gw 192.168.10.1

Both host and guest pinging each other properly.. but problem occurs
when I tried to ping opendns's default servers from lfslivecd.

lfslivecd(guest):
$ ping -c 3 208.67.222.222
3 packets transmitted, 0 packets received, 100% packet loss

After disabling 'gufw', everything worked. And I added opendns's
nameservers in resolv.conf

lfslivecd(guest):
$ cat > resolv.conf
nameserver 208.67.222.222
nameserver 208.67.220.220

It will be helpful if someone can write a rule to accept packets to go
to Guest Instances in the default Gufw rules setup. Is accepting packets
for Guest's, a security concern?

** Affects: gui-ufw
     Importance: Undecided
         Status: New


** Tags: iptables masquerade qemu

-- 
Gufw not allowing Qemu Guest's packets (tun/tap)
https://bugs.launchpad.net/bugs/424631
You received this bug notification because you are a member of Gufw
Developers, which is the registrant for Gufw.

Status in GUI for ufw: New

Bug description:
While set up a tun/tap network with Ubuntu as host and lfslivecd as guest in Qemu, I got some problem. Here is the commands I used,

Ubuntu(host):
$ sudo qemu -cdrom lfslivecd -boot d -kernel-kqemu -m 512 -net nic -net tap &
$ sudo ifconfig tap0 192.168.10.1
$ sudo sysctl -w net.ipv4.ip_forward=1
$ sudo iptables -t nat -A POSTROUTING -j MASQUERADE

lfslivecd(guest):
$ ifconfig eth0 192.168.10.2
$ route add default gw 192.168.10.1

Both host and guest pinging each other properly.. but problem occurs when I tried to ping opendns's default servers from lfslivecd.

lfslivecd(guest):
$ ping -c 3 208.67.222.222
3 packets transmitted, 0 packets received, 100% packet loss

After disabling 'gufw', everything worked. And I added opendns's nameservers in resolv.conf

lfslivecd(guest):
$ cat > resolv.conf
nameserver 208.67.222.222
nameserver 208.67.220.220

It will be helpful if someone can write a rule to accept packets to go to Guest Instances in the default Gufw rules setup. Is accepting packets for Guest's, a security concern?



Follow ups

References