Bugzilla – Bug 155287
Network of dom0 after start of xend not working anymore
Last modified: 2006-06-19 17:38:52 UTC
Hi, please have a look at attached logfile (MAC addresses of eth0/wlan0 changed) I tried this a few times with different versions of xen during the last months with no success. I also tried packages from http://www.suse.de/~garloff/linux/xen/RPMs-100. This happens with fast ethernet eth0 or with wireless wlan0 getting IP address via DHCP. I also tried to add some routes (e.g. the disappeared default route) with no success. After stopping xend and doing "/etc/init.d/network restart" the network although doesn't work like before starting xend.
Created attachment 71253 [details] action log: network before and after starting xend
In yast, on the Network Address Setup page, is the Device Activation set as "At Boot Time" or "On Cable Connection"? Currently, there are problems with "On Cable Connection". Is the firewall on or off? The firewall can get turned back on automatically when network adapters are configured in yast. What physical LAN adapter is eth0 assigned to?
Your assumption, that this has got something to do with the firewall was right! Shutting down the firewall before with "/etc/init.d/SuSEfirewall2* stop" brings back the default-route after the start of xend but the network is still not working. It is neccesary to "chkconfig SuSEfirewall2* off" and reboot to make the network work. The Device activation is at system start. linux1:~ # lspci -v -s 02:08.0 02:08.0 Ethernet controller: Intel Corporation 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller (rev 41) Subsystem: IBM ThinkPad A/T/X Series Flags: bus master, medium devsel, latency 66, IRQ 11 Memory at c0200000 (32-bit, non-prefetchable) [size=4K] I/O ports at 6400 [size=64] Capabilities: [dc] Power Management version 2 linux1:~ # cat /proc/iomem 00000000-0009efff : System RAM 0009f000-0009ffff : reserved 000a0000-000bffff : Video RAM area 000c0000-000cdfff : Video ROM 000ce000-000cefff : Adapter ROM 000cf000-000cffff : Adapter ROM 000e0000-000effff : Extension ROM 000f0000-000fffff : System ROM 00100000-1ff6ffff : System RAM 1ff70000-1ff7dfff : reserved 1ff7e000-1ff7ffff : reserved 1ff80000-1fffffff : reserved 20000000-200003ff : 0000:00:1f.1 50000000-50000fff : 0000:02:00.0 50000000-50000fff : yenta_socket 51000000-51000fff : 0000:02:00.1 51000000-51000fff : yenta_socket c0100000-c01fffff : PCI Bus #01 c0100000-c017ffff : 0000:01:00.0 c0200000-cfffffff : PCI Bus #02 c0200000-c0200fff : 0000:02:08.0 c0200000-c0200fff : e100 c0201000-c02010ff : 0000:02:02.0 c0400000-c07fffff : PCI CardBus #03 c0800000-c0bfffff : PCI CardBus #07 c1200000-c1200fff : pcmcia_socket0 d0000000-dfffffff : 0000:00:00.0 e0000000-ebffffff : PCI Bus #01 e0000000-e1ffffff : 0000:01:00.0 e4000000-e7ffffff : 0000:01:00.0 e8000000-ebffffff : 0000:01:00.0 f0000000-f7ffffff : PCI Bus #02 f0000000-f03fffff : PCI CardBus #03 f0400000-f07fffff : PCI CardBus #07 ff800000-ffffffff : reserved
Apply a minimal set of modifications to the /etc/sysconfig/SuSEfirewall2 config file to allow the firewall to work with xen. Add the bridge e.g. xenbr0 to FW_DEV_EXT or to one where eth0 is referenced. This field can be updated through yast. Set FW_ROUTE to yes. Set FW_ALLOW_CLASS_ROUTING to yes. With these three variables set, I was able to ping out from both dom0 and domU with the firewall on. The "At Boot Time" or "On Cable Connection" configuration of the NIC issues have been addressed in SLES 10 Beta8.