Discuss June 2013

discuss@lists.centos.org

152 participants
129 discussions

CentOS-announce Digest, Vol 100, Issue 3
by centos-announce-request＠centos.org 06 Jun '13

06 Jun '13

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CEBA-2013:0901 CentOS 6 iputils Update (Johnny Hughes) 2. CEBA-2013:0900 CentOS 6 kexec-tools Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 6 Jun 2013 02:12:42 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2013:0901 CentOS 6 iputils Update To: centos-announce(a)centos.org Message-ID: <20130606021242.GA50473(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2013:0901 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0901.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ea9ed964e8d0f1dcd7725235b5e3c55e4c4905a02cc8003ec5b111867734773f iputils-20071127-17.el6_4.i686.rpm x86_64: 81415f9071b059acbf250321e61c40e37940ada02a0ac1333cf6495850f79e7a iputils-20071127-17.el6_4.x86_64.rpm Source: 257edc25c2f27bde625259c9924e3ec2111791349c4959f5a0d731386473de30 iputils-20071127-17.el6_4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Thu, 6 Jun 2013 02:13:03 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2013:0900 CentOS 6 kexec-tools Update To: centos-announce(a)centos.org Message-ID: <20130606021303.GA50567(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2013:0900 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0900.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7cbe680d3847a124a70ce2c9a459ccde40c8186d1824830d5b361697b8672871 kexec-tools-2.0.0-258.el6_4.2.i686.rpm x86_64: cfed8bec988366325c805ec48cd5988383e9f63e52af48e896e23a643530db81 kexec-tools-2.0.0-258.el6_4.2.x86_64.rpm Source: 48873a743152c86955e4d1a35e310d3a8382f7a55fcb889d73f0c7c51e3ee74d kexec-tools-2.0.0-258.el6_4.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 100, Issue 3 ***********************************************

1 0

CentOS in OpenNebulaConf2013. Deadline for talk proposals
by Jaime Melis 06 Jun '13

06 Jun '13

Hello everyone, We have just published an extended keynote line-up for the OpenNebula Conference 2013 (http://blog.opennebula.org/?p=4707) that includes experts from leading institutions using OpenNebula. The first ever OpenNebula Conference will be held on Sept. 24-26 in Berlin and is intended to serve as a meeting point for OpenNebula cloud users, developers, administrators, builders, integrators and researchers. Everyone of you that has used OpenNebula with CentOS already knows why the combination of the two makes a lot of sense: it's stable, robust, works out of the box, there's upstream support and more importantly of all, a very big part of the OpenNebula user base is using CentOS. We would love to have people from the CentOS user base to speak at the OpenNebulaConf. There is only 10 days left to submit talk proposals (the deadline is June 15th). http://opennebulaconf.com/proposals/ Looking forward to welcoming you personally in Berlin! Cheers, Jaime -- Join us at OpenNebulaConf2013 <http://opennebulaconf.com/> in Berlin, 24-26 September, 2013 -- Jaime Melis Project Engineer OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org | jmelis(a)opennebula.org

1 0

cross link connection fall down
by Leon Fauster 06 Jun '13

06 Jun '13

Hey all, i am fighting with a strange behavior here - i have two systems connected via a direct crosslink wire. After booting, the connection is up and both systems can reach the other one. After a small time window the interface is down. $ dmesg |grep eth4 igb 0000:41:00.2: added PHC on eth4 igb 0000:41:00.2: eth4: (PCIe:5.0Gb/s:Width x4) igb 0000:41:00.2: eth4: PBA No: G13158-000 8021q: adding VLAN 0 to HW filter on device eth4 igb: eth4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX igb: eth4 NIC Link is Down igb: eth4 NIC Link is Up 10 Mbps Full Duplex, Flow Control: RX/TX igb: eth4 NIC Link is Down igb: eth4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX igb: eth4 NIC Link is Down igb: eth4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX igb: eth4 NIC Link is Down igb: eth4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX igb: eth4 NIC Link is Down igb: eth4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX igb: eth4 NIC Link is Down if i bring the connection manually up (ethtool -r eth4), i just have to wait and the status shows "down" again. $ grep eth4 /var/log/messages Jun 5 18:35:17 node2 kernel: igb 0000:41:00.2: added PHC on eth4 Jun 5 18:35:17 node2 kernel: igb 0000:41:00.2: eth4: (PCIe:5.0Gb/s:Width x4) Jun 5 18:35:17 node2 kernel: igb 0000:41:00.2: eth4: PBA No: G13158-000 Jun 5 18:35:17 node2 kernel: 8021q: adding VLAN 0 to HW filter on device eth4 Jun 5 18:35:17 node2 kernel: igb: eth4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Jun 5 18:38:10 node2 kernel: igb: eth4 NIC Link is Down Jun 5 19:23:21 node2 kernel: igb: eth4 NIC Link is Up 10 Mbps Full Duplex, Flow Control: RX/TX Jun 5 19:23:47 node2 kernel: igb: eth4 NIC Link is Down Jun 5 19:23:50 node2 kernel: igb: eth4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Jun 5 19:24:57 node2 kernel: igb: eth4 NIC Link is Down Jun 5 19:24:60 node2 kernel: igb: eth4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Jun 5 19:25:45 node2 kernel: igb: eth4 NIC Link is Down Jun 5 19:25:60 node2 kernel: igb: eth4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Jun 5 19:48:57 node2 kernel: igb: eth4 NIC Link is Down its a quad nic $ cat /etc/udev/rules.d/70-persistent-net.rules ... # PCI device 0x8086:0x1521 (igb) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="...", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4" the eth4 link is not in use right now. the other ports on the nic are currently in use (bonded). Had anyone ever seen such a behavior (on el6)? -- Thanks LF PS: cable already substituted / el6 system is up to date

1 0

Samba4 and NVSv4
by Steve Thompson 05 Jun '13

05 Jun '13

Short story: cannot get Kerberized NFSv4 to work. I've googled a great deal and cannot find where I have goofed (and there sure is a lot of misleading and just plain incorrect information out there), so would appreciate another pair of eyes. NFSv4 without Kerberos does work fine, as does ID mapping. We're using NFSv4 in production with sec=sys, but I'm not happy with that. My kerberized NFSv4 attempts are on a separate test cluster. Longer story (sorry for the length): All servers and clients are CentOS 6.4 with kernel 2.6.32-358.6.2.el6 and nfs-utils 1.2.3-36.el6; patches are up to date. NFSv4 servers are x86_64, clients are both x86_64 and i686. Two DC's are both i686, running Samba 4.0.5 with bind 9.91 + bind_dlz. Replication is good. All CentOS systems use sssd only and no winbind; this is also working (kinit, sudo, ssh, etc all good). Samba is at 3.6.9 on all systems except for the DC's. Samba4 works; DNS works; Kerberos works; NFSv4 works with sec=sys. I joined the clients to the domain ("TITAN.TEST.CORNELL.EDU") with: # net ads join -U Administrator ... # net ads testjoin and created the nfs service principals (on the client and NFSv4 server) with: # net ads keytab add nfs -U Administrator This all works. I can see that the nfs service principals have been added; on the client abbott.test.cornell.edu, for example: # net ads keytab list | grep -i nfs 2 DES cbc mode with CRC-32 nfs/abbott.test.cornell.edu(a)TITAN.TEST.CORNELL.EDU 2 DES cbc mode with RSA-MD5 nfs/abbott.test.cornell.edu(a)TITAN.TEST.CORNELL.EDU 2 ArcFour with HMAC/md5 nfs/abbott.test.cornell.edu(a)TITAN.TEST.CORNELL.EDU 2 AES-128 CTS mode with 96-bit SHA-1 HMAC nfs/abbott.test.cornell.edu(a)TITAN.TEST.CORNELL.EDU 2 AES-256 CTS mode with 96-bit SHA-1 HMAC nfs/abbott.test.cornell.edu(a)TITAN.TEST.CORNELL.EDU 2 DES cbc mode with CRC-32 nfs/abbott(a)TITAN.TEST.CORNELL.EDU 2 DES cbc mode with RSA-MD5 nfs/abbott(a)TITAN.TEST.CORNELL.EDU 2 ArcFour with HMAC/md5 nfs/abbott(a)TITAN.TEST.CORNELL.EDU 2 AES-128 CTS mode with 96-bit SHA-1 HMAC nfs/abbott(a)TITAN.TEST.CORNELL.EDU 2 AES-256 CTS mode with 96-bit SHA-1 HMAC nfs/abbott(a)TITAN.TEST.CORNELL.EDU and on one of the DC's: # ldbsearch cn=abbott | grep -i nfs servicePrincipalName: NFS/abbott servicePrincipalName: NFS/abbott.test.cornell.edu and on the client "net ads search '(sAMAccountName=abbott$)'" also works, as does klist: # klist -ke | grep -i nfs 2 nfs/abbott.test.cornell.edu(a)TITAN.TEST.CORNELL.EDU (des-cbc-crc) 2 nfs/abbott.test.cornell.edu(a)TITAN.TEST.CORNELL.EDU (des-cbc-md5) 2 nfs/abbott.test.cornell.edu(a)TITAN.TEST.CORNELL.EDU (arcfour-hmac) 2 nfs/abbott.test.cornell.edu(a)TITAN.TEST.CORNELL.EDU (aes128-cts-hmac-sha1-96) 2 nfs/abbott.test.cornell.edu(a)TITAN.TEST.CORNELL.EDU (aes256-cts-hmac-sha1-96) 2 nfs/abbott(a)TITAN.TEST.CORNELL.EDU (des-cbc-crc) 2 nfs/abbott(a)TITAN.TEST.CORNELL.EDU (des-cbc-md5) 2 nfs/abbott(a)TITAN.TEST.CORNELL.EDU (arcfour-hmac) 2 nfs/abbott(a)TITAN.TEST.CORNELL.EDU (aes128-cts-hmac-sha1-96) 2 nfs/abbott(a)TITAN.TEST.CORNELL.EDU (aes256-cts-hmac-sha1-96) In /etc/sysconfig/nfs, SECURE_NFS=yes on all clients and servers, and rpc.gssd and rpc.svcgssd are running (although no need for the latter on the clients). The NFSv4 server exports with sec=sys:krb5 (and as I said, NFSv4 works fine without krb5, so I believe the exports file to be correct). But when I try to mount, I get the catch-all error: # mount -t nfs4 -o sec=krb5 costello.test.cornell.edu:/data /mnt/tmp mount.nfs4: access denied by server while mounting costello.test.cornell.edu:/data and in /var/log/messages on the same client: Jun 5 17:11:13 abbott rpc.gssd[1439]: Success getting keytab entry for 'nfs/abbott.test.cornell.edu(a)TITAN.TEST.CORNELL.EDU' Jun 5 17:11:13 abbott rpc.gssd[1439]: WARNING: Client 'nfs/abbott.test.cornell.edu(a)TITAN.TEST.CORNELL.EDU' not found in Kerberos database while getting initial ticket for principal 'nfs/abbott.test.cornell.edu(a)TITAN.TEST.CORNELL.EDU' using keytab 'FILE:/etc/krb5.keytab' Jun 5 17:11:13 abbott rpc.gssd[1439]: ERROR: No credentials found for connection to server costello.test.cornell.edu With tcpdump I can see that the DC is contacted during the mount, but the NFSv4 server is not. The log files on the NFSv4 server are silent. I have tried (everything was restarted between tests); "no change" means that it still does not work and gives the same exact errors: - verified that /etc/idmapd.conf on all systems has the same domains and realms. This works anyway with sec=sys. - reduced the keytab to the DES enctypes for nfs/... on all systems; no change. - used "allow_weak_crypto=true" in /etc/krb5.conf; no change. - set default_tgs_enctypes and default_tkt_enctypes to "des-cbc-md5 des-cbc-md4 des-cbc-crc" in /etc/krb5.conf; no change. - tried adding the service principals on the DC with "samba-tool spn add" instead of "net ads keytab add" on the client, and then exporting the keytab to the client; no change. - add the SPN "nfs/abbott.test.cornell.edu(a)TITAN.TEST.CORNELL.EDU" and "nfs/abbott(a)TITAN.TEST.CORNELL.EDU" in case the missing realm was a factor; no change. - started rpc.gssd on the clients with the -l switch; no change. - started rpc.svcgssd with the -n switch so that nfs/ service principals are in theory not required; no change. I do not understand why rpc.gssd canot find the service principal, when it does exist in the database. I've probably missed out some other things that I have tried to no effect. Help! Steve -- ---------------------------------------------------------------------------- Steve Thompson E-mail: smt AT vgersoft DOT com Voyager Software LLC Web: http://www DOT vgersoft DOT com 39 Smugglers Path VSW Support: support AT vgersoft DOT com Ithaca, NY 14850 "186,282 miles per second: it's not just a good idea, it's the law" ----------------------------------------------------------------------------

2 4

xhost + via Desktop centos 6.3 not working
by Edsall, William (WJ) 05 Jun '13

05 Jun '13

Hello list, In the past we have instructed users to perform 'xhost +' from their centos desktop, then set the DISPLAY variable on a remote computer to forward their display back to the desktop. This does not seem to work on centos 6 - but it did work in centos 5. It works from a vnc session on the desktop machine, but does not work from the local desktop. We would typically use a display variable like this: export DISPLAY=163.198.177.218:0.0 - The target system acts like the request is being refused: Error: Can't open display: 163.198.177.218:0.0 Have there been any changes in centos 6 which make xhost + behave differently for the desktop session? We've been struggling with this issue now for some time - can't find the right solution. Any help would be appreciated! Thanks in advance, William

5 4

ssh -Y X-forwarding?
by Les Mikesell 05 Jun '13

05 Jun '13

On rare occasions I want to run a remote X command (like 'meld' to interactively merge changes in files) and normally 'ssh -Y remote_host' from a terminal in an NX/freenx window that is acting as my desktop to start and any X program subsequently started would open in a new window via X-forwarding - at least when the target is a 5.x host. I don't do it often enough to remember if it ever worked when the remote side is 6.x, but today it is not setting the $DISPLAY variable, so I get: Error: Can't open display: Using -vv shows it at least trying to go through the motions: debug2: x11_get_proto: /usr/bin/xauth list :1420.0 2>/dev/null debug1: Requesting X11 forwarding with authentication spoofing. debug2: channel 0: request x11-req confirm 0 debug2: client_session2_setup: id 0 debug2: channel 0: request pty-req confirm 1 debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug2: channel 0: request env confirm 0 debug2: channel 0: request shell confirm 1 debug2: fd 3 setting TCP_NODELAY But, $DISPLAY is not set to anything. What am I missing? -- Les Mikesell lesmikesell(a)gmail.com

7 10

centos 6' repositories against redhat 6 upstream
by Gelen James 05 Jun '13

05 Jun '13

Hi Wonder how's the relationship between the centos 6's main OS/ repository and redhat 6's repositories. Let's say, Redhat 6 seperate RPMs into a series of repos like: redhat-6-server ##(base redhat 6 OS/) redhat-6-server-optional redhat-6-server-supplementary redhat-6-server-rhev-agent rhel-6-server-cf-tools ... Does centos 6 merge all the redhat 6 repos into one big repository? or still leave out some minor/functional ones? If the second is true, then it will be great if we can find the repo mapping link between Redhat 6 and centos 6. Thanks a lot. --Rob

2 1

CentOS-announce Digest, Vol 100, Issue 2
by centos-announce-request＠centos.org 05 Jun '13

05 Jun '13

1 0

Centos6.4 routing problem
by Johan Vermeulen 05 Jun '13

05 Jun '13

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 UUID="cdfe1d58-c56c-47fc-8a93-5df2e168d176" IPV6INIT=no USERCTL=no DNS2=195.238.2.22 DNS1=192.168.66.1 IPADDR=192.168.66.5 NETMASK=255.255.255.128 GATEWAY=192.168.66.1 and one nic serving the lan and dhpcd. vi /etc/sysconfig/network-scripts/ifcfg-em2 DEVICE=em2 BOOTPROTO=none HWADDR=d4:ae:52:c1:28:2c NM_CONTROLLED=no ONBOOT=yes TYPE=Ethernet UUID="e72a17b6-fb5f-43f0-9136-fa4d92b542ae" IPADDR=192.168.70.129 NETMASK=255.255.255.128 IPV6INIT=no USERCTL=no in iptables, prerouting and masquerading are configured : # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *nat :PREROUTING ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :POSTROUTING ACCEPT [0:0] -A POSTROUTING -o eth+ -j MASQUERADE -A POSTROUTING -o em2 -j MASQUERADE COMMIT *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -i eth+ -j ACCEPT -A INPUT -i em2 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT -A FORWARD -p icmp -j ACCEPT -A FORWARD -i lo -j ACCEPT -A FORWARD -i eth+ -j ACCEPT -A FORWARD -i em2 -j ACCEPT -A FORWARD -o eth+ -j ACCEPT -A FORWARD -o em2 -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT and in /etc/sysctl.conf ipforwarding is set to 1 # Kernel sysctl configuration file for Red Hat Linux # # For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and # sysctl.conf(5) for more details. # Controls IP packet forwarding net.ipv4.ip_forward = 1 clients get ip adresses from dhcp server, and there's no other dhcp server on the lan. But clients cannot ping the public internet, e.g. 8.8.8.8 the only EM I'm seeing is when executing command : [root@centoshofkwartier ~]# sysctl -p /etc/sysctl.conf net.ipv4.ip_forward = 1 net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.default.accept_source_route = 0 kernel.sysrq = 0 kernel.core_uses_pid = 1 net.ipv4.tcp_syncookies = 1 error: "net.bridge.bridge-nf-call-ip6tables" is an unknown key error: "net.bridge.bridge-nf-call-iptables" is an unknown key error: "net.bridge.bridge-nf-call-arptables" is an unknown key kernel.msgmnb = 65536 kernel.msgmax = 65536 kernel.shmmax = 68719476736 kernel.shmall = 4294967296 I switched the cables and switches, and changed the connection with the public internet. Can anybody offer some advise on this? Greetings, J. -- Johan Vermeulen IT-medewerker Caw De Kempen Opensource Software is the future.

5 7

Re: [CentOS] Centos6.4 routing problem
by Bonnie Mtengwa 05 Jun '13

05 Jun '13

Sent from my HTC ----- Reply message ----- From: "Johan Vermeulen" <jvermeulen(a)cawdekempen.be> To: "CentOS mailing list" <centos(a)centos.org> Subject: [CentOS] Centos6.4 routing problem Date: Tue, Jun 4, 2013 16:13 hello Mark, thanks for the help. Op 04-06-13 15:56, m.roth(a)5-cent.us schreef: > Johan Vermeulen wrote: >> 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: >> > First, we always have BOOTPROTO set - in your case, assuming you're > getting em1's IP from DHCP, you should have that; in the case of em2, it's > BOOTPROTO=static. As it is, I'd think (without testing) that em1 is trying > to present a reserved IP to the 'Net, which is a no-no. both ifcfg's now have BOOTPROTO=static and I restarted network and dhcpd. > >> 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 >> UUID="cdfe1d58-c56c-47fc-8a93-5df2e168d176" >> IPV6INIT=no >> USERCTL=no >> DNS2=195.238.2.22 >> DNS1=192.168.66.1 >> IPADDR=192.168.66.5 >> NETMASK=255.255.255.128 >> GATEWAY=192.168.66.1 >> >> and one nic serving the lan and dhpcd. >> >> vi /etc/sysconfig/network-scripts/ifcfg-em2 >> >> DEVICE=em2 >> BOOTPROTO=none >> HWADDR=d4:ae:52:c1:28:2c >> NM_CONTROLLED=no >> ONBOOT=yes >> TYPE=Ethernet >> UUID="e72a17b6-fb5f-43f0-9136-fa4d92b542ae" >> IPADDR=192.168.70.129 >> NETMASK=255.255.255.128 >> IPV6INIT=no >> USERCTL=no > <snip> > Secondly, what does route show? > > mark > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos [root@centoshofkwartier ~]# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.70.128 * 255.255.255.128 U 0 0 0 em2 192.168.66.0 * 255.255.255.128 U 0 0 0 em1 link-local * 255.255.0.0 U 1002 0 0 em1 link-local * 255.255.0.0 U 1003 0 0 em2 default 192.168.66.1 0.0.0.0 UG 0 0 0 em1 greetings, J. _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss June 2013