Displaying 20 results from an estimated 300 matches similar to: "Server with 2 Nics (continuation)"
2014 Aug 17
1
Centos 7 and Network/Bridges
Hi all,
I'm a little bit confused about networking in Centos 7: I've copied my
bridge setup from a Centos 6 for KVM networking to Centos 7. I changed
the interface name to the new schema and I had expect that it would
work.
But:
The Bridges didn't came up with the following log message:
"Error: Device 'br61' is waiting for slaves before proceeding with
activation"
2010 Mar 16
2
Unable to remove interface (5.4)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
So here is my problem: I'm unable to remove an interface on CentOS 5.4
(/etc/init.d/network restart keeps enabling it again)
Background:
The system had several interfaces set
(eth0 eth0.6 eth0.7 eth0.8)
1.) I added a test interface...eth0.9
2.) but later deleted the /etc/sysconfig/network-scripts/ifcfg-eth0.9
file (since i no longer needed it)
2008 Dec 12
0
xend nothing to flush, waiting for peth0 to negotiate
Hi,
I would like to ask concerning problems after installing xen 3.3 on Centos
5.2
I use 2.6.18.8-xen (xen3.3.1 testing - installing with mercurial). After
done with make world and make install, I did mkinitrd and placing it in
/boot
changing the grub and reboot.. succeded
I do not install libvirt and the domUs from the previous xen 3.0 (built-in
Centos 5.2) are NOT able to start :
[root@wing
2013 Jun 08
0
xen-4 dom0 bridge failed to bring up eth1
Hallo,
I have running xen-4.2/linux-3.8 (compiled) on any hosts.
- dell pe r720: drac, eth0-3:igb squeeze -> boot_xen:ok net:ok bridge:ok
- dell pe R620: drac=eth0, eth1-3:tg3 wheezy -> boot_xen:ok net:ok
bridge:fail
So i running "xend start" (or "xenbridges start")
on my patient (R620 with broadcom tg3)
network will be lost:
RTNETLINK answers: File exists
2008 Apr 02
1
Strange TCP-Problem with GPL PV 0.8.8
Hi all,
I have a strange problem with GPL PV 0.8.8 (0.6.4 did work).
On my 2nd vif I cannot establish TCP connections. The 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
2010 Nov 18
2
How to know which interface DomU sees the Vif device
Is there a way to dinamically know on which network interface domU sees
the Vif Dom0 "gives" to them.
Ex:
on Dom0: Vifname: vif111.0
on DomU: vif111.0 on network interface : eth0
Best Regards,
Diego Dias
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
2011 Oct 17
1
Extending flow control into the vm
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.
2010 Aug 20
1
smbd version 3.5.4-62.fc13 can NOT bind to IPv4 endpoint( 0.0.0.0:445 ), but it bind to IPv6 endpoint ( :::445 )
# smbd -Fi -d 2
smbd version 3.5.4-62.fc13 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
uid=0 gid=0 euid=0 egid=0
rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
Processing section "[homes]"
Processing section
2007 May 06
0
peth1 not created on boot, now what?
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
2007 Mar 20
0
Resolved | peth1: received packet with own address as source address
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 more than one dom0 on your
2007 Feb 26
0
Xen network bridge questions (using network configuration tools provided by distribution)
Hi list!
I''m trying to figure out a way to use network configuration scripts provided
by the distribution to manage network/bridge configuration with xen..
This means I dont''t want use xen "network-bridge" (or any other) script at
all, because they are a bit limited in functionality.
I want to setup VLAN interfaces with the scripts/tools provided by the
2009 Jun 17
7
Can''t get guest domain network working!
Hi, there:
I have installed xen(2.6.18.8-xen) and had
successfully started domU guests (one or two) from dom0. However, I am
not able to start the network for domU machines.
Following is the information from my linux box.
After the it is started:
$ 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
2008 May 09
1
no network to DomU in Ubuntu Hardy
Hi,
I just installed Xen in Ubuntu Hardy.
DomU is not accessible either from Dom0 or external network.
I used default set up network-bridge/vif-bridge from xend-conf.sxp.
Bridge has got default name eth1 which is my default ethernet interface.
Before creating DomU:
root@jaguar-0:/home/longina# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0
2009 May 14
2
Xen with 2 eth interface
hello,
I want to configure 2 interface like this
eth0 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
2019 Oct 08
4
Dovecot v2.3.8 released
https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz.sig
Binary packages in https://repo.dovecot.org/
Changes
+ Added mail_delivery_started and mail_delivery_finished events, see
https://doc.dovecot.org/admin_manual/list_of_events/ for details.
+ dsync-replication: Don't replicate users who have "noreplicate" extra
field in
2019 Oct 08
4
Dovecot v2.3.8 released
https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz.sig
Binary packages in https://repo.dovecot.org/
Changes
+ Added mail_delivery_started and mail_delivery_finished events, see
https://doc.dovecot.org/admin_manual/list_of_events/ for details.
+ dsync-replication: Don't replicate users who have "noreplicate" extra
field in
2013 May 06
1
Iptables issue on a PV Debian 7.0 host
Howdy,
I have a strange issue,
first some back story,
I failed to upgrade from Debian 6.0 to 7.0 and had to do a fresh install
of 7.0
I had a few PV''s and a Windows 7 VM on this system.
they still work for the most part
for the router I have the following issue that I am not able to reproduce
on the other PV''s
root@router:/home/kd5lct# iptables --list
libkmod: ERROR
2010 Feb 15
0
Re: pv_ops kernel and network problems (checksumoffloading?)
Hi,
I found this mail about network problems in the archive.
I think I have the same network problems with a routing (with or without
NAT) domU connected by two network bridges.
The dom0 logs thousands of following messages:
--
Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet
--
and all outgoing TCP packets have wrong TCP checksums (traced on another
machine on the
2008 Feb 19
0
Bridge Network route Dom0 through a DomU?
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 gateway is set to the local network IP of the
DomU, as is
2009 Jul 16
0
xen-3.0.3-80.el5_3.3 on RHEL 5.3 -- peth0 and xenbr0 don''t exist
Has anyone ran into this issue before?
2 physical nics:
eth0 hooked up to 10.175.8.0/21
eth1 hooked up to 10.150.8.0/24
Ifconfig -a looks like this:
[root@mgixen1 ~]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:19:B9:F2:1B:C3
inet addr:10.175.8.158 Bcast:10.175.15.255
Mask:255.255.248.0
inet6 addr: fe80::219:b9ff:fef2:1bc3/64 Scope:Link
UP