search for: peth1

...th1, vif[x].[x] Following I attach the results, thus you might examine: [root@wing godwing]# /usr/sbin/brctl show bridge name bridge id STP enabled interfaces eth0 8000.00173f0a7a26 no peth0 eth1 8000.0019db3895b4 no peth1 xenbr0 8000.000000000000 no xenbr1 8000.000000000000 no note: I don''t know why eth0 and eth1 become the bridge??!! The xenbr0 and xenbr1 I built it with brctl addbr, but it won''t bridge to eth0. I still can connect to inet (LAN) with it. [root@wing...

...3rd IP packet (ACK from XEN-Image) is not forwarded by XEN/DOM0-Bridge. If I boot Windows without /GPLPV option, everything works fine. I did some investigation and found out that the packages arrive differently if GPLPV is enabled. "br_inet" is a bridge connected to the DSL router via peth1. With /GPLPV: iptables log: IN=br_inet OUT=br_inet PHYSIN=tap3 PHYSOUT=peth1 SRC=10.10.11.250 DST=209.85.129.99 LEN=40 TOS=0x00 PREC=0x00 TTL=128 ID=465 DF PROTO=TCP SPT=1050 DPT=80 WINDOW=65535 RES=0x00 ACK URGP=0 => Those packets are never forwarded to peth1. To be sure I verified this by...

...Genmask Flags MSS Window irtt Iface 0.0.0.0 194.95.57.33 0.0.0.0 UG 0 0 0 eth1 194.95.57.32 0.0.0.0 255.255.255.224 U 0 0 0 eth1 3 packets transmitted, 3 received, 0% packet loss, time 1998ms start bridge=eth1 Waiting for peth1 to negotiate link...........(link isnt in running state) Failed to bring up eth1. bridge name bridge id STP enabled interfaces eth1 8000.90b11c208db6 no peth1 BROADCAST MULTICAST MTU:1500 Metric:1 Kernel IP routing table Destination...

If you get a lot of those messages and you don''t want them: peth1: received packet with own address as source address or peth0: received packet with own address as source address This is the way I found to solve this problem on Debian maybe someone can post more information about other distribution like suse or redhat... This problem will occur if you have mor...

Here is the situation. I have a xen system with 2 drives setup in a RAID1. I pulled one drive and put it into an identical server. Now, when I boot up the new server, peth1 is not created. [root@dom0 ~]# ifconfig | grep Link eth1 Link encap:Ethernet HWaddr 00:14:38:A7:55:C2 inet6 addr: fe80::214:38ff:fea7:55c2/64 Scope:Link lo Link encap:Local Loopback vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff...

...RX packets:6440 errors:0 dropped:0 overruns:0 frame:0 TX packets:6440 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:55534272 (52.9 MiB) TX bytes:55534272 (52.9 MiB) ////////////Start xend #xend start Nothing to flush. Waiting for peth1 to negotiate link. # ifconfig eth1 Link encap:Ethernet HWaddr 00:A0:C9:D6:65:DB inet addr:XXX.XXX.10.133 Bcast:XXX.XXX.10.255 Mask:255.255.255.0 inet6 addr: fe80::2a0:c9ff:fed6:65db/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX pa...

We have been using Xen as our vm only recently (about a year now). We recently started to look at the tcp flow control that is coming in and out of the VM. Our configuration is that a physical interface on the host, peth1, is connect to vif1.1 by bridge br1, vif1.1 is instantiated as eth1 inside the vm. We have a data source attached to eth1 that over subscribe the data capacity of peth1. Using pcap on all 4 location, we see that flow control is correctly enforced on peth1 but goes no further. Is there a way to e...

...has an ethernet device, but there''s never any response. After digging through the system for a while and comparing it to another system I have that works, I discovered that the bridge appears to only be partially set up on boot. Specifically, it''s empty, and the pethX (in my case peth1) device is missing entirely. I have dredged through the network-bridge script and run through as much of it as I can in my head, it *seems* like the situation I''m encountering should be impossible unless something is failing in an odd manner in the middle of the script. I can''t p...

...ID Mem VCPUs State Time(s) Domain-0 0 1887 2 r-----24.6 root@jaguar-0:/home/longina# brctl show bridge name bridge id STP enabled interfaces eth1 8000.0060085f963e no peth1 After creating DomU''s image and starting it up: xen-create-image --hostname=jaguar --mac=00:16:3e:00:00:04 --ip=10.110.4.201 --force xm create jaguar.cfg root@jaguar-0:/home/longina# xm list Name ID Mem VCPUs State Time(s) Domain-0...

