similar to: Centos 6.5 em1 network can not up????

Shorewall 4.5.15 3 Interface setup em1 p3p1 p4p4 ppp0 Hi, Since changing to NetworkManger on Fedora 18 I can no longer connect to the DSL Modem, which is connected to Interface em1. When the NetworkManger brings up the interfaces and ppp0, it no longer assigns an IP to em1. If I have ppp0 disabled and NetworkManger brings up the interfaces, em1 gets an IP of 192.168.1.2. Then when I get

Once upon a time, Lists <lists at benjamindsmith.com> said: > I understand that it's possible to allow the 4 VM guest systems to each have a > "direct" fixed IP address and access the addresses \via the host network > adapter, while the host retains its fixed IP. If you are running NetworkManager (the default), it's not too hard. Here's an example

Hey, I have KVM installed on my Fedora 17 box. I added the network interfaces of the virtual machines to the openvswitch bridge as follows: ____ ____ / VM1\______br0_______/ em1\ \____/ | \____/ | _|_ /VM2\ \____/ virbr0 is the virtual network switch VM1 and VM2 are on the same subnet having tap interfaces vnet0 and vnet1 respectively. em1 is the default

I am running NOX controller with a python script that prints out the destination mac and the source mac for each packet arriving at the now controller and then floods it out. So here's what happening: With em1 connected, all the packets that arrive at em1 are coming to the controller and printing out the details. However, without em1 connected to the OVS, when I have the following setup:

hi everyone I'm having a bit of a puzzle on one centos system, I have four interfaces: nm-team1 10.5.6.100 em1 192.168.2.17 em2 192.168.2.18 p3p3 172.25.12.222 I do: ping 10.5.6.17 -I em1 PING 10.5.6.17 (10.5.6.17) from 192.168.2.17 em1: 56(84) bytes of data. 64 bytes from 10.5.6.17: icmp_seq=1 ttl=64 time=0.367 ms the same for -I em2, for -I em1 and naturally for -I nm-team1 - all good.

Hello everyone I am running into some strange issues when configuring networking interfaces on my physical server running Centos 7.5. Let me give you an overview of what's going on: We have a physical server, running CentOS 7.5. This server has one 4 port NIC and one 2 port NIC and a Dell IDRAC port. The first port of the 4 port NIC, em1, is used for Management traffic. The first port of

Okay you can stop laughing, yes I still have an NT server running for some special software. I've got a new linux machine running Samba version 3.6.23 and am having problems getting it to connect to winXP machines to talk to their shared printers It can join the domain and smbtree and smbclient sort of work. 192.168.4.28 is a windows XP machine NEW#: smbclient -L 192.168.4.28 -U

Hello All, I seem to have run into a bug with the new --bridgeslaves=<INTERFACE> option. It would seem that if I tell the bridge device to use a virtual interface (like bond0) rather than a physical interface (em1/em2) that kickstart completely barfs on it. I have provided my network section below which works fine as long as i don't enable all the bridge content. When the

I'm trying to autoinstall a DELL 9030 desktop with CentOS7 using PXE and Kikstart. I fall in a strange problem (I have several other laptop or desktop using this install process without any problem, kernel and initrd are from a Centos 7.4 iso) - PXE boot start and the desktop load the kernel and the inirtd file - the kernel is booted and at this time the led of the network switch goes down

Hi all, Someone played with kickstart bonding with centos 6.4 ? CentOS 6.4, as upstream now support ifcae bonding in kickstart network section. I've an issue with configuring a second bonding iface in kicstart on CentOS 6.4. The first bonding (bond0) works as espected but the second is not configured during installation. I've a 6 nic server (two for "puclic" network, two for

current setup SIP phone 192.168.1.30 --> linksys wrt54g sveasoft -- INTERNET -- (xl0) Firewall (xl2:172.16.0.50)--> (em1:172.16.0.101) Asterisk problem is RTP stream not oging trouhg from * to sip and vice versa. #1 and asterusk is pushing 192.168.1.30 back to linksys with 172 as return address.... or #2 asterisk trying to get back to me as 192.168 on public internet.. got

Hi, When I initially boot my system, it fails to bring up the network. Once booted, if I run "systemctl restart network.service", or even stop, wait a while, then start, it starts up fine and all is well. I'm running Fedora 19 (updated). I followed the instructions on this page to set up a bridged network: http://wiki.libvirt.org/page/Networking I note however that I did *not*

dear All, I'm facing this routing problem, the setup is actualy part of ltsp, but I think this problem is Centos-specific. The server is a Dell Poweredge R210. The install is standard 6.4, updated. I have one nic facing the public internet: vi /etc/sysconfig/network-scripts/ifcfg-em1 DEVICE=em1 BOOTPROTO=none HWADDR=d4:ae:52:c1:28:2b NM_CONTROLLED=no ONBOOT=yes TYPE=Ethernet

Hello all, I'm wondering if there's any interest in trying to bond em1 and eth0 (respectively wired and wireless interfaces here), and if any, how to do it in CentOS6. I've found this, which could possibly help (but I'm failing yet): http://r.outlyer.net/linux:bonding https://help.ubuntu.com/community/UbuntuBonding Both are dealing w/ ifenslave. Any experience or point of

CentOS 6.2......... Why do the physical interfaces report (correctly) that they're negotiated at 1000Mb/s, but when I `cat /proc/net/bonding/bond0` I get 100Mbps for the member interfaces, and when I ` mii-tool bond0` I get 10Mbps for the bond? ----------------------------------------------------------------------------------------- ethtool em1 Settings for em1: Supported ports: [

Hello, Anybody else run into problems with biosdevname .0.5..0-2 changing names from p2p1 to em1 when upgrading from biosdevname 0.4.1-3? Darn! I thought biosdevname was to keep the names the same!! -- Stephen Clark *NetWolves Managed Services, LLC.* Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark at netwolves.com http://www.netwolves.com

Hi all, I moved from 8.0-RELEASE to last week's -STABLE: $ uname -v FreeBSD 8.1-STABLE #0: Thu Sep 2 16:38:02 SAST 2010 root@XXXXX:/usr/obj/usr/src/sys/GENERIC and all seems well except my network card is unusable. On boot up: em0: <Intel(R) PRO/1000 Network Connection 7.0.5> port 0x3040-0x305f mem 0xe3200000-0xe321ffff,0xe3220000-0xe3220fff irq 10 at device 25.0 on pci0 em0: Setup

Hi there. I have configured kvm domain (rhel6.4) with ethernet bridged over macvtap, and found no filtration applied except mac. 'virsh' just silently ignoring attributes 'filterref' and 'ip address' in different formats. No error on validate stage. Config examples: ... <interface type='direct'> <mac address='52:54:00:31:ae:1a'/>

What is the best way to stop CentOS 6 from renaming the eth0 interface to em1? I've googled a bit and found many relevant posts, but have still not come up with an elegant solution. One of the resources I found was http://www.arachnoid.com/linux/network_names/index.html, and while the Python script contained therein does create a new udev rule that renames em1 back to eth0 it feels kludgy

On 5/19/2015 10:54 AM, m.roth at 5-cent.us wrote: > And that one drives me nuts. It breaks PXE boot kickstart builds. Maybe > *you* have all same model systems from the same manufacturer; we've got > boxen from...<thinking> at least five or six manufacturers, of varying > ages, from the 10+ yr old Altix 3000 from SGI, to the current one from > SGI, to my 5 yr old Dell