Hi Girish Pls find the location of the driver , download and try loading the driver . http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false Regrads Karthik redhat-list-request@xxxxxxxxxx wrote: Send redhat-list mailing list submissions to redhat-list@xxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit https://www.redhat.com/mailman/listinfo/redhat-list or, via email, send a message with subject or body 'help' to redhat-list-request@xxxxxxxxxx You can reach the person managing the list at redhat-list-owner@xxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of redhat-list digest..." Today's Topics: 1. RE: network card not detected in rhel 5 (Geofrey Rainey) 2. need squid help (Anil Saini) 3. Re: need squid help (Madan Thapa) 4. squid request overloaded (Anil Saini) 5. Re: squid request overloaded (Marcos Aurelio Rodrigues) 6. Samba + CUPS high cpu usage and huge logfiles (Marco Nesler) 7. Re: NIC Teaming (Michael Simpson) 8. RE: NIC Teaming (Gerrard Geldenhuis) 9. Re: NIC Teaming (Michael Simpson) 10. RE: NIC Teaming (Gerrard Geldenhuis) 11. Re: NIC Teaming (Michael Simpson) 12. RE: NIC Teaming (Gerrard Geldenhuis) 13. RE: NIC Teaming (John Horne) ---------------------------------------------------------------------- Message: 1 Date: Mon, 31 Mar 2008 10:21:16 +1300 From: "Geofrey Rainey" Subject: RE: network card not detected in rhel 5 To: "General Red Hat Linux discussion list" Message-ID: Content-Type: text/plain; charset="us-ascii" Try reinstalling and at the prompt type > linux noprobe, and then you can select the drivers you want to load for your hardware(obviously you need To identify what driver should work with that chipset). -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of girish Sent: Friday, 28 March 2008 8:37 p.m. To: General Red Hat Linux discussion list Subject: network card not detected in rhel 5 Hi Everybody, I purchased a new system. My system configuration is core 2 duo processor , 2GB RAM and 160GB SATA hard disk. I installed RHEL 5 on it. After installing I found out that the network card is not detected. My NIC card is Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC. I even searched the net to get the drivers but I could not find any driver for it. Please help me to solve the problem. Thanking you in advance Girish. M -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list ========================================================== For more information on the Television New Zealand Group, visit us online at tvnz.co.nz ========================================================== CAUTION: This e-mail and any attachment(s) contain information that is intended to be read only by the named recipient(s). This information is not to be used or stored by any other person and/or organisation. ------------------------------ Message: 2 Date: Mon, 31 Mar 2008 12:09:31 +0530 From: "Anil Saini" Subject: need squid help To: redhat-list@xxxxxxxxxx Message-ID: <61d1be380803302339j696414d7xfa4535b8ca5ed657@xxxxxxxxxxxxxx> Content-Type: text/plain; charset=ISO-8859-1 how can i block port 443 for all sites except gmail and gtalk i tried acl https url_regex -i www.gmail.com https_access https allow https_access deny all but it is not working is it correct.... -- Anil Saini M.E. - Software Systems B.E. - Electronics and Communication Project Assistant CISCO LAB Information Processing Center Unit BITS-PILANI ------------------------------ Message: 3 Date: Mon, 31 Mar 2008 12:25:54 +0530 From: "Madan Thapa" Subject: Re: need squid help To: "General Red Hat Linux discussion list" Message-ID: <3a4237470803302355hce232d6ie16631e853746f18@xxxxxxxxxxxxxx> Content-Type: text/plain; charset=ISO-8859-1 On Mon, Mar 31, 2008 at 12:09 PM, Anil Saini wrote: > how can i block port 443 for all sites except gmail and gtalk > i tried > acl https url_regex -i www.gmail.com > https_access https allow > https_access deny all > > but it is not working > is it correct.... > =======> You can do it with IPtables: Testing ############### [root@~]# telnet hotmail.com 443 Trying 64.4.32.7... Connected to hotmail.com (64.4.32.7). Escape character is '^]'. quit [root@ ~]# iptables -I OUTPUT -d hotmail.com -p tcp --dport 443 -j DROP [root@ ~]# telnet hotmail.com 443 Trying 64.4.32.7... [root@ ~]# telnet gmail.com 443 Trying 64.233.161.83... Connected to gmail.com (64.233.161.83). Escape character is '^]'. quit Connection closed by foreign host. [root@ ~]# So , in your case the following rules should work: ### First allow ### /sbin/iptables -I OUTPUT -d gmail.com -p tcp --dport 443 -j ACCEPT /sbin/iptables -I OUTPUT -d -p tcp --dport 443 -j ACCEPT ### Then Deny ### /sbin/iptables -I OUTPUT -p tcp --dport 443 -j DROP ------------------------------ Message: 4 Date: Mon, 31 Mar 2008 13:03:23 +0530 From: "Anil Saini" Subject: squid request overloaded To: redhat-list@xxxxxxxxxx Message-ID: <61d1be380803310033iffb0a13gcc63371876aac485@xxxxxxxxxxxxxx> Content-Type: text/plain; charset=ISO-8859-1 m using squid on openBSD 4.2 my cache.log shows dnssubmit: queue overloaded, rejecting xxxxx.com dnssubmit: queue overloaded, rejecting xxxxx.com dnssubmit: queue overloaded, rejecting xxxxx.com dnssubmit: queue overloaded, rejecting xxxxx.com dnssubmit: queue overloaded, rejecting xxxxx.com how i solve this problem -- Anil Saini M.E. - Software Systems B.E. - Electronics and Communication Project Assistant CISCO LAB Information Processing Center Unit BITS-PILANI ------------------------------ Message: 5 Date: Mon, 31 Mar 2008 08:23:22 -0300 From: "Marcos Aurelio Rodrigues" Subject: Re: squid request overloaded To: "General Red Hat Linux discussion list" Message-ID: Content-Type: text/plain; charset=ISO-8859-1 If you are using OpenBSD 4.2 you hat to send a message to the 4.2BSD list. I think you are using the cache_dns_program directive and you need to increase the number of childrens. -- ======================================== Marcos Aurelio Rodrigues (DEiGrAtiA-33) CCNA, MCSO Mirabilia laudo semprer, Dei ======================================== On Mon, Mar 31, 2008 at 4:33 AM, Anil Saini wrote: > m using squid on openBSD 4.2 > > my cache.log shows > > dnssubmit: queue overloaded, rejecting xxxxx.com > dnssubmit: queue overloaded, rejecting xxxxx.com > dnssubmit: queue overloaded, rejecting xxxxx.com > dnssubmit: queue overloaded, rejecting xxxxx.com > dnssubmit: queue overloaded, rejecting xxxxx.com > > how i solve this problem > > > -- > Anil Saini > M.E. - Software Systems > B.E. - Electronics and Communication > > Project Assistant > CISCO LAB > Information Processing Center Unit > BITS-PILANI > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > ------------------------------ Message: 6 Date: Mon, 31 Mar 2008 14:32:54 +0200 From: "Marco Nesler" Subject: Samba + CUPS high cpu usage and huge logfiles To: redhat-list@xxxxxxxxxx Message-ID: Content-Type: text/plain; charset=UTF-8 hi all, i'm running a rhel 5.1 with samba (stand-alone) and cups just for printers sharing. I noticed that my cupsd process always uses around 7-10% cpu this is quite strange because the usage is very low (less than 1-2 print jobs every 10-15mins). Looking at my logs I noticed that cups logs are really huge, I found a string like this one repeated several times on my access log: localhost - - [31/Mar/2008:14:28:13 +0200] "POST / HTTP/1.1" 200 188 Get-Printer-Attributes successful-ok Googling around I found some info on samba + cups integration, and it seems this is a samba bug, basically samba asks cups for printer details several times for every printer, flooding the logs: http://www.usenetlinux.com/archive/topic.php/t-891220.html I cannot use the suggested workaround, i'm not managing properties and drivers of the printers from samba, is there any other workaround who does not involve the recompilation of the whole package ? Any suggestion ? thank you marco ------------------------------ Message: 7 Date: Mon, 31 Mar 2008 13:34:56 +0100 From: "Michael Simpson" Subject: Re: NIC Teaming To: "General Red Hat Linux discussion list" Message-ID: <82abd3a70803310534u7ed377f1v61f06ff714e8bc05@xxxxxxxxxxxxxx> Content-Type: text/plain; charset=ISO-8859-1 On 3/27/08, Gerrard Geldenhuis wrote: > Hi Vivek, > It is also called bonding which might yield better results in google. > > It is actually very simple: > Create a new file called ifcfg-bond0 in /etc/sysconfig/network-scripts/ > with the following data inside: > DEVICE=bond0 > BOOTPROTO=static > ONBOOT=yes > IPADDR=Your ip here > NETMASK=Your netmask here > > In the interface that you want as part of the bond edit the appropriate > file. For example ifcfg-eth0 and ifcfg-eth2 which can also be found in > /etc/sysconfig/network-scripts/ > > You should edit out the ip address and netmask. Make sure the bootproto > is none, keep the hardware address, add slave=yes and add master=bond0 > > DEVICE=eth0 > BOOTPROTO=none > HWADDR=AA:AA:C4:BE:AA:AA > ONBOOT=yes > TYPE=Ethernet > SLAVE=yes > MASTER=bond0 > Hi there i thought that you were meant to remove the HWADDR= lines from ifcfg-eth0 and ifcfg-eth1 as bonding manipulates these values to make the necessary arp magic work. the documentation seems to support this view. mike ------------------------------ Message: 8 Date: Mon, 31 Mar 2008 13:53:50 +0100 From: "Gerrard Geldenhuis" Subject: RE: NIC Teaming To: "General Red Hat Linux discussion list" Message-ID: Content-Type: text/plain; charset="us-ascii" Leaving the values won't confuse the bonding driver. I leave them specifically because that helps to tie down interface so they are always the same. eth0 will thus always be the same physical interface and so on. Can you point me to the documentation that supports removing hwaddr lines... It is also likely that the manipulation of configuration files differs from distro to distro... The bonding driver documentation states that you can specify options for the bond interface in the ifcfg-bondX file but that has not been the case for me. I still have to specify options in the /etc/modprobe.conf file. Regards > -----Original Message----- > From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list- > bounces@xxxxxxxxxx] On Behalf Of Michael Simpson > Sent: 31 March 2008 13:35 > To: General Red Hat Linux discussion list > Subject: Re: NIC Teaming > > On 3/27/08, Gerrard Geldenhuis wrote: > > Hi Vivek, > > It is also called bonding which might yield better results in google. > > > > It is actually very simple: > > Create a new file called ifcfg-bond0 in /etc/sysconfig/network-scripts/ > > with the following data inside: > > DEVICE=bond0 > > BOOTPROTO=static > > ONBOOT=yes > > IPADDR=Your ip here > > NETMASK=Your netmask here > > > > In the interface that you want as part of the bond edit the appropriate > > file. For example ifcfg-eth0 and ifcfg-eth2 which can also be found in > > /etc/sysconfig/network-scripts/ > > > > You should edit out the ip address and netmask. Make sure the bootproto > > is none, keep the hardware address, add slave=yes and add master=bond0 > > > > DEVICE=eth0 > > BOOTPROTO=none > > HWADDR=AA:AA:C4:BE:AA:AA > > ONBOOT=yes > > TYPE=Ethernet > > SLAVE=yes > > MASTER=bond0 > > > > Hi there > > i thought that you were meant to remove the HWADDR= lines from > ifcfg-eth0 and ifcfg-eth1 as bonding manipulates these values to make > the necessary arp magic work. > > the documentation seems to support this view. > > mike > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list ------------------------------ Message: 9 Date: Mon, 31 Mar 2008 14:53:45 +0100 From: "Michael Simpson" Subject: Re: NIC Teaming To: "General Red Hat Linux discussion list" Message-ID: <82abd3a70803310653v7414c467jbf5764c4a9405eed@xxxxxxxxxxxxxx> Content-Type: text/plain; charset=ISO-8859-1 On 3/31/08, Gerrard Geldenhuis wrote: > Leaving the values won't confuse the bonding driver. I leave them > specifically because that helps to tie down interface so they are always > the same. eth0 will thus always be the same physical interface and so > on. i normally do this in modprobe.conf as something hinky happens on dells with more than 2 ethernet ports and udev :-) > > Can you point me to the documentation that supports removing hwaddr > lines... It is also likely that the manipulation of configuration files > differs from distro to distro... > http://www.linuxquestions.org/linux/answers/Networking/Linux_bonding_howto_0 also from bonding.txt All interfaces that are part of the trunk, should have SLAVE and MASTER definitions. For example, in the case of RedHat, if you wish to make eth0 and eth1 (or other interfaces) a part of the bonding interface bond0, their config files (ifcfg-eth0, ifcfg-eth1, etc.) should look like this: DEVICE=eth0 USERCTL=no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none from bond_main.c 16 * How it works: 17 * ifconfig bond0 ipaddress netmask up 18 * will setup a network device, with an ip address. No mac address 19 * will be assigned at this time. The hw mac address will come from 20 * the first slave bonded to the channel. All slaves will then use 21 * this hw mac address. 22 * 23 * ifconfig bond0 down 24 * will release all slaves, marking them as down. 25 * 26 * ifenslave bond0 eth0 27 * will attach eth0 to bond0 as a slave. eth0 hw mac address will either 28 * a: be used as initial mac address 29 * b: if a hw mac address already is there, eth0's hw mac address 30 * will then be set from bond0. 31 * The only reason i think this is that i have had problems with bonding with RH5.1 where i had the HWADDR values specified. bond0 wouldn't come up until i removed - indeed the box wouldn't boot - until i removed those lines from ifcfg-eth0 and 1 I could be wrong, i often am best wishes mike > The bonding driver documentation states that you can specify options for > the bond interface in the ifcfg-bondX file but that has not been the > case for me. I still have to specify options in the /etc/modprobe.conf > file. > > Regards > > > -----Original Message----- > > From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list- > > bounces@xxxxxxxxxx] On Behalf Of Michael Simpson > > Sent: 31 March 2008 13:35 > > To: General Red Hat Linux discussion list > > Subject: Re: NIC Teaming > > > > On 3/27/08, Gerrard Geldenhuis > wrote: > > > Hi Vivek, > > > It is also called bonding which might yield better results in > google. > > > > > > It is actually very simple: > > > Create a new file called ifcfg-bond0 in > /etc/sysconfig/network-scripts/ > > > with the following data inside: > > > DEVICE=bond0 > > > BOOTPROTO=static > > > ONBOOT=yes > > > IPADDR=Your ip here > > > NETMASK=Your netmask here > > > > > > In the interface that you want as part of the bond edit the > appropriate > > > file. For example ifcfg-eth0 and ifcfg-eth2 which can also be found > in > > > /etc/sysconfig/network-scripts/ > > > > > > You should edit out the ip address and netmask. Make sure the > bootproto > > > is none, keep the hardware address, add slave=yes and add > master=bond0 > > > > > > DEVICE=eth0 > > > BOOTPROTO=none > > > HWADDR=AA:AA:C4:BE:AA:AA > > > ONBOOT=yes > > > TYPE=Ethernet > > > SLAVE=yes > > > MASTER=bond0 > > > > > > > Hi there > > > > i thought that you were meant to remove the HWADDR= lines from > > ifcfg-eth0 and ifcfg-eth1 as bonding manipulates these values to make > > the necessary arp magic work. > > > > the documentation seems to support this view. > > > > mike > > > > -- > > redhat-list mailing list > > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > > https://www.redhat.com/mailman/listinfo/redhat-list > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > ------------------------------ Message: 10 Date: Mon, 31 Mar 2008 15:10:07 +0100 From: "Gerrard Geldenhuis" Subject: RE: NIC Teaming To: "General Red Hat Linux discussion list" Message-ID: Content-Type: text/plain; charset="us-ascii" > i normally do this in modprobe.conf as something hinky happens on > dells with more than 2 ethernet ports and udev > :-) What lines do you add to modprobe to achieve this? Out of interest... > > > > > Can you point me to the documentation that supports removing hwaddr > > lines... It is also likely that the manipulation of configuration files > > differs from distro to distro... > > > > http://www.linuxquestions.org/linux/answers/Networking/Linux_bonding_how to > _0 > > also from bonding.txt > > All interfaces that are part of the trunk, should have SLAVE and MASTER > definitions. For example, in the case of RedHat, if you wish to make eth0 > and > eth1 (or other interfaces) a part of the bonding interface bond0, their > config > files (ifcfg-eth0, ifcfg-eth1, etc.) should look like this: > > DEVICE=eth0 > USERCTL=no > ONBOOT=yes > MASTER=bond0 > SLAVE=yes > BOOTPROTO=none > > from bond_main.c > Hmmm, that does not specifically say remove the hwaddr line... > > The only reason i think this is that i have had problems with bonding > with RH5.1 where i had the HWADDR values specified. bond0 wouldn't > come up until i removed - indeed the box wouldn't boot - until i > removed those lines from ifcfg-eth0 and 1 > > I could be wrong, i often am Indeed, but so could I. I asked a question about consistent naming for ethernet device on rhel5 mailinglist and one recommendation was to keep the hardware address in the icfg-ethx files. Have a look at the thread in the arcives called "Persistent naming for eth devices" https://www.redhat.com/mailman/listinfo/rhelv5-list Regards > > best wishes > > mike > > > The bonding driver documentation states that you can specify options for > > the bond interface in the ifcfg-bondX file but that has not been the > > case for me. I still have to specify options in the /etc/modprobe.conf > > file. > > > > Regards > > ------------------------------ Message: 11 Date: Mon, 31 Mar 2008 15:30:23 +0100 From: "Michael Simpson" Subject: Re: NIC Teaming To: "General Red Hat Linux discussion list" Message-ID: <82abd3a70803310730l7ca46cbeo271757abd3d2bc09@xxxxxxxxxxxxxx> Content-Type: text/plain; charset=ISO-8859-1 On 3/31/08, Gerrard Geldenhuis wrote: > > i normally do this in modprobe.conf as something hinky happens on > > dells with more than 2 ethernet ports and udev > > :-) > > What lines do you add to modprobe to achieve this? Out of interest... > it was more using alias eth0 tg3 alias eth1 tg3 alias eth2 e1000 alias eth3 e1000 etc to stop the nic cards being jumbled for different bonds using different cards ------------------------------ Message: 12 Date: Mon, 31 Mar 2008 15:38:07 +0100 From: "Gerrard Geldenhuis" Subject: RE: NIC Teaming To: "General Red Hat Linux discussion list" Message-ID: Content-Type: text/plain; charset="us-ascii" I have the same: alias eth0 bnx2 alias eth1 bnx2 === message truncated === --------------------------------- You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
