Hi there.. I''ve been all day trying to figure it out how to connect my Dom0 to the interntet, or at least conect to Dom0 this is my configuration, using xen-4 Dom0 Only ethernet connected to internet ( public IP, dhcp ) eth0 Link encap:Ethernet HWaddr 00:21:86:94:c5:c0 inet addr:x.x.x.x Bcast:0.0.0.0 Mask:255.255.252.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18396 errors:0 dropped:0 overruns:0 frame:0 TX packets:4999 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:7944236 (7.5 MiB) TX bytes:513066 (501.0 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) peth0 Link encap:Ethernet HWaddr 00:21:86:94:c5:c0 UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:18627 errors:0 dropped:0 overruns:0 frame:0 TX packets:5017 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8216636 (7.8 MiB) TX bytes:514436 (502.3 KiB) Interrupt:154 Base address:0x6000 ubuntu904 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:12 errors:0 dropped:0 overruns:0 frame:0 TX packets:4481 errors:0 dropped:962 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:336 (336.0 B) TX bytes:269718 (263.3 KiB) netwarrior xen # iptables -nL Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination netwarrior xen # brctl show bridge name bridge id STP enabled interfaces eth0 8000.00218694c5c0 no peth0 ubuntu904 vif = [ ''mac=00:16:3E:52:CB:78, bridge=eth0, vifname=ubuntu904'' ] Domu Config root@ubuntu904:/etc/network# brctl show bridge name bridge id STP enabled interfaces root@ubuntu904:/etc/network# iptables -nL Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination root@ubuntu904:/etc/network# ifconfig eth0 Link encap:Ethernet direcci��nHW 00:16:3e:52:cb:78 Direc. inet:192.168.10.10 Difus.:192.168.10.255 M��sc:255.255.255.0 ACTIVO DIFUSI��N FUNCIONANDO MULTICAST MTU:1500 M��trica:1 Paquetes RX:6487 errores:0 perdidos:0 overruns:0 frame:0 Paquetes TX:12 errores:0 perdidos:0 overruns:0 carrier:0 colisiones:0 long.colaTX:1000 Bytes RX:299550 (299.5 KB) TX bytes:504 (504.0 B) Interrupci��n:245 root@ubuntu904:/etc/network# netstat -nr Tabla de rutas IP del n��cleo Destino Pasarela Genmask Indic MSS Ventana irtt Interfaz 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.10.1 0.0.0.0 UG 0 0 0 eth0 Still cannot ping each other, added a second ethernet (eth1) to dom0, and configured it as 192.198.10.1 , added to the bridge interfase, and cannot ping either from DomU, removed ir from the bridge and same behavior, now I removed eth1 from dom0 Thanks in advance Best Regards _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10-07-05 09:26 PM, Net Warrior wrote:> Hi there.. > > I''ve been all day trying to figure it out how to connect my Dom0 to the > interntet, or at least conect to Dom0 > this is my configuration, using xen-4 > > Dom0 > Only ethernet connected to internet ( public IP, dhcp ) > > eth0 Link encap:Ethernet HWaddr 00:21:86:94:c5:c0 > inet addr:x.x.x.x Bcast:0.0.0.0 Mask:255.255.252.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:18396 errors:0 dropped:0 overruns:0 frame:0 > TX packets:4999 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:7944236 (7.5 MiB) TX bytes:513066 (501.0 KiB) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > peth0 Link encap:Ethernet HWaddr 00:21:86:94:c5:c0 > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > RX packets:18627 errors:0 dropped:0 overruns:0 frame:0 > TX packets:5017 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:8216636 (7.8 MiB) TX bytes:514436 (502.3 KiB) > Interrupt:154 Base address:0x6000 > > ubuntu904 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > RX packets:12 errors:0 dropped:0 overruns:0 frame:0 > TX packets:4481 errors:0 dropped:962 overruns:0 carrier:0 > collisions:0 txqueuelen:32 > RX bytes:336 (336.0 B) TX bytes:269718 (263.3 KiB) > > netwarrior xen # iptables -nL > Chain INPUT (policy ACCEPT) > target prot opt source destination > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > > netwarrior xen # brctl show > bridge name bridge id STP enabled interfaces > eth0 8000.00218694c5c0 no peth0 > ubuntu904 > > vif = [ ''mac=00:16:3E:52:CB:78, bridge=eth0, vifname=ubuntu904'' ] > > Domu Config > > > root@ubuntu904:/etc/network# brctl show > bridge name bridge id STP enabled interfaces > root@ubuntu904:/etc/network# iptables -nL > Chain INPUT (policy ACCEPT) > target prot opt source destination > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > > root@ubuntu904:/etc/network# ifconfig > eth0 Link encap:Ethernet direcci��nHW 00:16:3e:52:cb:78 > Direc. inet:192.168.10.10 Difus.:192.168.10.255 M��sc:255.255.255.0 > ACTIVO DIFUSI��N FUNCIONANDO MULTICAST MTU:1500 M��trica:1 > Paquetes RX:6487 errores:0 perdidos:0 overruns:0 frame:0 > Paquetes TX:12 errores:0 perdidos:0 overruns:0 carrier:0 > colisiones:0 long.colaTX:1000 > Bytes RX:299550 (299.5 KB) TX bytes:504 (504.0 B) > Interrupci��n:245 > > root@ubuntu904:/etc/network# netstat -nr > Tabla de rutas IP del n��cleo > Destino Pasarela Genmask Indic MSS Ventana irtt Interfaz > 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 0.0.0.0 192.168.10.1 0.0.0.0 UG 0 0 0 eth0 > > > Still cannot ping each other, added a second ethernet (eth1) to dom0, > and configured it as 192.198.10.1 , added to the > bridge interfase, and cannot ping either from DomU, removed ir from the > bridge and same behavior, now I removed eth1 from dom0 > > Thanks in advance > Best RegardsI''m not sure if this will help, as this was written for CentOS. I also had a heck of a time sorting out networking in Xen, so I wrote this little tutorial. http://wiki.alteeve.com/index.php/Networking_in_Xen -- Digimer E-Mail: linux@alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jul 6, 2010 at 8:26 AM, Net Warrior <netwarrior863@gmail.com> wrote:> Dom0 > Only ethernet connected to internet ( public IP, dhcp ) > > eth0 Link encap:Ethernet HWaddr 00:21:86:94:c5:c0 > inet addr:x.x.x.x Bcast:0.0.0.0 Mask:255.255.252.0> vif = [ ''mac=00:16:3E:52:CB:78, bridge=eth0, vifname=ubuntu904'' ]> root@ubuntu904:/etc/network# ifconfig > eth0 Link encap:Ethernet direcci��nHW 00:16:3e:52:cb:78 > Direc. inet:192.168.10.10 Difus.:192.168.10.255 M��sc:255.255.255.0How did you setup networking on domU? IF, like you said: - eth0 on dom0 is configured via DHCP - domU is on eth0 bridge Then domU should be configured using DHCP as well. It should end up in the SAME network address as dom0, AND have the same DNS/gateway parameters. In other words, domU will behave like ANOTHER physical host on the same network as dom0. You''ve masked out dom0''s IP address, which makes it harder for those who want to help. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 07/06/10 01:50, Fajar A. Nugraha wrote:> On Tue, Jul 6, 2010 at 8:26 AM, Net Warrior <netwarrior863@gmail.com> wrote: > >> Dom0 >> Only ethernet connected to internet ( public IP, dhcp ) >> >> eth0 Link encap:Ethernet HWaddr 00:21:86:94:c5:c0 >> inet addr:x.x.x.x Bcast:0.0.0.0 Mask:255.255.252.0 >> > >> vif = [ ''mac=00:16:3E:52:CB:78, bridge=eth0, vifname=ubuntu904'' ] >> > >> root@ubuntu904:/etc/network# ifconfig >> eth0 Link encap:Ethernet direcci��nHW 00:16:3e:52:cb:78 >> Direc. inet:192.168.10.10 Difus.:192.168.10.255 M��sc:255.255.255.0 >> > How did you setup networking on domU? > > IF, like you said: > - eth0 on dom0 is configured via DHCP > - domU is on eth0 bridge > > Then domU should be configured using DHCP as well. It should end up in > the SAME network address as dom0, AND have the same DNS/gateway > parameters. In other words, domU will behave like ANOTHER physical > host on the same network as dom0. > > You''ve masked out dom0''s IP address, which makes it harder for those > who want to help. > >Well, no luck yet. root@ubuntu904:~# dhclient Internet Systems Consortium DHCP Client V3.1.1 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/00:21:86:94:c5:c0 Sending on LPF/eth0/00:21:86:94:c5:c0 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 No DHCPOFFERS received. No working leases in persistent database - sleeping. Dom0 netwarrior xen # ifconfig eth0 Link encap:Ethernet HWaddr 00:21:86:94:c5:c0 inet addr:186.18.132.141 Bcast:0.0.0.0 Mask:255.255.252.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1228339 errors:0 dropped:0 overruns:0 frame:0 TX packets:16369 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:65589099 (62.5 MiB) TX bytes:1537751 (1.4 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) peth0 Link encap:Ethernet HWaddr 00:21:86:94:c5:c0 UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:1228529 errors:0 dropped:0 overruns:0 frame:0 TX packets:16428 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:82800527 (78.9 MiB) TX bytes:1542343 (1.4 MiB) Interrupt:154 Base address:0x6000 ubuntu904 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:5 errors:0 dropped:0 overruns:0 frame:0 TX packets:2471 errors:0 dropped:924 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:1640 (1.6 KiB) TX bytes:148260 (144.7 KiB) Firewall is open in both, Dom0 and DomU. Thanks for your time and support Regards _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jul 6, 2010 at 8:51 PM, Net Warrior <netwarrior863@gmail.com> wrote:>> IF, like you said: >> - eth0 on dom0 is configured via DHCP >> - domU is on eth0 bridge >> >> Then domU should be configured using DHCP as well. It should end up in >> the SAME network address as dom0, AND have the same DNS/gateway >> parameters. In other words, domU will behave like ANOTHER physical >> host on the same network as dom0.> Well, no luck yet.> Dom0 > netwarrior xen # ifconfig > eth0 Link encap:Ethernet HWaddr 00:21:86:94:c5:c0 > inet addr:186.18.132.141 Bcast:0.0.0.0 Mask:255.255.252.0> ubuntu904 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1Okay, lets''s try some experiments. First, make sure that /proc/sys/net/ipv4/ip_forward is set to 1 on dom0. Next, your dom0 is using 186.18.132.141, with netmask of 255.255.252.0. Therefore, your domU IP address should also be in that IP range. Try using static configuration on domU first, something like 186.18.132.142 (ping from dom0 first to make sure the address is unused). Then test pinging dom0 -> domU and domU -> dom0. If it doesn''t work, while pinging, do a "tcpdump -n -i eth0 host 186.18.132.142" on both dom0 and domU. That should at least give some idea of what''s going on. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 07/06/10 14:21, Fajar A. Nugraha wrote:> On Tue, Jul 6, 2010 at 8:51 PM, Net Warrior <netwarrior863@gmail.com> wrote: > >>> IF, like you said: >>> - eth0 on dom0 is configured via DHCP >>> - domU is on eth0 bridge >>> >>> Then domU should be configured using DHCP as well. It should end up in >>> the SAME network address as dom0, AND have the same DNS/gateway >>> parameters. In other words, domU will behave like ANOTHER physical >>> host on the same network as dom0. >>> > >> Well, no luck yet. >> > >> Dom0 >> netwarrior xen # ifconfig >> eth0 Link encap:Ethernet HWaddr 00:21:86:94:c5:c0 >> inet addr:186.18.132.141 Bcast:0.0.0.0 Mask:255.255.252.0 >> > >> ubuntu904 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff >> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 >> > Okay, lets''s try some experiments. > First, make sure that /proc/sys/net/ipv4/ip_forward is set to 1 on dom0. > Next, your dom0 is using 186.18.132.141, with netmask of > 255.255.252.0. Therefore, your domU IP address should also be in that > IP range. Try using static configuration on domU first, something like > 186.18.132.142 (ping from dom0 first to make sure the address is > unused). Then test pinging dom0 -> domU and domU -> dom0. If it > doesn''t work, while pinging, do a "tcpdump -n -i eth0 host > 186.18.132.142" on both dom0 and domU. That should at least give some > idea of what''s going on. > >Sorry for the delay, had some personal issues. Well, after all I had some issues with my router which I was able to solve, now I can connect the DomU to internet via dhcp as you mentioned before. Thanks for your time and support!!! Regards _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users