Xen users - Apr 2008 - Not sure if my bridge is the problem or my firewall

I''m running Xen and created a virtual os called Domain-1.  So now I
have two
systems, Domain-0(dom0) and Domain-1(dom1), both running fedora 8.  I only
have 1 ethernet device eth0.  However, for some reason, my internet
doesn''t
work in Domain-1.  

My output for route -n on Domain-0 is: 
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0
virbr0
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0

My output for route -n on Domain-1 is:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.122.0     0.0.0.0         255.255.255.0   U     0      0        0
eth0
169.254.0.0        0.0.0.0         255.255.0.0        U    0      0        0
eth0

eth0 is running dhcp
I also have a linksys router with an ip address of 192.168.1.1, that router
is running dhcp.  So 192.168.1.1 is my gateway to the internet.  So I tried
changing domU''s gateway to 192.168.1.1 with

route add default gw 192.168.1.1 eth0
but I get this error message:
SIOCADDRT: No such process

Any ideas guys?  I just started using Xen, well hehe, just started using
linux after using windows all my life, so I''m new to the scene, but
I''m very
thirsty for knowledge.  I''m been learning tons of stuff every day about
linux, so if you can, help me out with a solution, and if you have time,
explain the solution so that I could learn.  Thanks.  Also, I''m posted
ipfconfig -a from Dom0 and the ifcfg-eth0 from Dom0 right below just in case
you guys need it.

ipconfig -a Dom0

eth0      Link encap:Ethernet  HWaddr 00:18:F3:75:E7:72  
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::218:f3ff:fe75:e772/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:362 errors:0 dropped:0 overruns:0 frame:0
          TX packets:216 errors:0 dropped:0 overruns:0 carrier:1
          collisions:0 txqueuelen:1000 
          RX bytes:134586 (131.4 KiB)  TX bytes:32756 (31.9 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:6695 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6695 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:11633574 (11.0 MiB)  TX bytes:11633574 (11.0 MiB)

tap0      Link encap:Ethernet  HWaddr 02:7D:DB:72:EA:C0  
          inet6 addr: fe80::7d:dbff:fe72:eac0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:51 errors:0 dropped:0 overruns:0 frame:0
          TX packets:302 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:6251 (6.1 KiB)  TX bytes:17106 (16.7 KiB)

tmpbridge Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
          BROADCAST MULTICAST  MTU:1500  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)

vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:295 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

virbr0    Link encap:Ethernet  HWaddr 02:7D:DB:72:EA:C0  
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:51 errors:0 dropped:0 overruns:0 frame:0
          TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:5537 (5.4 KiB)  TX bytes:7375 (7.2 KiB)

[root@localhost trist007]# tail /etc/sysconfig/network-scripts/ifcfg-eth0
# Attansic Technology Corp. L1 Gigabit Ethernet Adapter
DEVICE=eth0
TYPE=Ethernet
ONBOOT=yes
USERCTL=no
BOOTPROTO=dhcp
PEERDNS=no
HWADDR=00:18:F3:75:E7:72
IPV6INIT=no

thanks again, let me know if you guys need anymore info.


-- 
View this message in context:
http://www.nabble.com/Not-sure-if-my-bridge-is-the-problem-or-my-firewall-tp16530281p16530281.html
Sent from the Xen - User mailing list archive at Nabble.com.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun, Apr 06, 2008 at 02:49:43PM -0700, trist007
wrote:
> 
> I''m running Xen and created a virtual os called Domain-1.  So now
I have two
> systems, Domain-0(dom0) and Domain-1(dom1), both running fedora 8.  I only
> have 1 ethernet device eth0.  However, for some reason, my internet
doesn''t
> work in Domain-1.  
> 
> My output for route -n on Domain-0 is: 
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0
eth0
> 192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0
> virbr0
> 0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0
eth0
You''re using the wrong bridge, one created by libvirtd. Either define
the correct bridge in your domU configuration, or stop libvirtd and
prevent it from running:

# service libvirtd stop
# chkconfig libvirtd off

You''ll have to shutdown and restart domU.

-- 
lfr
0/0


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users