[Bug 795737] New: Use of Class A Private Network space as default
https://bugzilla.novell.com/show_bug.cgi?id=795737 https://bugzilla.novell.com/show_bug.cgi?id=795737#c0 Summary: Use of Class A Private Network space as default Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: P5 - None Component: KVM AssignedTo: kvm-bugs@forge.provo.novell.com ReportedBy: tonysu@su-networking.com QAContact: jdouglas@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Firefox/17.0 For awhile KVM networking was working more or less as expected. Then, connected to a large, public shared network (local library system) and all my VM networking died. Upon further investigation, it seems that the Admins for this large, public shared network changed their address space to use the Default Class A Private Network space using the default subnet mask. The characteristics of this particular configuration is that only one network is possible while maximizing the number of possible Hosts. The effect on KVM and any other type of solution that sets up a real or virtual network "behind" the publicly shared network leading to the internet is that because all networks must share the same address space (because it's the Class A Private Network using the default subnet mask) no routing is possible. Reproducible: Always Steps to Reproduce: No Steps to reproduce should be required, the description should be sufficient and self-explanatory. Actual Results: All KVM networking is killed. Although no one should ever setup a Class A Private Network using the default subnet mask, it should be easy to see that not only is it possible and maybe even likely if the Admins are not sufficiently experienced or knowledgeable. In the interests of minimizing possible network address space collisions and improving the chances that an initial setup would work, perhaps another address space could be considered. Using a default subnet mask, there are 15 possible Class B networks (most using 16, the lowest second octet) while still supporting a multitude of possible addresses. There are even more possible Class C networks (using the default subnet mask) but of course with only 253 possible Host addresses, but is that sufficient? Am recommending only an "Enhancement" priority only because I assume that this problem has not been encountered often yet should be weighed against the serious ramifications when this scenario is encountered. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=795737 https://bugzilla.novell.com/show_bug.cgi?id=795737#c1 Bruce Rogers <brogers@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |brogers@suse.com Resolution| |WORKSFORME --- Comment #1 from Bruce Rogers <brogers@suse.com> 2013-01-03 20:21:32 UTC --- There is some flexibility with the user mode network which is set up by default, or via -net user or -netdev user. See: http://wiki.qemu.org/Documentation/Networking There it shows an example using the 192.168.76.0 network. So I think qemu-kvm already handles your enhancement request. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=795737 https://bugzilla.novell.com/show_bug.cgi?id=795737#c2 Tony Su <tonysu@su-networking.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | --- Comment #2 from Tony Su <tonysu@su-networking.com> 2013-01-04 18:01:30 UTC --- Hello Bruce, I had already found that page and attempted to use the command described there to modify the default virtual network(s), but unsuccessfully. Uncertain whether the problem is my own or not, I've posted for help/comment in a number of forums including the openSUSE Technical Help forums, the QEMU mailing list, my local Linux UG all without resolution (was going to post in a KVM list and maybe a libvirt list as well). Perhaps this is a technical bug rather than User Error, pls review my openSUSE Technical Help Forums post, if my command does not involve a syntax error then this is a bug which which needs to be addressed: https://forums.opensuse.org/english/get-technical-help-here/virtualization/4... Thx. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=795737 https://bugzilla.novell.com/show_bug.cgi?id=795737#c Bruce Rogers <brogers@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kvm-bugs@forge.provo.novell |boyang@suse.com |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=795737 https://bugzilla.novell.com/show_bug.cgi?id=795737#c3 Yang Bo <boyang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |tonysu@su-networking.com --- Comment #3 from Yang Bo <boyang@suse.com> 2013-03-29 06:11:13 UTC --- /usr/bin/qemu-kvm -M pc-0.14 -enable-kvm -m 1140 -smp 4,sockets=4,cores=1,threads=1 -name sles11sp1 -uuid c38a8043-4885-989f-5c78-aa0fabd5d12d -nodefconfig -nodefaults -rtc base=utc -drive file=/mnt/data/images/sles11sp1/disk0.raw,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,bus=pci.0,multifunction=on,addr=0x4.0x0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev user,id=mynet0,net=192.168.100.0/24,dhcpstart=192.168.100.6 -device virtio-net-pci,netdev=mynet0,id=net0,mac=52:54:00:54:94:72,bus=pci.0,multifunction=on,addr=0x3.0x0 -usb -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x5.0x0 -sdl The command works for me. The legacy command line may not work. you have to match -netdev with -device. Then slirp works. Can you try it this way and see if it works? Then we probably can close this bug. :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=795737 https://bugzilla.novell.com/show_bug.cgi?id=795737#c4 --- Comment #4 from Yang Bo <boyang@suse.com> 2013-05-13 08:28:24 UTC --- ping -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=795737 https://bugzilla.novell.com/show_bug.cgi?id=795737#c5 Jason Douglas <jdouglas@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED InfoProvider|tonysu@su-networking.com | Resolution| |NORESPONSE --- Comment #5 from Jason Douglas <jdouglas@suse.com> 2013-07-17 07:09:57 MDT --- No response since March. Please reopen the bug if you can provide the requested information. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com