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] Query about the vifX.Y interfaces

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Query about the vifX.Y interfaces
From: Colin Coe <CCoe@xxxxxxxxxxxxxxx>
Date: Fri, 23 Dec 2005 07:59:19 +0800
Delivery-date: Fri, 23 Dec 2005 00:02:42 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
Hi all

Really silly question here:  do the vif interfaces require IP addresses?
I'm totally stuck with getting IP traffic to my guest domain, layer 2
traffic (ie ARP queries/responces, broadcasts, etc) is all OK.  Another
question, what is peth0 used for?

Thanks again

CC



Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      251     4 r-----   164.0
vm1                                6      256     2 -b----    22.1


eth0      Link encap:Ethernet  HWaddr 00:14:5E:3C:41:98
          inet addr:x.x.x.114  Bcast:x.x.x.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1063363 errors:0 dropped:0 overruns:0 frame:0
          TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:67975834 (64.8 MiB)  TX bytes:2940 (2.8 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:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1570 (1.5 KiB)  TX bytes:1570 (1.5 KiB)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:1118372 errors:0 dropped:0 overruns:0 frame:0
          TX packets:316786 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:77304672 (73.7 MiB)  TX bytes:88452384 (84.3 MiB)
          Interrupt:77

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:54 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1063363 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2940 (2.8 KiB)  TX bytes:67975834 (64.8 MiB)

vif6.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:73 errors:0 dropped:0 overruns:0 frame:0
          TX packets:785052 errors:0 dropped:446 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4994 (4.8 KiB)  TX bytes:50068779 (47.7 MiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet addr:x.x.x.114  Bcast:x.x.x.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1118600 errors:0 dropped:0 overruns:0 frame:0
          TX packets:316603 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:56218554 (53.6 MiB)  TX bytes:87173370 (83.1 MiB)

(I manually added eth0's IP to xenbr0)
************************************************************************
Bunnings Legal Disclaimer:

1)     This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2)     All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.
************************************************************************


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

<Prev in Thread] Current Thread [Next in Thread>