[CentOS] network not accessible through bridged interface but traffic visible
I had a major HD failure and need to rebuild my host server and the virtual servers that resided on it. I am moving from CentOS 5.6 to CentOS 6.3. I am using the same configuration, as best as I can tell, that was working only hours ago on 5.6 but does not work on 6.3. My guest server can see network traffic on the bridged network device but I cannot seem to interact with it. Iptables turned off on both the host and guest makes no difference. *Host server settings that apply:* NetworkManager is off Network is on /etc/sysconfig/network NETWORKING=yes NETWORKING_IPV6=no HOSTNAME=host GATEWAY=192.168.4.1 /etc/resolv.conf search domain.com nameserver 68.87.xx.xx nameserver 68.87.xx.xx /etc/sysctl.conf net.ipv4.ip_forward = 1 net.bridge.bridge-nf-call-ip6tables = 0 net.bridge.bridge-nf-call-iptables = 0 net.bridge.bridge-nf-call-arptables = 0 /etc/sysconfig/network-scripts/ifcfg-em2 DEVICE=em2 NM_CONTROLLED=no BOOTPROTO=none HWADDR=... ONBOOT=yes HOTPLUG=no BRIDGE=br2 /etc/sysconfig/network-scripts/ifcfg-br2 DEVICE=br2 TYPE=Bridge BOOTPROTO=none ONBOOT=yes DELAY=0 /etc/sysconfig/network-scripts/ifcfg-em3 DEVICE=em3 NM_CONTROLLED=no BOOTPROTO=none HWADDR=... ONBOOT=yes HOTPLUG=no BRIDGE=br3 /etc/sysconfig/network-scripts/ifcfg-br3 DEVICE=br3 TYPE=Bridge BOOTPROTO=none ONBOOT=yes DELAY=0 On the host I connect to the network using a different nic ifcfg-em5. Which connects to the gateway server and the internet just fine. *The guest settings:* Virtual Network Interface Source Device: Host device vnet0 (Bridge 'br2') Device Model: virtio MAC Address: ... Virtual Network Interface Source Device: Host device vnet1 (Bridge 'br3') Device Model: virtio MAC Address: ... NetworkManager is off Network is on /etc/sysconfig/network NETWORKING=yes NETWORKING_IPV6=no HOSTNAME=host GATEWAY=192.168.4.1 /etc/resolv.conf search domain.com nameserver 68.87.xx.xx nameserver 68.87.xx.xx /etc/sysctl.conf net.ipv4.ip_forward = 1 net.bridge.bridge-nf-call-ip6tables = 0 net.bridge.bridge-nf-call-iptables = 0 net.bridge.bridge-nf-call-arptables = 0 /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=static HWADDR=... NM_CONTROLLED=no ONBOOT=yes IPADDR=192.168.4.3 NETMASK=255.255.255.0 NETWORK=192.168.4.0 DNS1=68.87.XX.XX DNS2=68.87.XX.XX /etc/sysconfig/network-scripts/ifcfg-eth1 DEVICE=eth1 BOOTPROTO=static HWADDR=... NM_CONTROLLED=no ONBOOT=yes IPADDR=192.168.6.1 NETMASK=255.255.255.0 NETWORK=192.168.6.0 #route Kernel IP routing table DestinationGateway Genmask Flags Metric Ref Use Iface 192.168.6.0* 255.255.255.0 U0 0 0 eth1 192.168.5.0 otherserver255.255.255.0 UG 0 0 0 eth0 192.168.4.0 * 255.255.255.0 U0 0 0 eth0 192.168.1.0 anotherserver 255.255.255.0 UG 0 0 0 eth0 link-local * 255.255.0.0 U1002 00 eth0 link-local * 255.255.0.0 U1003 00 eth1 default gatewayserver 0.0.0.0UG 0 00 eth0 This is the most bizarre thing. I can see the nic traffic on the guest with a tcpdump but I cannot interact with the traffic. # traceroute 192.168.4.1 traceroute to 192.168.4.1 (192.168.4.1), 30 hops max, 60 byte packets 1guestserver (192.168.4.3)3000.636ms !H 3000.633ms !H 3000.628 ms !H Any fresh ideas and insights are greatly appreciated! Thanks! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] School cloud solution
I did look at alfresco but, like moodle, it has way more going on then I need. Sent from my ASUS Eee Pad Rajagopal Swaminathan raju.rajs...@gmail.com wrote: Greetings, On Sun, Nov 6, 2011 at 8:13 AM, Doug Coats dcoats...@gmail.com wrote: Your own instance of liferay/alfresco community edition exposed to internet with the usual safegaurds perhaps... BTW, taking this example, what exactly are the usual safeguards apart from enabling selinux in permissive mode and enabling firewall with only http and ssh ports open? Some apps behave ugly in selinux enforcing mode. Any pointers? TIA -- Regards, Rajagopal ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] School cloud solution
That is exactly the search criteria i needed! I had never seen the term before or at least didnt remember it. Thanks! Sent from my ASUS Eee Pad Toby Bluhm toby.bl...@alltechmedusa.com wrote: On 11/5/2011 10:43 PM, Doug Coats wrote: I understand what google docs offers but it comes with the need for an email address that i can not make students have, the inability for me to control who has access to which files, and no way to get teachers access without each student configuring that on their own. My teachers have enough to worry about. They will not use a solution that is more difficult then what we already use. Any solution has to be a clear upgrade with advantages for it to be adopted. Sent from my ASUS Eee Pad Try a search for document management system open source. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] School cloud solution
This really isn't a CentOS specific queation but that is our server OS of choice. I manage a student file server and i would like to add cloud access to it. Basically i would like our students to have access to the same files at home that they have at school. This would allow them to start an asignment at home, finish it at school, and print it off without having to worry about losing their usb drive. I want it housed on our servers for backups and ease of access for our teachers when necessary. I have looked at Moodle but it has way to many layers that we are not interested in. I would like something like squirrel mail. A simple web login that then gives you access to your samba managed files. I have repeatedly searched for such capabilities but i have not found any that fit what i outlined above. Is there such a program out there? Thanks for your thoughts! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] School cloud solution
Thanks for all of your thoughts. I will look into gollem. The clients at school are windows 7. At home the clients might be any number of OS's. Eventually we might be using some sort of tablet devise probably Android based. Have any of you used Gollem? On Nov 5, 2011 8:16 PM, Barry Brimer li...@brimer.org wrote: ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] School cloud solution
I understand what google docs offers but it comes with the need for an email address that i can not make students have, the inability for me to control who has access to which files, and no way to get teachers access without each student configuring that on their own. My teachers have enough to worry about. They will not use a solution that is more difficult then what we already use. Any solution has to be a clear upgrade with advantages for it to be adopted. Sent from my ASUS Eee Pad John R Pierce pie...@hogranch.com wrote: On 11/05/11 6:29 PM, Doug Coats wrote: Thanks for all of your thoughts. I will look into gollem. The clients at school are windows 7. At home the clients might be any number of OS's. Eventually we might be using some sort of tablet devise probably Android based. see, another problem with a 'file' based solution is editing software... ok, you have windows7 at school... what format are the documents in, MS Office 2010 ? Users at home are going to have a motley mix of older versions and other platforms, possibly not have the same font sets, etc etc. The Google App approach bypasses this entirely, the client editing software is the browser and the google app Ajax stuff. The documents are the same regardless of what platform the user is on. -- john r pierceN 37, W 122 santa cruz ca mid-left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS problem while trying to join windows 7 to samba3x pdc
I am not using Samba 3.x. I am using Samba3x-3.3.8. As I understand it, RHEL provided this branch so that Windows 7 could join a Samba domain. That aside, It does not seems to me that the error message indicates that it cannot resolve where the PDC is. What method is Windows 7 trying to use that is differnent for Windows XP to find the PDC? Samba 3.x cannot provide AD and thus the error about AD DNS name does not exist is not meaningful You probably want to use Sernet Samba packages at this point if you want to use Windows 7 clients but see this page... http://wiki.samba.org/index.php/Windows7 Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS problem while trying to join windows 7 to samba3x pdc
I think as long as persist in chasing pointless ends, you will continue to fail. DNS AD are not at issue here. Samba 3 cannot provide AD services. If resolution is a problem, it may be that you don't have nmb running on your Samba server and you probably want it to be a wins server if it is a Domain Controller. Craig Craig, Thanks for you interest in my problem. I don't think I am trying to get Samba to do something that it was not intended to do. All I am saying is that using the same config on Samba 3.0 as a PDC with windows XP machines behaves different than Samba3x with Windows 7 and windows XP machines. I just now tried to join an XP machine to the network and got a similar error. Maybe this is a Samba3x.3.3.8 issue? I don't expect Samba to provide AD services. I simply want single sign-on on my network. Has anyone been able to get Samba3x.3.3.8 to work as a PDC? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS problem while trying to join windows 7 to samba3x pdc
I think you are being vague (similar error). What is the exact error? What is the output of 'testparm -sv' ? Craig Sorry for being to vague. Here is the XP Pro error I get when I try to join the domain. A domian controller for the domain admin could not be contacted. Esure that the domain name is typed correctly. If the name is correct, click on the Details for troubleshooting information. Details: Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt. The domain name admin might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS. If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration. An error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain admin. The error was: No records found for given DNS query. (error code 0x251D DNS_INFO_NO_RECORDS) The query was for the SRV record for _ldap._tcp.dc._msdcs.admin For more information, click Help. Here is the testparm -sv you requested. For a short explaination of the IP's listed. We have two domains. One served by 192.168.6.1 and one by 192.168.5.1. I am currantly upgrading the 192.168.6. network to Windows 7. Or atleast trying. 192.168.4.1 is our gatway and the two servers listed above act as file servers and routers for their domains. I hope that makes sence. Load smb config files from /etc/samba/smb.conf Processing section [homes] Processing section [netlogon] WARNING: The share modes option is deprecated Processing section [admin] Processing section [staff] Processing section [ElemTeachers] Processing section [SecTeachers] Processing section [it] Processing section [office] Processing section [finance] Processing section [backup] Processing section [www] Processing section [scribeshare] Processing section [sosub] Loaded services file OK. Server role: ROLE_DOMAIN_PDC [global] dos charset = CP850 unix charset = UTF-8 display charset = LOCALE workgroup = ADMIN realm = netbios name = HERITAGE3 netbios aliases = netbios scope = server string = Administration Samba Server interfaces = 192.168.4.3, 192.168.6.1, 127.0.0.1 bind interfaces only = No config backend = file security = USER auth methods = encrypt passwords = Yes update encrypted = No client schannel = Auto server schannel = Auto allow trusted domains = Yes map to guest = Never null passwords = No obey pam restrictions = No password server = * smb passwd file = /etc/samba/smbpasswd private dir = /var/lib/samba/private passdb backend = smbpasswd algorithmic rid base = 1000 root directory = guest account = nobody enable privileges = Yes pam password change = No passwd program = passwd chat = *new*password* %n\n *new*password* %n\n *changed* passwd chat debug = No passwd chat timeout = 2 check password script = username map = password level = 0 username level = 0 unix password sync = No restrict anonymous = 0 lanman auth = No ntlm auth = Yes client NTLMv2 auth = No client lanman auth = No client plaintext auth = No preload modules = use kerberos keytab = No log level = 1 syslog = 1 syslog only = No log file = /var/log/samba/%m.log max log size = 50 debug timestamp = Yes debug prefix timestamp = No debug hires timestamp = No debug pid = No debug uid = No debug class = No enable core files = Yes smb ports = 445 139 large readwrite = Yes max protocol = NT1 min protocol = CORE min receivefile size = 0 read raw = Yes write raw = Yes disable netbios = No reset on zero vc = No acl compatibility = auto defer sharing violations = Yes nt pipe support = Yes nt status support = Yes announce version = 4.9 announce as = NT max mux = 50 max xmit = 16644 name resolve order = hosts wins lmhosts bcast max ttl = 259200 max wins ttl = 518400 min wins ttl = 21600 time server = Yes unix extensions = Yes use spnego = Yes client signing = auto server signing = No client use spnego = Yes client ldap sasl wrapping = plain enable asu support = No svcctl list = deadtime = 0 getwd cache = Yes
Re: [CentOS] DNS problem while trying to join windows 7 to samba3x pdc
His problem is WINS resolution doesn't tell the workstations which computer is the domain controller and that is what he needs to fix (first by designating a domain controller and then by making sure that WINS is functioning well). Craig Thanks for all the help. I agree that WINS seems to be the issue, or atleast it is a place that we can start with to help track down the issue. Currently 192.168.4.1 is the WINS server. This is necessary because I need cross subnet brownsing between 192.168.6. and 192.168.5. According to the man page for smb.conf only one computer on your network can be a WINS server and this is the computer that all other computers have access to. That being said 192.168.6. and 192.168.5. are both PDC's for their subnet. All I have done is moved the 192.168.6.1 configuration to a new machine. Replaced that machine. Removed Samba 3.0 and Installed Samba3x. How do I make sure that 192.168.4.1 recognizes 192.168.6.1 as the ADMIN PDC so that WINS traffic is directed correctly? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS problem while trying to join windows 7 to samba3x pdc
a 'network' is 192.168.x assuming that you are using class C subnet masks (255.255.255.0) and so you should have a WINS server on EACH network (192.168.4, 192.168.5, 192.168.6, etc.) Cross network browsing is somewhat of a hit or miss and not reliable... for a number of reasons such as the default firewall settings for Windows systems will only allow network traffic to the immediate network that it is on (i.e. 192.168.6) The important thing is to get the WINS working on EACH network. It's also easiest to have your PDC be the WINS server - period. Also, a PDC must necessarily have... domain master = yes preferred master = yes domain logins = yes security = user Craig I agree that preferred master should have been set to yes. I made that change with but still no joy. I don't mean to be contrary but our cross subnet browsing has been working since 2003 when we set up this network. It has been very reliable and I depend on it to work. And I believe it is because of have our WINS servers the way that they are. I do think that I have hit upon an issue. The WINS data for samba is kept in /var/cache/samba.dat but it is updated dynamically with nmdb. It has dated data. When I moved the server I changed the server name slightly and so the WINS data points to the old name at the current IP. In fact with this network rebuild I changed most of my computer names and they are all incorrect. I think I need to shut down all three instances of samba clear the wins data and then start them all again so that they populate from scratch. Doug ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS problem while trying to join windows 7 to samba3x pdc
I do think that I have hit upon an issue. The WINS data for samba is kept in /var/cache/samba.dat but it is updated dynamically with nmdb. It has dated data. When I moved the server I changed the server name slightly and so the WINS data points to the old name at the current IP. In fact with this network rebuild I changed most of my computer names and they are all incorrect. I think I need to shut down all three instances of samba clear the wins data and then start them all again so that they populate from scratch. Correction to that. Only the WINS server has data in this location. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS problem while trying to join windows 7 to samba3x pdc
With the WINS data cleared. for the past 20 min. (I did it before I wrote about it) Neither PDC has reported to WINS. So no wonder my PC's can't find their domain. So how do I make sure that 192.168.6.1 is added to wins.dat. I could do it manually but I would rather it communicate the way that it was intended to just so I know that the network is configured and working correctly. Doug ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS problem while trying to join windows 7 to samba3x pdc
Um, does a timing issue come into play here? If the local clock is not within a few seconds, we can't connect to AD (we are going through kerborous). Is there time data in the cache? mark Both the XP box and the Windows 7 use the PDC server as their time server so they are set to the same time. Doug ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS problem while trying to join windows 7 to samba3x pdc
--- Ok since you say the interdomain networking is functioning (triangle routing) have a read at this: http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/domain-member.html#id2573732 John all else that fails put that machine on another known working Subnet and have a go at that. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos As I said in another post I changed the machine name to an entirely different format and I didn't copy any domain information from the prior machine(meaning I didn't try to migrate the information placed in the smbpasswd). Since all the machines were being switched to Windows 7 I wanted a clean start. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS problem while trying to join windows 7 to samba3x pdc
I just did a checkconfig on the PDC in question 192.168.6.1. And I noticed something that might be nothing but it puzzles me. The nmb service is set to off at all run levels. If I check the nmb status it says that it is stopped. Doesn't Samba need that for net-bios support? I am probably showing my ignorace here but what is the connection between net-bios names and WINS? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS problem while trying to join windows 7 to samba3x pdc
How 'bout with the server that's supposed to be the master, above the two other PDCs? mark It is set up to NTP to the same external servers so they should all be in sync. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS problem while trying to join windows 7 to samba3x pdc
Netbios can use multiple network transports, some of which only have broadcasts to support name resolution. Each subnet will elect a master browser to collect the names and respond to queries. As an extension for the IP protocol which is routeable, the WINS service accepts the lists from multiple master browsers at a pre-configured IP address. For it to work, the master browser that happens to be elected on any subnet must be configured to use the same WINS address and must have IP protocol working - and the clients need the address to query as part of their configuration, either from DHCP or manually entered if they have a static IP. -- Les Mikesell lesmikes...@gmail.com Thank you Les for not killing me off like some of the other people who have been trying to help. As a response to others, YES, I should have read the man but I might have posed the question all the same. Sometimes my eyes glaze over after about he 3rd sentence when trying to make sense of them. I turned on nmb and that solved my problem. Sometimes my life serves as a warning to others and now all they have to do is read my posts and learn from my mistakes. Thanks for your patience ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS problem while trying to join windows 7 to samba3x pdc
After a little bit of research I feel a little vindicated. It seems that Samba3x seporated out nmb. On Samba 3.0 the nmb service does not show up in the chkconfig. It simply starts and stops with smb. On Samba3x it seporates out nmb and it does not start by itself. So based on my experience I never needed to start nmb seporately so just like all of you it didn't enter my mind as the culperate. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] KVM virtual guest can not use serial port
Thanks - Markus. I'll check it out. The following link describes how to configure libvirt for serial port pass through. http://empegbbs.com/ubbthreads.php?ubb=showflatNumber=314827 - -- Regards, Markus ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] KVM virtual guest can not use serial port
That was exactly what I needed...Thanks a ton! Doug ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] DNS problem while trying to join windows 7 to samba3x pdc
I am running centos 5.5 using samba3x as a pdc. I migrated to samba3x so that I could join Windows 7 machines to the domain. It is a new setup using a tried and true configuration from a different box. I have used this configuration in the past to joing Windows XP Pro machines. And I havn't found anyting helpful on the error with google. I can ping the server name and the server can ping the windows 7 box. I can access smaba shares on the server but I cannot join the domain. I have applied the reg settings to win7 and when I try to join I get this error. An Active Directory Domain Controller (AD DC) for domain admin could not be contacted. Ensure that the domain name is typed correctly. If the name is correct, click Details for troubleshooting information. The details read: Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt. The domain name admin might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS. If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration. The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain admin: The error was: DNS name does not exist. (error code 0x232B RCODE_NAME_ERROR) The query was for the SRV record for _ldap._tcp.dc._msdcs.admin Common causes of this error include the following: - The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses: 192.168.4.1 - One or more of the following zones do not include delegation to its child zone: admin . (the root zone) I seem to have a DNS problem but I don't even know what it should be doing so that I know where to start to troubleshoot. Thanks for any help! Doug ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] KVM virtual guest can not use serial port
I hope this is not to far off topic. I have a Windows 2003 guest on a CentOS 5.5 KVM host. I need to use the serial port on the win2003 guest for the application it is serving. I have no idea what needs to be done but it looks like the linux host is trying to use the serial port as the priamary console but I don't really understand what that is or where it is configured. What I need is for the host to ignore any traffice over the serial port and to pass it to the guest. On the host, ls -l /dev | grep ttyS, returns: crw-rw 1 root uucp 4,64 Jul 6 10:17 ttyS0 crw-rw 1 root uucp 4,65 Jul 6 10:17 ttyS1 crw-rw 1 root uucp 4,66 Jul 6 10:17 ttyS2 crw-rw 1 root uucp 4,67 Jul 6 10:17 ttyS3 It only has 1 serial port so I don't know why ttyS1-S3 are listed. On the guest it says that Com1 is configured and working properly. On the Virtual Machine Hardware tab of the guest it lists a Serial 0. Details: Serial Device (Priamary Console) Device Type: pty Target Port: 0 Source Path: /dev/pts/2 Any help would be greatly appreaciated. Thanks!!! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] KVM virtual guest can not use serial port
I would expect it to be guest os independent, that means it has to be configured in the host ? Regards, Markus So does anyone know how to configure a serial port properly in CentOS 5.5? Thanks again ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Routing issue - Revisited
A number of weeks ago I had huge help from many of you configuring routing on a server with multiple Internet facing nics. Thanks for all of your help I am still having a routing issue that I am hoping someone can help me tweek. This server, besides acting as our gateway to the internet, is also our web and email server. The server has 4 nics. Two are connected to the internet and the other two route traffic to internal subnets. Our network topography in question looks like this: Internet - Gateway Server - 192.168.4 subnet - Internal Server - 192.168.6 subnet - Clients The problem that I am experiencing is that part of our internal network, the 192.168.6 subnet cannot view our website that is hosted on our Gateway server. Our Internal Server can access the site but the Clients simply time out looking for it. If I point the Client to the internal address of the Gateway Server I can pull up the site but if I use the URL the browser times out. If I turn off my ip rules I can then view the URL on my Clients but of course external routing falls apart. /etc/sysconfig/network-scripts/rule-eth2 from 173.11.51.45 table Cable /etc/sysconfig/network-scripts/rule-eth3 from 67.152.166.2 table T1 /etc/sysconfig/network-scripts/route-eth0 GATEWAY1=192.168.4.3 NETMASK1=255.255.255.0 ADDRESS1=192.168.6.0 GATEWAY0=192.168.4.2 NETMASK0=255.255.255.0 ADDRESS0=192.168.5.0 /etc/sysconfig/network-scripts/route-eth1 GATEWAY0=192.168.4.1 NETMASK0=255.255.255.0 ADDRESS0=192.168.4.0 /etc/sysconfig/network-scripts/route-eth2 173.11.51.44/30 dev eth2 proto kernel scope link src 173.11.51.45 table Cable 173.11.51.44/30 dev eth2 src 173.11.51.45 default via 173.11.51.46 table Cable default via 173.11.51.46 192.168.4.0/24 dev eth0 proto kernel scope link src 192.168.4.1 table Cable /etc/sysconfig/network-scripts/route-eth3 67.152.166.0/27 dev eth3 proto kernel scope link src 67.152.166.2 table T1 67.152.166.0/27 dev eth3 src 67.152.166.2 default via 67.152.166.1 table T1 192.168.4.0/24 dev eth0 proto kernel scope link src 192.168.4.1 table T1 # ip rule list 0: from all lookup 255 32764: from 67.152.166.2 lookup T1 32765: from 173.11.51.45 lookup Cable 32766: from all lookup main 32767: from all lookup default # ip route show 173.11.51.44/30 dev eth2 scope link src 173.11.51.45 67.152.166.0/27 dev eth3 proto kernel scope link src 67.152.166.2 192.168.6.0/24 via 192.168.4.3 dev eth0 192.168.5.0/24 via 192.168.4.2 dev eth0 192.168.4.0/24 dev eth0 proto kernel scope link src 192.168.4.1 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.1 169.254.0.0/16 dev eth3 scope link default via 173.11.51.46 dev eth2 # ip route show table cable 173.11.51.44/30 dev eth2 proto kernel scope link src 173.11.51.45 192.168.4.0/24 dev eth0 proto kernel scope link src 192.168.4.1 default via 173.11.51.46 dev eth2 # ip route show tabel T1 67.152.166.0/27 dev eth3 proto kernel scope link src 67.152.166.2 192.168.4.0/24 dev eth0 proto kernel scope link src 192.168.4.1 default via 67.152.166.1 dev eth3 Any insight would be greatly appreciated! I have been pecking away at it and I just can't seem to get it right. Thanks - Doug ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Routing issue - Revisited
You were exactly correct. This resolved my issue. Thanks so much!!! As you can tell I am new to using iproute2. Thanks again!!! I believe what you need to fix this issue is: # ip route add 192.168.6.0/24 via 192.168.4.3 dev eth0 table Cable # ip route add 192.168.6.0/24 via 192.168.4.3 dev eth0 table T1 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Multiple Internet facing Nics - Gateway issue
Adding the routes and rules to the appropriate files in network-scripts did
not work. It gave me a number of errors and did not create the rules after
reboot or/and network restart.
On Fri, Jul 3, 2009 at 11:12 AM, Chan Chung Hang Christopher
christopher.c...@bradbury.edu.hk wrote:
in fact, upon some digging, it looks like you put RULES in
/etc/sysconfig/network-scripts/rule-ethX and ROUTES in
/etc/sysconfig/network-scripts/route-ethX
the lines in the rule-* file are run prefixed by `ip rule add` while the
lines in the route-* file are prefixed by `ip route add` on an interface
'up' event, and on the corresponding 'down' event, they are prefixed by
ip {route|rule} del
So does anyone have a clue on which is the syntax for creating complex
routes
and rules using route-* and rule-*?
Heh. I have not had time to go through the network scripts...last thing
I heard about was route-* but that was Centos/RHEL 4. Docs have been
lacking on this side of things...
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Multiple Internet facing Nics - Gateway issue
Bob you are so right! I made the mistake of not removing ip rule add and ip route add from each of the lines. Which caused the script, which wanted to add those itself, get confused. Now I have removed those and it brings up my routes on reboot and network restart. You will have to show the file contents and the actual error messages to get any serious help. did not work is not enough info. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Multiple Internet facing Nics - Gateway issue
So for those of you following this thread. This is what I ended up with that seems to be working. /etc/iproute2/rt_tables # # reserved values # 255 local 254 main 253 default 0 unspec # # local # #1 inr.ruhep 1 Cable 2 T1 /etc/sysconfig/network-scripts/rule-eth2 # Creates Rule Cable from xx.yy.51.46 table Cable # Sets up the routing rule from xx.yy.51.45 to default lookup Cable /etc/sysconfig/network-scripts/rule-eth3 # Creates Rule T1 from aa.bb.166.2 table T1 # Sets up the routing rule from aa.bb.166.2 to default lookup T1 /etc/sysconfig/network-scripts/route-eth2 # Sets up routing for Cable xx.yy.51.44/30 dev eth2 src xx.yy.51.45 table Cable default via xx.yy.51.45 table Cable # Sets up main routing table for Cable xx.yy.51.44/30 dev eth2 src xx.yy.51.45 # Sets up default route default via xx.yy.51.46 # Sets up route for internal network 192.168.4.0/24 dev eth0 proto kernel scope link src 192.168.4.1 table Cable /etc/sysconfig/network-scripts/route-eth3 # Sets up routing for T1 aa.bb.166.0/27 dev eth3 src aa.bb.166.2 table T1 default via aa.bb.166.2 table T1 # Sets up main routing table for T1 aa.bb.166.0/27 dev eth3 src aa.bb.166.2 # Sets up routing for internal network 192.168.4.0/24 dev eth0 proto kernel scope link src 192.168.4.1 table T1 Now where would the proper place be to put a route for load balancing like: ip route add default scope global nexthop via xx.yy.51.46 dev eth2 weight 3 nexthop via aa.bb.166.2 dev eth3 weight 1 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Multiple Internet facing Nics - Gateway issue
Christopher - you have been a great help! My internal network ip is 192.168.4.1 and I need it to access the aa.bb.166.2 interface or eth3. What would the rule look like that I need to add? On Thu, Jul 2, 2009 at 6:51 PM, Christopher Chan christopher.c...@bradbury.edu.hk wrote: As a follow up issue. The only thing that is not working properly is that I can not pull up my website that is hosted on this server from our private network. Do I need iproutes for my other two nics? I have never needed them before. That is because you never redirected routing lookups to the custom tables. You can either add routing entries for your internal network into those two custom tables or you can add two SNAT rules assuming you also use the box as a nat box for the Internet. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Multiple Internet facing Nics - Gateway issue
I am ecstatically confused. After I entered the last two commands my routing is working the way that I need it to. ip rule add from 173.11.51.46 table Cable ip rule add from 67.152.166.2 table T1 The problem is I don't know which actual commands worked. I had just rebooted. The other ip commands were all in the rc.local file so they all ran. Why did the above commands make the Cable and T1 rules show up in the rules list but the following two did not? ip route add 173.11.51.44/30 dev eth2 src 173.11.51.45 table Cable ip route add 67.152.166.0/27 dev eth3 src 67.152.166.2 table T1 Do I need all of the commands? So that what is in rc.local looks like this? ip rule add from 173.11.51.46 table Cable ip route add 173.11.51.44/30 dev eth2 src 173.11.51.45 table Cable ip route add default via 173.11.51.45 table Cable ip route add 173.11.51.44/30 dev eth2 src 173.11.51.45 ip route add default via 173.11.51.46 ip rule add from 173.11.51.45 to default lookup Cable ip rule add from 67.152.166.2 table T1 ip route add 67.152.166.0/27 dev eth3 src 67.152.166.2 table T1 ip route add default via 67.152.166.2 table T1 ip route add 67.152.166.0/27 dev eth3 src 67.152.166.2 ip rule add from 67.152.166.2 to default lookup T1 ip route flush cache ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Multiple Internet facing Nics - Gateway issue
I was simply trying to follow the example in: http://lartc.org/howto/lartc.rpdb.multiple-links.html That is my introduction and main resource for what I was doing. If there is other resorces that any could suggest beyond the man page I wold be interested to understanding this better. As a follow up issue. The only thing that is not working properly is that I can not pull up my website that is hosted on this server from our private network. Do I need iproutes for my other two nics? I have never needed them before. Thanks again for all your help On Thu, Jul 2, 2009 at 8:06 AM, Chan Chung Hang Christopher christopher.c...@bradbury.edu.hk wrote: Doug Coats wrote: I am ecstatically confused. After I entered the last two commands my routing is working the way that I need it to. ip rule add from 173.11.51.46 table Cable ip rule add from 67.152.166.2 table T1 The problem is I don't know which actual commands worked. I had just rebooted. The other ip commands were all in the rc.local file so they all ran. Why did the above commands make the Cable and T1 rules show up in the rules list but the following two did not? The following too are not ip rules. They are ip routing table entries. They will show up if you run 'ip route list table Cable' ip route add 173.11.51.44/30 dev eth2 src 173.11.51.45 table Cable ip route add 67.152.166.0/27 dev eth3 src 67.152.166.2 table T1 Do I need all of the commands? So that what is in rc.local looks like this? Take a look at the ones I posted...they are taken from rc.local since I have not taken to effort to integrate them elsewhere per interface. ip rule add from 173.11.51.46 table Cable ip route add 173.11.51.44/30 dev eth2 src 173.11.51.45 table Cable ip route add default via 173.11.51.45 table Cable ip route add 173.11.51.44/30 dev eth2 src 173.11.51.45 ip route add default via 173.11.51.46 ip rule add from 173.11.51.45 to default lookup Cable ip rule add from 67.152.166.2 table T1 ip route add 67.152.166.0/27 dev eth3 src 67.152.166.2 table T1 ip route add default via 67.152.166.2 table T1 ip route add 67.152.166.0/27 dev eth3 src 67.152.166.2 ip rule add from 67.152.166.2 to default lookup T1 ip route flush cache I find it interesting that you have ip rule commands before the relevant ip route commands for the custom routing table... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Multiple Internet facing Nics - Gateway issue
I have a server with 4 nics. Two are using different internet connections, both with static IP's, and two are connected to our private network. The two internet facing nics seem to be battling over the gateway designation. Which ever I designate as the gateway the other stops responding to incoming traffic. I need both to listen to inbound traffic. One for our main web page and the other for another web server. I found some information of Iproute2 but that did not seem to solve my issues. Here are the config files: ifcfg-eth2 DEVICE=eth2 BOOTPROTO=static HWADDR=00:24:E8:52:92:8E ONBOOT=yes IPADDR=xx.yy.51.45 NETMASK=255.255.255.252 GATEWAY=xx.yy.51.46 ifcfg-eth3 DEVICE=eth3 BOOTPROTO=static HWADDR=00:24:E8:52:92:90 ONBOOT=yes IPADDR=aa.bb.166.2 NETMASK=255.255.255.224 GATEWAY=aa.bb.166.1 network NETWORKING=yes NETWORKING_IPV6=no HOSTNAME=heritage01 GATEWAY=xx.yy.51.46 GATEWAYDEV=eth2 rt_tables # # reserved values # 255 local 254 main 253 default 0 unspec # # local # #1 inr.ruhep 200 Cable 201 T1 iproute2 routes ip route add xx.yy.51.44/30 dev eth2 src xx.yy.51.46 table Cable ip route add default via xx.yy.51.46 ip route add xx.yy.51.44/30 dev eth2 src xx.yy.51.46 ip route add default via xx.yy.51.46 ip rule add from xx.yy.51.46 table Cable ip route add aa.bb.166.0/27 dev eth3 src aa.bb.165.2 table T1 ip route add default via aa.bb.166.1 ip route add aa.bb.166.0/27 dev eth3 src aa.bb.166.2 ip rule add from aa.bb.166.2 table T1 ip route flush cache Other people seem to be using this configuration successfully but I seem to be missing something important. Any help is greatly appreciated!!! Thanks! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Multiple Internet facing Nics - Gateway issue
Thanks for your responses. I have tried some of the configurations that you have mentioned but not all of them. I will try the others tonight when the server is less active. In the meantime I will read the links you sent. Thanks again. This is starting to drive me crazy. On Wed, Jul 1, 2009 at 3:07 PM, Alexander Dalloz ad+li...@uni-x.orgad%2bli...@uni-x.org wrote: Doug Coats schrieb: I have a server with 4 nics. Two are using different internet connections, both with static IP's, and two are connected to our private network. The two internet facing nics seem to be battling over the gateway designation. Which ever I designate as the gateway the other stops responding to incoming traffic. I need both to listen to inbound traffic. One for our main web page and the other for another web server. I found some information of Iproute2 but that did not seem to solve my issues. Here are the config files: ifcfg-eth2 DEVICE=eth2 BOOTPROTO=static HWADDR=00:24:E8:52:92:8E ONBOOT=yes IPADDR=xx.yy.51.45 NETMASK=255.255.255.252 GATEWAY=xx.yy.51.46 ifcfg-eth3 DEVICE=eth3 BOOTPROTO=static HWADDR=00:24:E8:52:92:90 ONBOOT=yes IPADDR=aa.bb.166.2 NETMASK=255.255.255.224 GATEWAY=aa.bb.166.1 network NETWORKING=yes NETWORKING_IPV6=no HOSTNAME=heritage01 GATEWAY=xx.yy.51.46 GATEWAYDEV=eth2 rt_tables # # reserved values # 255 local 254 main 253 default 0 unspec # # local # #1 inr.ruhep 200 Cable 201 T1 iproute2 routes ip route add xx.yy.51.44/30 dev eth2 src xx.yy.51.46 table Cable ip route add default via xx.yy.51.46 ip route add xx.yy.51.44/30 dev eth2 src xx.yy.51.46 ip route add default via xx.yy.51.46 ip rule add from xx.yy.51.46 table Cable ip route add aa.bb.166.0/27 dev eth3 src aa.bb.165.2 table T1 ip route add default via aa.bb.166.1 ip route add aa.bb.166.0/27 dev eth3 src aa.bb.166.2 ip rule add from aa.bb.166.2 table T1 ip route flush cache Other people seem to be using this configuration successfully but I seem to be missing something important. Any help is greatly appreciated!!! Thanks! The GATEWAY parameter within the ifcfg-ethX configuration files tries to set the default gateway. There can be just 1 default gateway for a system. So, the interface which comes up first will set the route and the other has no effect. Remove the GATEWAY entry from all ifcfg-ethX files and place the GATEWAY parameter into /etc/sysconfig/network only. Running different networks you must can set additional routings by route-ethX configuration files inside /etc/sysconfig/network-scripts/. Given your default gateway is set as xx.yy.51.46 for the network configured on eth2, you set to use a gateway aa.bb.166.1 for other destinations by ip route add targetnet/CIDR via aa.bb.166.1 dev eth3 Please see http://www.centos.org/docs/5/html/5.1/Deployment_Guide/s1-networkscripts-static-routes.html You multiple uplink topic is documented in this howto http://lartc.org/howto/lartc.rpdb.multiple-links.html Alexander ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Multiple Internet facing Nics - Gateway issue
I changed those two rules to no affect. I have also done the above mentioned things. My tcpdump shows connections comming in on eth3 but there is no outbound communication. Example: tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth3, link-type EN10MB (Ethernet), capture size 96 bytes 20:21:11.915624 IP 41.178.204.108.25591 ipaa-bb-166-2.z166-152-67.customer.algx.net.smtp: S 3528290937:3528290937(0) win 65535 mss 1442,nop,wscale 2,nop,nop,sackOK 20:21:14.892106 IP 41.178.204.108.25591 ipaa-bb-166-2.z166-152-67.customer.algx.net.smtp: S 3528290937:3528290937(0) win 65535 mss 1442,nop,wscale 2,nop,nop,sackOK 20:21:16.017705 20:21:16.663301 IP newsletter.publicradio.org.54562 ipaa-bb-166-2.z166-152-67.customer.algx.net.smtp: S 1665702165:1665702165(0) win 5840 mss 1460,sackOK,timestamp 3732071063 0,nop,wscale 3 20:21:17.658835 IP client-201.230.112.209.speedy.net.pe.12095 ipaa-bb-166-2.z166-152-67.customer.algx.net.smtp: S 2778637809:2778637809(0) win 65535 mss 1400,nop,wscale 1,nop,nop,sackOK An abreviated lsof -i4 -n COMMANDPID USER FD TYPE DEVICE SIZE NODE NAME mysqld4004 mysql 10u IPv4 8750 TCP *:mysql (LISTEN) spamd 4056 root5u IPv4 8943 TCP 127.0.0.1:783 (LISTEN) sendmail 4076 root4u IPv4 9094 TCP *:smtp (LISTEN) httpd 4110 root4u IPv4 9117 TCP aa.bb.166.2:http (LISTEN) httpd 4166 apache4u IPv4 9117 TCP aa.bb.166.2:http (LISTEN) httpd 4167 apache4u IPv4 9117 TCP aa.bb.166.2:http (LISTEN) httpd 4168 apache4u IPv4 9117 TCP aa.bb.166.2:http (LISTEN) So it appears to me that the device is listening but it never picks up the phone. Any thoughts? On Wed, Jul 1, 2009 at 7:00 PM, Christopher Chan christopher.c...@bradbury.edu.hk wrote: ip rule add from xx.yy.51.46 table Cable ip rule add from aa.bb.166.2 table T1 Other people seem to be using this configuration successfully but I seem to be missing something important. Change the above rules to: ip rule add from xx.yy.51.46 to default lookup Cable ip rule add from aa.bb.166.2 to default lookup T1 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Multiple Internet facing Nics - Gateway issue
Thanks for your responce! If I open up Iptables to accept everything on eth3 and eth2 or turn it off all together I get the same results. I will have to look through your iproute2 commands to see how they match up to mine. Do you see anything different in mine that would indicate the issue? On Wed, Jul 1, 2009 at 9:25 PM, Christopher Chan christopher.c...@bradbury.edu.hk wrote: Hello Doug, Here are the iproute2 commands for a multigateway setup I did. ip route add 220.232.217.72/29 dev eth0 proto kernel scope link src 220.232.217.78 table pacific ip route add 10.9.0.0/17 dev eth1 proto kernel scope link src 10.9.1.101 table pacific ip route add default via 220.232.217.73 dev eth0 table pacific ip route add 203.174.45.24/29 dev eth2 proto kernel scope link src 203.174.45.30 table wharf ip route add 10.9.0.0/17 dev eth1 proto kernel scope link src 10.9.1.101 table wharf ip route add default via 203.174.45.25 dev eth2 table wharf ip route add 59.152.193.16/29 dev eth2 proto kernel scope link src 59.152.193.22 table frahw ip route add 10.9.0.0/17 dev eth1 proto kernel scope link src 10.9.1.101 table frahw ip route add default via 59.152.193.17 dev eth2 table wharf ip route add 10.9.0.0/17 dev eth1 proto kernel scope link src 10.9.1.101 table saurer ip route add 10.0.0.0/8 via 10.9.0.1 dev eth1 table saurer ip rule add from 220.232.217.78 to default lookup pacific ip rule add from 203.174.45.30 to default lookup wharf You may also want to check your firewall rules too. I must also say that there are no GATEWAY entries in my ifcfg-ethx. Only one in network. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Multiple Internet facing Nics - Gateway issue
I am not understanding somethings very fundamental to me troubleshooting this issue. How do I clear the iproute2's that I have created? How do I tell if they are in affect? What should they look like when listed if they are configured properly? Thanks for holding my hand in this! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Multiple Internet facing Nics - Gateway issue
I am convinced that my iproute2 tables are all messed upIn fact I found some errors in my initial post. # ip rule list 0: from all lookup 255 32766: from all lookup main 32767: from all lookup default /etc/iproute2/rt_tables # # reserved values # 255 local 254 main 253 default 0 unspec # # local # #1 inr.ruhep 200 Cable 201 T1 So Cable and T1 are not even showing up in the list. When I run my ip commands from the command line I get the following results for each line. # ip route add 173.11.51.44/30 dev eth2 src 173.11.51.45 table Cable # ip route add default via 173.11.51.45 table Cable # ip route add 173.11.51.44/30 dev eth2 src 173.11.51.45 RTNETLINK answers: File exists # ip route add default via 173.11.51.46 RTNETLINK answers: File Exists # ip rule add from 173.11.51.45 to default lookup Cable RTNETLINK answers: Numerical result out of range # ip route add 67.152.166.0/27 dev eth3 src 67.152.166.2 table T1 # ip route add default via 67.152.166.2 table T1 # ip route add 67.152.166.0/27 dev eth3 src 67.152.166.2 RTNETLINK answers: File Exists # ip rule add from 67.152.166.2 to default lookup T1 RTNETLINK answers: Numerical result out of range So the first few lines run fine for each table and then I start getting errors. Are these all the commands that I need to use to set this up? I know that when I first entered them by hand the T1 and Cable showed up in the tables list. Am I going crazy? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Multiple Internet facing Nics - Gateway issue
So if I run the following two commands the rules show up in the list. ip rule add from 173.11.51.46 table Cable ip rule add from 67.152.166.2 table T1 # ip rule list 0: from all lookup 255 32764: from 67.152.166.2 lookup T1 32765: from 173.11.51.46 lookup Cable 32766: from all lookup main 32767: from all lookup default So why does that work but my other command not? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Forcing ifcfg-eth0 to use the same nic in multi nic machine
I am new to CentOS (coming from Fedora) and I really like it! I am having difficulty getting one of my machines to boot and assign the same designation of eth0 and eth1 to the same nics consistantly. I have an MSI motherboard with 2 nics on the board. Strangely enough both nics report the same MAC address. This is not an issue since I use the computer to route between two different subnets so they don't see each other on the network. The problem comes when I reboot and they race against each other to see which one will get to be eth0. If they switch my routing dies and I loose access with out rebooting and hoping they switch back or switching the actual cables. I have googled and searched my networking resources but all of the fixes that I have found focus on using the MAC address to solve the problem but in my case they are the same. The only difference is that they use different drivers. One is a Realtek and other is a Marvell. I have turned off Kudzu or they reconfigured every time a booted the machine. It only happens every once in a while but I need it to be consistent. Any suggestions or pushes in the right direction would be most appreciated. Doug Coats ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Re: Forcing ifcfg-eth0 to use the same nic in multi nic machine
Is the boards bios up to date? Yes Do you have the proper alias entries in /etc/modprobe.conf? These are the relevent listings in the modprobe.conf alias eth0 r8169 alias eth1 forcedeth ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Forcing ifcfg-eth0 to use the same nic in multi nic machine
As far as I understand networking, if you only have 1 MAC, you only have 1 NIC. You might have 2 connectors, but that seems really strange. It seems like this is some sort of undefined behavior. I think that having only 1 MAC really *IS* an issue. I have used these boards(I have 6 of the same motherboard) for about 3 years now with no problems, until I upgraded the OS this summer from Fedora Core 4 to CentOS 5. With every windows install and Linux install on these mother boards they report two separate nics that can both be configured and active at the same time with the same MAC address. Doug ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
