Re: [SCIENTIFIC-LINUX-USERS] network port issue with Scientific Linux 6.3
It looks like you've trimmed a bit off of the ifcfg-eth* scripts. I'd expect to see a UUID, HWADDR, NAME, and LAST_CONNECT. Any chance for the untrimmed config files? Out of curiosity, what does 'nm-tool' report on this system? If possible I'd love a before and after the problem. Pat On 08/14/2013 08:16 AM, Edison, Arul (GE Healthcare) wrote: Hi , I am using the repacked version of Scientific Linux 6.3 My PC has a mother board , which has 2 Ethernet port eth0 is connected to a device & IP configured for eth0 is 192.168.2.1 eth1 is connected to a hub. This is intern connected with another PC. IP configured for eth0 is 192.168.1.20 The issue here is eth0 IP Address is now got changed to the IP address of eth1 when the Device connected with eth0 become powered on . With this, eth0 & eth1 has same IP address. Because of this the application running on Scientific Linux 6.3 PC is not able to communicate with the Device connected with eth0. I have enclosed the /var/log/message file below for the reference Please suggest me what is the configuration to be done for the same? /etc/sysconfig/network-scripts/ifcfg-eth0 file from system is as below:- *** DEVICE=eth0 ONBOOT=yes BOOTPROTO=none IPADDR=192.168.2.1 NETMASK=255.255.255.0 /etc/sysconfig/network-scripts/ ifcfg-eth1 file from system is as below:- * DEVICE=eth1 BOOTPROTO=none #IPADDR=192.168.1.90 IPADDR=192.168.1.20 NETMASK=255.255.255.0 When the Scientific Linux 6.3 Pc is booted , the network configuration of the system is as below:- eth0 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A6 inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:16 Memory:fdbc-fdbe eth1 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A7 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:381 errors:0 dropped:0 overruns:0 frame:0 TX packets:267 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:26234 (25.6 KiB) TX bytes:29696 (29.0 KiB) Interrupt:17 Memory:fddc-fdde loLink 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 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:240 (240.0 b) TX bytes:240 (240.0 b) When the Device that is connected to the eth0 is powered on and booted, the network configuration of the system changed as below:- * eth0 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A6 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:240 (240.0 b) TX bytes:9814 (9.5 KiB) Interrupt:16 Memory:fdbc-fdbe eth1 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A7 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6077 errors:0 dropped:0 overruns:0 frame:0 TX packets:4412 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:427716 (417.6 KiB) TX bytes:287127 (280.3 KiB) Interrupt:17 Memory:fddc-fdde loLink 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 RX packets:42683 errors:0 dropped:0 overruns:0 frame:0 TX packets:42683 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4447027 (4.2 MiB) TX bytes:4447027 (4.2 MiB) /var/log/message file is as below:- ** Aug 17 11:54:42 magic kernel: ttyS2: LSR safety check engaged! Aug 17 11:54:46 magic kernel: ttyS2: LSR safety check engaged! Aug 17 11:54:57 magic kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Aug 17 11:54:57 magic kernel: A
Re: New Install of 6.4 - no Internet step 2, 3, 4 -- 5 - What works & Does not
On Wed, 14 Aug 2013, Larry Linder wrote: Gigabyte 970A-DS3 with Quad core AMD. SL 5.8 loads and everything works. Fedora 19 loads and everything works. kernel linux 3.9.5-301.fc19 SL 6.4 loads and when network is set up. Realtech on board chip set RTL 8168/811E as marked on chip. Network will not connect. Ping 192.168.0.1 - router and it runs ping and no return from router. "ifconfig" eth0 receives data but TX is always "0". Tried different drivers for realtech chip - nothing worked and most would fail when you "restart" no eth0. Fresh install of 6.4 with network set up - same result - no network TX. Loaded new Kernel from Elrepo.kernel-it-3.0.89-el6.elrepo.x86_64.rpm Installed with rpm -i *.rpm. rebooted system touched key to select new kernel at boot. "ifconfig" eth0 receives data and transmits data. network now connects and everything now works. Conclusion is the kernel supplied in 6.4 has a mistake somewhere, realtech driver and hardware are good. Does SL 6.3 work out of the box? Each "point" release has many kernel changes. If it is known if 6.3 works but 6.4 does not then that helps to pins down when the problem was induced. -Connie Sieh r8168 driver works with SL5.8. Installing new kernel solved the problem. r8169 driver is used with Fedora 19. Have learned more than I wanted to know. Thank you all for your help. Larry Linder On Tuesday 13 August 2013 11:57 am, Larry Linder wrote: On Monday 12 August 2013 10:41 am, Larry Linder wrote: On Friday 09 August 2013 12:44 pm, you wrote: On Fri, Aug 9, 2013 at 7:19 AM, Larry Linder wrote: Have you looked at ELRepo? Particularly, FAQ#4 at http://elrepo.org/tiki/FAQ may help you find the right driver for the NIC. Akemi The problem with the MB's using RTL8168/8111 has been know for a few years. The 32 bit version of SL 6.2 works - have not verified it. We need to use SL 64 our system. Installed Windows 7 on a spare disk, Internet found and worked - hardware is checked. Downloaded new driver from "realtech.com" for RTL8168/8111 and sneaker net ed it over to SL 6.4 box applied the new driver. New driver must have a problem with the 64 bit interface - or SL 6 X _64 code is broken somewhere. Did you have a chance to identify your device IDs (see above, my note)? I have a system with the following NIC: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 02) The motherboard is GA-MA785GM-US2H. I use ELRepo's driver from kmod-r8168-8.032.00-1.el6.elrepo.x86_64. The OS is SL 6.4 (64-bit) but this machine has been running SL for at least 3 years with no apparent network trouble. Akemi Tried the driver from elrepo.X86.64 - did not work - A direct install of SL6.4 resulted in eth0 receiving data but not transmission. Installing new driver resulted in eth0 not being recognized. Ping quit - no eth0 found. "ifconfig" confirms that there is not eth0. We had to enable IOMMU on mother board and then Fedora 19 live would load. The driver used was in Fedora 19 was R1869- Internet was working. Tried using r1869 with SL 6.4 and eth0 was not listed in "ifconfig" Numerous people on net said that SL 6.4 32 bit version would load and Ethernet worked. May try this a later today to verify it. Reloading SL 6.4 from DVD this AM to use system as an isolated box. Any help would be appreciated. Learned more about drivers than I wanted to know. Comment: Fedora 19 with the latest Gnome desktop is written for a tablet. It only takes 6 mouse clicks to do anything useful - Hope RH 7 will allow a person to select an older version of KDE or Gnome. I would hate to think of the number of "mouse ites" injuries we could have. Is there a number of simpler desktops available. The new KDE is useless, Gnome in Fidora 19 is terrible so where do people who need a no BS computer go? Thank You All Larry Linder The mystery of why there is no Internet on 6.4 using the Gigabyte board become more confusing. We were looking at our hardware list and decided that boxes deployed two years ago had essentially the same NIC stuff and they worked with 5.5 - 5.9. We loaded 5.8 into new Gigabyte hardware and guess what it worked perfectly !!! The 6.4 DVD was down loaded and checked and everything matches. There is something wrong in the Gnome system network set up. SL 5.8 has a very different network setup. We got pretty suspicious when we loaded updated driver and new Kernel 3.0.8 and same result. Too many people stated that this worked. SL 6.4 is loading for the nth time and we will use another scheme to setup network. Thank You All Larry Linder
Re: New Install of 6.4 - no Internet step 2, 3, 4 -- 5 - What works & Does not
On Wednesday 14 August 2013 11:04 am, Connie Sieh wrote: > On Wed, 14 Aug 2013, Larry Linder wrote: > > Gigabyte 970A-DS3 with Quad core AMD. > > SL 5.8 loads and everything works. > > > > Fedora 19 loads and everything works. > > kernel linux 3.9.5-301.fc19 > > > > SL 6.4 loads and when network is set up. Realtech on board chip set RTL > > 8168/811E as marked on chip. > > Network will not connect. > > Ping 192.168.0.1 - router and it runs ping and no return from router. > > "ifconfig" > > eth0 receives data but TX is always "0". > > Tried different drivers for realtech chip - nothing worked and most would > > fail when you "restart" no eth0. > > Fresh install of 6.4 with network set up - same result - no network TX. > > Loaded new Kernel from Elrepo.kernel-it-3.0.89-el6.elrepo.x86_64.rpm > > Installed with rpm -i *.rpm. > > rebooted system > > touched key to select new kernel at boot. > > "ifconfig" > > eth0 receives data and transmits data. > > network now connects and everything now works. > > > > Conclusion is the kernel supplied in 6.4 has a mistake somewhere, > > realtech driver and hardware are good. > > Does SL 6.3 work out of the box? Each "point" release has many kernel > changes. If it is known if 6.3 works but 6.4 does not then that helps to > pins down when the problem was induced. > > -Connie Sieh > > > r8168 driver works with SL5.8. Installing new kernel solved the problem. > > r8169 driver is used with Fedora 19. > > > > Have learned more than I wanted to know. > > > > Thank you all for your help. > > Larry Linder > > > > On Tuesday 13 August 2013 11:57 am, Larry Linder wrote: > >> On Monday 12 August 2013 10:41 am, Larry Linder wrote: > >>> On Friday 09 August 2013 12:44 pm, you wrote: > On Fri, Aug 9, 2013 at 7:19 AM, Larry Linder > > wrote: > >>> Have you looked at ELRepo? Particularly, FAQ#4 at > >>> http://elrepo.org/tiki/FAQ may help you find the right driver for > >>> the NIC. > >>> > >>> Akemi > > > > The problem with the MB's using RTL8168/8111 has been know for a few > > years. The 32 bit version of SL 6.2 works - have not verified it. > > We need to use SL 64 our system. > > > > Installed Windows 7 on a spare disk, Internet found and worked - > > hardware is checked. > > > > Downloaded new driver from "realtech.com" for RTL8168/8111 and > > sneaker net ed it over to SL 6.4 box applied the new driver. > > New driver must have a problem with the 64 bit interface - or SL 6 X > > _64 code is broken somewhere. > > Did you have a chance to identify your device IDs (see above, my > note)? > > I have a system with the following NIC: > > 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. > RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev > 02) > > The motherboard is GA-MA785GM-US2H. > > I use ELRepo's driver from kmod-r8168-8.032.00-1.el6.elrepo.x86_64. > The OS is SL 6.4 (64-bit) but this machine has been running SL for at > least 3 years with no apparent network trouble. > > Akemi > >>> > >>> Tried the driver from elrepo.X86.64 - did not work - > >>> A direct install of SL6.4 resulted in eth0 receiving data but not > >>> transmission. Installing new driver resulted in eth0 not being > >>> recognized. Ping quit - no eth0 found. "ifconfig" confirms that there > >>> is not eth0. > >>> > >>> We had to enable IOMMU on mother board and then Fedora 19 live would > >>> load. The driver used was in Fedora 19 was R1869- Internet was > >>> working. > >>> > >>> Tried using r1869 with SL 6.4 and eth0 was not listed in "ifconfig" > >>> > >>> Numerous people on net said that SL 6.4 32 bit version would load and > >>> Ethernet worked. May try this a later today to verify it. > >>> > >>> Reloading SL 6.4 from DVD this AM to use system as an isolated box. > >>> > >>> Any help would be appreciated. > >>> Learned more about drivers than I wanted to know. > >>> > >>> Comment: > >>> Fedora 19 with the latest Gnome desktop is written for a tablet. It > >>> only takes 6 mouse clicks to do anything useful - Hope RH 7 will allow > >>> a person to select an older version of KDE or Gnome. > >>> I would hate to think of the number of "mouse ites" injuries we could > >>> have. Is there a number of simpler desktops available. > >>> The new KDE is useless, Gnome in Fidora 19 is terrible so where do > >>> people who need a no BS computer go? > >>> > >>> Thank You All > >>> > >>> Larry Linder > >> > >> The mystery of why there is no Internet on 6.4 using the Gigabyte board > >> become more confusing. > >> We were looking at our hardware list and decided that boxes deployed two > >> years ago had essentially the same NIC stuff and they worked with 5.5 - > >> 5.9. We loaded 5.8 into new Gigabyte hardware and guess what it worked > >> perfectly !!! > >> The 6.4 DVD was down loaded and checked and everyth
