WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] network-routing

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] network-routing
From: Christian Witt <christian_witt@xxxxxx>
Date: Wed, 20 Feb 2008 18:54:45 +0100
Delivery-date: Wed, 20 Feb 2008 09:55:15 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.9 (X11/20070801)
Dear Xen-Users,

I use Xen 3.1.0_15042 on my OpenSuSE-10.3-computer. Without starting the
xen-kernel I can connect my second computer via my native computer to
the internet. After starting the xen-kernel the xen-bridge came
automatically up.
How can I configure the xen-bridge or the xen-devices?
I get routing problems:
Feb 20 18:31:36 intel6550 kernel: martian source 217.237.149.142 from
192.168.0.4, on dev eth1
Feb 20 18:31:36 intel6550 kernel: ll header:
00:a0:24:29:5b:25:00:60:b0:67:2a:af:08:00

or on my own firewall-rules:
Feb 20 18:36:46 intel6550 kernel: Forward-Routing: IN=xenbr0 OUT=xenbr0
PHYSIN=peth1 PHYSOUT=vif0.0 SRC=192.168.0.3 DST=217.237.150.205 LEN=60
TOS=0x00 PREC=0x00 TTL=64 ID=35617 DF PROTO=UDP SPT=1060 DPT=53 LEN=40

how can I use routing with started xen-bridge? Every Computer at home
has a fixed / hard IP-address (from the 192.168.0.x net) and only my
internet-computer / gateway (192.168.0.4) has another network-card with
an extern IP-address.

My Interfaces are:
intel6550:~ # ifconfig -a
dsl0      Link encap:Point-to-Point Protocol
          inet addr:x.x.x.x  P-t-P:217.x.x.x  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:215 errors:0 dropped:0 overruns:0 frame:0
          TX packets:250 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:53752 (52.4 Kb)  TX bytes:21311 (20.8 Kb)

eth0      Link encap:Ethernet  HWaddr 00:1A:4D:50:1F:D3
          inet6 addr: fe80::21a:4dff:fe50:1fd3/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:261 errors:0 dropped:0 overruns:0 frame:0
          TX packets:320 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:61308 (59.8 Kb)  TX bytes:40719 (39.7 Kb)
          Interrupt:16 Base address:0xc000

eth1      Link encap:Ethernet  HWaddr 00:A0:24:29:5B:25
          inet addr:192.168.0.4  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::2a0:24ff:fe29:5b25/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:168 errors:0 dropped:0 overruns:0 frame:0
          TX packets:166 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:18737 (18.2 Kb)  TX bytes:17209 (16.8 Kb)

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:42 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2708 (2.6 Kb)  TX bytes:2708 (2.6 Kb)

peth1     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:256 errors:0 dropped:0 overruns:0 frame:0
          TX packets:188 errors:0 dropped:0 overruns:0 carrier:2
          collisions:0 txqueuelen:1000
          RX bytes:25657 (25.0 Kb)  TX bytes:21992 (21.4 Kb)
          Interrupt:20 Base address:0xd000

veth1     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)

veth2     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)

veth3     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)

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:166 errors:0 dropped:0 overruns:0 frame:0
          TX packets:168 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:17209 (16.8 Kb)  TX bytes:18737 (18.2 Kb)

vif0.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          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)

vif0.2    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          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)

vif0.3    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          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)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:32 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4705 (4.5 Kb)  TX bytes:168 (168.0 b)

without any started virtual guests.
I wanted an routing like
<Second Computer>----<Main / Internet computer / Gateway>---<internet>
<192.168.0.3>----<192.168.0.4 and x.x.x.x>----<x.x.x.x>
and inside of the main computer:
<eth1=192.168.0.4>
<eth0=dsl0=x.x.x.x>
<xen-guest=192.168.0.10>
do I need xenbr0 or vif0.0 to vif0.3 or veth0 to veth3?

please help me so that routing works:
-from the second computer to the internet (without xen and xenbr
everything works fine)
-from the xen-guest to the internet (I think this has the same reason)

If you need more information - please ask.

with kindly regards
Christian Witt

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] network-routing, Christian Witt <=