...inet addr:10.0.0.48 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::215:17ff:fe8d:bf1/64 Scope:Link 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 peth1 Link encap:Ethernet HWaddr 00:15:17:8D:0B:F1 inet6 addr: fe80::215:17ff:fe8d:bf1/64 Scope:Link virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 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...

...bridge each VLAN separately, so I can flexibly assign (and manage) specific VLAN''s to domU''s. This does not work with the default xen network-bridge script (the black magic it does seems to fail with VLAN interfaces). Example configuration: peth0.X == xenbrX peth0.Y == xenbrY peth1.Z == xenbrZ peth1.W == xenbrW Default Xen network-bridge script does the following (in addition to other things): 1. Changes the MAC-address of peth0 to FE:FF:FF:FF:FF:FF. If I have another physical interface, peth1, can it have the same MAC address, or does it have to be different? 2. Sets pe...

...th0 for LAN is 172.16.0.3 eth1 for SAN is 192.168.0.13 I want all VM can access to all network my configuration is : (network-script ''network-bridge netdev=eth0'') to have peth0 and I have a peth0 interface (network-script ''network-bridge netdev=eth1'') to have peth1but I don''t have a peth1 interface Can you help me to activate a peth1 interface. Thanks. -- Franck Delmond 6 allée des Chaumes 44250 Saint Brévin les Pins mail : f.delmond@free.fr tel : 02 40 21 83 40 gsm : 06 60 82 17 49 _______________________________________________ Xen-users...

When does vif0.0 get created? Is there some shell magic? I''m trying to figure out how to do a similar peth1/veth1 split for eth1. -- Nicholas Lee http://stateless.geek.nz gpg 8072 4F86 EDCD 4FC1 18EF 5BDD 07B0 9597 6D58 D70C _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I have seen those documents, I did not see anything that indicates how _automatic_ bridge configuration could be enabled with xl. For my specific set up I have two bridges (xenbr0 -> peth0 & xenbr1 -> peth1). If I have to configure this manually with ifcfg scripts I will, but if an automatic method is provided or is possible with xl I'd prefer to use that. -Gene On Thu, Jan 29, 2015 at 4:07 AM, Lars Kurth <lars.kurth.xen at gmail.com> wrote: > Gene, > I think you should find the an...

Situation peth0 = internet peth1 = local private network Dom0 is only configured to use peth1 and works fine as such I have a DomU setup as a NAT box for the local network to the internet and it is functioning as well. DomU is also running a caching DNS and DHCP for the local network The problem I have is DomO''s gatew...

Hi all, it''s happening a strange thing: After I boot the xen dom0 network is unavailable: I have to unload the network modules and load it again ( rmmod / modprobe) and execute a service network restart) This is strange, what do you suggest me to check? Thanks Marco Strullato _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

...cket -- and all outgoing TCP packets have wrong TCP checksums (traced on another machine on the external network) My setup: Private Network -> dom0: peth0 -> eth0(bridge) -> vif1.0 -> domU: eth0 -> routing (with or without NAT) -> eth1 -> dom0: vif1.1 -> eth1(bridge) -> peth1 -> Public Network Packets coming in from peth0 are either dropped (ICMP) by dom0 after routing through domU (see error above) or for TCP, they have wrong checksums. The checksums traced with tcpdump on dom0 eth1 are correct, but the checksums of the same packets traced on another machine on the...

...dr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 b) TX bytes:560 (560.0 b) 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:1786 errors:0 dropped:0 overruns:0 frame:0 TX packets:85 errors:0 dropped:0 overruns:0 carrier:...

...TP enabled interfaces xenbr0 8000.feffffffffff no vif0.0 peth0 xenbr1 8000.feffffffffff no vif0.1 peth1 xenbr2 8000.feffffffffff no vif0.2 peth2 xenbr3 8000.feffffffffff no vif0.3 peth3 xenbr4 800...

...ions:0 txqueuelen:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) The problem is that RX never changes in the ifconfig view and TX only records an increasing amount of dropped packets. The RX bytes and TX bytes remain zero no matter how much traffic is generated by the DomU guest. vif0.1, eth1, peth1 all record increased traffic in ifconfig when my DomU guest is generating network traffic. Any ideas how I can get things working? Alternatively, suggestions on how to track DomU bandwidth usage on OpenSuse 10.3 would also be welcome. j. _______________________________________________ Xen-users...