Re: [CentOS] DNS DoS attack
Am Thu, 16 Aug 2012 22:18:19 -0700 schrieb John R Pierce : > On 08/16/12 9:54 PM, Jussi Hirvi wrote: > >> Aug 17 07:41:38 mx2 named[6873]: client 205.145.64.200#53: query > >> (cache) 'ripe.net/ANY/IN' denied > >> >Aug 17 07:41:38 mx2 named[6873]: client 204.10.45.5#53: query > >> >(cache) 'ripe.net/ANY/IN' denied Aug 17 07:41:38 mx2 named[6873]: > >> >client 78.40.35.212#53: query (cache) 'ripe.net/ANY/IN' denied > >> >Aug 17 07:41:38 mx2 named[6873]: client 207.207.3.126#53: query > >> >(cache) 'ripe.net/ANY/IN' denied > > Are there any ways to mitigate this, or do I just have to wait? > > > meh, if its coming from lots of random hosts, then fail2ban style > techniques won't work. I assume this is an authoritative name > server? does it have recursive queries disabled so it can only return > results for the domain(s) its authoritative for ? It's a common "attack". Just search google. I think, someone mentioned a firewall rule here a couple of weeks ago to block these types of queries. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] vi defaults in 6.x
From: Les Mikesell > When I use copy/paste text into a window running vi, if there is a > single line starting with '#', in the pasted content, it adds a # to > all subsequent lines and indents each an additional level. Is there > some way to eliminate this bizarre behavior, preferably globally and > permanently so I don't have to repeat some change for every > machine/user where I might log in? If you do not want to change the defaults, you could temporarily call vim without the initializations: vim -u NONE ... JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS DoS attack
On 17.8.2012 8.18, John R Pierce wrote: > meh, if its coming from lots of random hosts, then fail2ban style > techniques won't work. I assume this is an authoritative name server? > does it have recursive queries disabled so it can only return results > for the domain(s) its authoritative for ? Yes, it is authoritative. Recursive queries were open very widely. That may be why I started to get plenty of requests. But I think that 240 per second is not normal anymore, it must me malicious. I believe my name server was used as a mediator only, and the real target (through recursive queries) was some other public nameserver. This morning I restricted recursive queries to trusted networks only. The load dropped slowly to 20 % of what it was before. - Jussi ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] default gateway outside of the LAN
Hi Boris, > We have a somewhat unique setup whereby our default router is outside of > the local network. 'unique' is a very mild expression. The word you're actually looking for was probably 'wrong'. Your gateway *must* be in the network your interfaces are in. You also would not want your living room be built without any doors and a sign on the wall 'the exit is in the kitchen'. Best regards, Peter. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS DoS attack
From: Jussi Hirvi > On 17.8.2012 8.18, John R Pierce wrote: >> meh, if its coming from lots of random hosts, then fail2ban style >> techniques won't work. I assume this is an authoritative name server? >> does it have recursive queries disabled so it can only return results >> for the domain(s) its authoritative for ? > > Yes, it is authoritative. Recursive queries were open very widely. That > may be why I started to get plenty of requests. But I think that 240 per > second is not normal anymore, it must me malicious. > > I believe my name server was used as a mediator only, and the real > target (through recursive queries) was some other public nameserver. > > This morning I restricted recursive queries to trusted networks only. > The load dropped slowly to 20 % of what it was before. Maybe it is this: http://arstechnica.com/business/2012/03/how-anonymous-plans-to-use-dns-as-a-weapon/ JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS DoS attack
On 17.8.2012 15.04, John Doe wrote: > Maybe it is this: > http://arstechnica.com/business/2012/03/how-anonymous-plans-to-use-dns-as-a-weapon/ Interesting idea. In that case the ip's in my logs would point to the targets of the attact. I checked a few of them, and they look more like hijacked victims, or ns query mediators like me. I don't see a common factor. ...icon.com (Ricoh, Japanese office machines) ...unum.com (employee insurances, I think) sexy-lingerie.uk.com mnet04-40.austin.datafoundry.com ...netmagicians.com ns1.p10.dynect.net www.macsales.com 66-226-73-103.dedicated.codero.net ns.rackspace.com ns1.clt.peak-10.com (their webpage: "We're rock solid"!) - Jussi ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNS DoS attack
Jussi Hirvi wrote: > On 17.8.2012 15.04, John Doe wrote: >> Maybe it is this: >> http://arstechnica.com/business/2012/03/how-anonymous-plans-to-use-dns-as-a-weapon/ > > Interesting idea. In that case the ip's in my logs would point to the > targets of the attact. I checked a few of them, and they look more like > hijacked victims, or ns query mediators like me. I don't see a common > factor. Thanks to John Doe for the link - very interesting read. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] default gateway outside of the LAN
> 'unique' is a very mild expression. The word you're actually looking for was > probably 'wrong'. > > Your gateway *must* be in the network your interfaces are in. You also would > not want your living room be built without any doors and a sign on the wall > 'the exit is in the kitchen'. There does exist one use case that was pointed out on IRC that might be valid ... although the OP is somewhat abstract in his original definition so this might not apply... In the event an ISP provides new IPs and routes them to your host but these are outside of the pre-existing subnet it is possible to use them with no gateway in the subnet associated with these (it's essentially a point to point link directing traffic at an interface)... This somewhat describes the situation: http://www.adminsehow.com/2011/09/gateway-on-a-different-subnet-on-linux/ However it is a rather specific use case and may not apply here... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] vi defaults in 6.x
On Fri, Aug 17, 2012 at 5:22 AM, John Doe wrote: > From: Les Mikesell > >> When I use copy/paste text into a window running vi, if there is a >> single line starting with '#', in the pasted content, it adds a # to >> all subsequent lines and indents each an additional level. Is there >> some way to eliminate this bizarre behavior, preferably globally and >> permanently so I don't have to repeat some change for every >> machine/user where I might log in? > > If you do not want to change the defaults, you could temporarily call vim > without the initializations: > vim -u NONE ... That's the effect I want, since I log into a lot of different machines and paste stuff into scripts. But, it doesn't seem to work. With 'vim -u NONE /tmp/test.pl' it still does the auto-comment stuff. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Intel D425KT Motherboard / Realtek RTL8105E
Greetings- I'm attempting to get CentOS 5.5 x86 (yes, very specific version required for specific software usage scenario... don't ask) running on an Intel D425KT mini-ITX motherboard. Everything works fine, with the exception of the onboard ethernet, which is a Realtek RTL8105E chip. The stock CentOS installation attempts to use the r8169 driver, which does not work. I've been around the block a few times dealing with Realtek interfaces and their driver hell, but this one is stumping me. Things tried so far: -Adding pci=assign-busses to the kernel parameters -Installing kmod-r8101 from elrepo, old and new versions -Compiling driver from scratch direct from Realtek In every test, I end up with what *appears* to be a functioning ethernet interface (r8101 driver detects chip as RTL8105E correctly), or as reported by the software (ifconfig, ethtool, etc). But, I just cannot get any traffic to pass. There is a link light for the ethernet interface, but no actual activity when testing. Any thoughts? --Tim ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] vi defaults in 6.x
From: Les Mikesell > On Fri, Aug 17, 2012 at 5:22 AM, John Doe wrote: >> From: Les Mikesell >> >>> When I use copy/paste text into a window running vi, if there is a >>> single line starting with '#', in the pasted content, it adds a > # to >>> all subsequent lines and indents each an additional level. Is there >>> some way to eliminate this bizarre behavior, preferably globally and >>> permanently so I don't have to repeat some change for every >>> machine/user where I might log in? >> >> If you do not want to change the defaults, you could temporarily call vim >> without the initializations: >> vim -u NONE ... > > That's the effect I want, since I log into a lot of different machines > and paste stuff into scripts. But, it doesn't seem to work. With > 'vim -u NONE /tmp/test.pl' it still does the auto-comment stuff. Works for me at least to avoid "crazy" double auto-indent... And it turns off syntax highlighting too. But I have no auto-comment in either modes... JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] vi defaults in 6.x
On Fri, Aug 17, 2012 at 10:35 AM, John Doe wrote: >>> When I use copy/paste text into a window running vi, if there is a single line starting with '#', in the pasted content, it adds a >> # to all subsequent lines and indents each an additional level. Is there some way to eliminate this bizarre behavior, preferably globally and permanently so I don't have to repeat some change for every machine/user where I might log in? >>> >>> If you do not want to change the defaults, you could temporarily call vim >>> without the initializations: >>>vim -u NONE ... >> >> That's the effect I want, since I log into a lot of different machines >> and paste stuff into scripts. But, it doesn't seem to work. With >> 'vim -u NONE /tmp/test.pl' it still does the auto-comment stuff. > > Works for me at least to avoid "crazy" double auto-indent... > And it turns off syntax highlighting too. > But I have no auto-comment in either modes... That's interesting - I don't think I've ever changed any defaults. I'm using the text mode version in a gnome-terminal window in case that makes a difference. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E
On Fri, 17 Aug 2012, Tim Nelson wrote: > To: CentOS mailing list > From: Tim Nelson > Subject: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E > > Greetings- > > I'm attempting to get CentOS 5.5 x86 (yes, very specific version required for > specific software usage scenario... don't ask) running on an Intel D425KT > mini-ITX motherboard. Everything works fine, with the exception of the > onboard ethernet, which is a Realtek RTL8105E chip. The stock CentOS > installation attempts to use the r8169 driver, which does not work. I've been > around the block a few times dealing with Realtek interfaces and their driver > hell, but this one is stumping me. > > Things tried so far: > > -Adding pci=assign-busses to the kernel parameters > -Installing kmod-r8101 from elrepo, old and new versions > -Compiling driver from scratch direct from Realtek > > In every test, I end up with what *appears* to be a functioning ethernet > interface (r8101 driver detects chip as RTL8105E correctly), or as reported > by the software (ifconfig, ethtool, etc). But, I just cannot get any traffic > to pass. There is a link light for the ethernet interface, but no actual > activity when testing. > > Any thoughts? Hi Tim. If this NIC is built onto the motherboard, would it not be easier just to find an (PCI?) expansion slot NIC that is known to work out of the box on Centos 5.5 and use that instead? HTH Keith --- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] --- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E
> On Fri, 17 Aug 2012, Tim Nelson wrote: > >> To: CentOS mailing list >> From: Tim Nelson >> Subject: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E >> >> Greetings- >> >> I'm attempting to get CentOS 5.5 x86 (yes, very specific version required >> for specific software usage scenario... don't ask) running on an Intel >> D425KT mini-ITX motherboard. Everything works fine, with the exception of >> the onboard ethernet, which is a Realtek RTL8105E chip. The stock CentOS >> installation attempts to use the r8169 driver, which does not work. I've >> been around the block a few times dealing with Realtek interfaces and their >> driver hell, but this one is stumping me. >> >> Things tried so far: >> >> -Adding pci=assign-busses to the kernel parameters >> -Installing kmod-r8101 from elrepo, old and new versions >> -Compiling driver from scratch direct from Realtek >> >> In every test, I end up with what *appears* to be a functioning ethernet >> interface (r8101 driver detects chip as RTL8105E correctly), or as reported >> by the software (ifconfig, ethtool, etc). But, I just cannot get any traffic >> to pass. There is a link light for the ethernet interface, but no actual >> activity when testing. >> >> Any thoughts? > > Hi Tim. > > If this NIC is built onto the motherboard, would it not be > easier just to find an (PCI?) expansion slot NIC that is > known to work out of the box on Centos 5.5 and use that > instead? Or the other option could be to use a USB to RJ45 adaptor instead of the onboard NIC? http://www.amazon.co.uk/USB-LAN01-Usb-lan-RJ45/dp/B000CCZP88/ref=sr_1_3?ie=UTF8&qid=1345222425&sr=8-3 Keith --- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] --- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E
On Fri, 17 Aug 2012, Keith Roberts wrote: *snip* > Or the other option could be to use a USB to RJ45 adaptor instead of the > onboard NIC? > > http://www.amazon.co.uk/USB-LAN01-Usb-lan-RJ45/dp/B000CCZP88/ref=sr_1_3?ie=UTF8&qid=1345222425&sr=8-3 Here's an interesting article about using Ethernet over USB: "The ability to connect Ethernet devices via USB ports is known as Ethernet over USB. There are many low-cost commercial adapters available to do this. The links below describe the technical details on how the technology works." http://en.wikipedia.org/wiki/Ethernet_over_USB HTH Keith --- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] --- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E
- Original Message - > If this NIC is built onto the motherboard, would it not be > easier just to find an (PCI?) expansion slot NIC that is > known to work out of the box on Centos 5.5 and use that > instead? > Yes, that is what I'm doing for testing and working on the system, but given the board is mini-ITZ with a single PCI slot which will be filled later with a different card, this isn't much of a solution. :) --Tim ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E
- Original Message - > > Or the other option could be to use a USB to RJ45 adaptor > instead of the onboard NIC? > Gross. Have you used any USB<->Ethernet adapters lately? I have, and they are horrible. --Tim ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E
Tim Nelson wrote: > Greetings- > > I'm attempting to get CentOS 5.5 x86 (yes, very specific version required > for specific software usage scenario... don't ask) running on an Intel > D425KT mini-ITX motherboard. Everything works fine, with the exception of > the onboard ethernet, which is a Realtek RTL8105E chip. The stock CentOS > installation attempts to use the r8169 driver, which does not work. I've > been around the block a few times dealing with Realtek interfaces and > their driver hell, but this one is stumping me. I've got a baaad feeling about this. Have you considered returning the m/b for a replacement? mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E
- Original Message - > Tim Nelson wrote: > > Greetings- > > > > I'm attempting to get CentOS 5.5 x86 (yes, very specific version > > required > > for specific software usage scenario... don't ask) running on an > > Intel > > D425KT mini-ITX motherboard. Everything works fine, with the > > exception of > > the onboard ethernet, which is a Realtek RTL8105E chip. The stock > > CentOS > > installation attempts to use the r8169 driver, which does not work. > > I've > > been around the block a few times dealing with Realtek interfaces > > and > > their driver hell, but this one is stumping me. > > I've got a baaad feeling about this. Have you considered returning > the m/b > for a replacement? > Yes, it crossed my mind, but the fact is I have 4 of these boards, all with the same symptoms. :( --Tim ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] tigervnc-server-module crashes after EL 6.3 update
On Thu, 2012-08-16 at 17:01 -0500, Johnny Hughes wrote: > On 08/16/2012 11:43 AM, Cal Webster wrote: > > On Wed, 2012-08-15 at 13:56 -0500, Johnny Hughes wrote: > >> On 08/15/2012 09:47 AM, Cal Webster wrote: > >>> On Tue, 2012-08-14 at 20:55 -0500, Johnny Hughes wrote: > On 08/14/2012 05:23 PM, Cal Webster wrote: > > We began experiencing failed vnc connections to the console display on > > servers that have been updated to EL 6.3. No such failures have occurred > > on similar connections to EL 6.2 servers. > > > > On the client machine a normal vncviewer display appears with the > > expected graphical login until the mouse pointer is moved within the > > boundaries of the vncviewer window. At this point the window closes and > > an error message appears in both a pop-up window and in the terminal > > window in which the session was initiated stating "read: Connection > > reset by peer (104)". > > > > On the server end, a core dump is generated and a abrt bug report is > > created. > > > > /var/log/messages > > -- > > Aug 14 11:00:30 jato2 abrt[11411]: File '/usr/bin/Xorg' seems to be > > deleted > > Aug 14 11:00:30 jato2 abrt[11411]: Saved core dump of pid 7892 > > (/usr/bin/Xorg) to /var/spool/abrt/ccpp-2012-08-14-11:00:30-7892 > > (42041344 bytes) > > Aug 14 11:00:30 jato2 abrtd: Directory 'ccpp-2012-08-14-11:00:30-7892' > > creation detected > > -- > > > > This bug has been reported in the CentOS bug tracker here: > > > > 0005824: tigervnc-server-module keep crashing > > http://bugs.centos.org/view.php?id=5824 > > > > However, this appears to be a bug upstream. The source RPM provided with > > CentOS is identical to that of upstream with no modifications. Also, > > there is an upstream bug reported that appears to have the same > > symptoms. I have added a comment to the upstream bug report (listed > > below) if anyone wishes to see the details. > > > > tigervnc-server-module crashes with dual screen setup > > https://bugzilla.redhat.com/show_bug.cgi?id=820443 > > > > > > > > We have verified that rebuilding the unmodified source RPM for tigervnc > > produces a tigervnc-server-module RPM that does not suffer from this > > bug. > > > > Removing the original tigervnc-server-module package and replacing it > > with the rebuilt one fixes the problem. > > > > I've duplicated the problem on 2 EL 6.3 x86_64 single-head display > > machines and have verified the fix. > > > > Tomorrow, I'll duplicate the problem on a dual-head x86_64 machine that > > currently still works after updating to EL 6.2 then confirm the the fix. > > > Did you rebuild the SRPM using mock or directly on a physical machine > with rpmbuild? > >>> No mock, just a simple "rpmbuild -ba SPEC/tigervnc.spec" > >> OK, if you find that this solves your problems for sure, I will build > >> the SRPM outside of mock and see if it is different. > > I've confirmed the same faulty behavior for the update to 6.3 on our > > dual-head systems. > > > > Also confirmed is that replacing the 6.3 base tigervnc-server-module rpm > > with the rebuilt one does fix the problem on the dual-head systems. > > > > One disturbing difference between single and dual headed systems is that > > on the dual-head systems Xorg generates a core dump and completely > > freezes up when the mouse movement is detected. Single-head systems just > > fail to connect. This complication could be somehow caused by our > > proprietary "ATI FirePro 2270" drivers, though. Once the rebuilt module > > is installed the systems run fine. > > > > I've also updated the upstream bug report. > > can you see if either or both of these work for you: > > http://people.centos.org/hughesjr/tigervnc/ > > One set was built inside of mock, the other outside of mock in a virtual > machine with only the build requirements of the SRPM installed. Both builds work without problems on single and dual-head systems here. As with all the other tests, I only replaced the tigervnc-server-module package on each host. I've also confirmed that i686 platforms suffer from the same bug. These too, however, are easily remedied by replacing the base tigervnc-server-module RPM with a locally re-build one. ./Cal ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Wiki dead links CentOS-Fasttrack
Hello, The links under the CentOS-Fasttrack paragraph at http://wiki.centos.org/AdditionalResources/Repositories all refer to non existent pages/files at mirror.centos.org. Where can one find the repo files and readme? Regards, Leonard. -- mount -t life -o ro /dev/dna /genetic/research ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E
On Fri, 17 Aug 2012, Tim Nelson wrote: > To: CentOS mailing list > From: Tim Nelson > Subject: Re: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E > > - Original Message - >> >> Or the other option could be to use a USB to RJ45 adaptor >> instead of the onboard NIC? >> > > Gross. Have you used any USB<->Ethernet adapters lately? I > have, and they are horrible. Hi Tim. Nope not had any need to yet. Why are they gross then? Keith --- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] --- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E
- Original Message - > On Fri, 17 Aug 2012, Tim Nelson wrote: > > > To: CentOS mailing list > > From: Tim Nelson > > Subject: Re: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E > > > > - Original Message - > >> > >> Or the other option could be to use a USB to RJ45 adaptor > >> instead of the onboard NIC? > >> > > > > Gross. Have you used any USB<->Ethernet adapters lately? I > > have, and they are horrible. > > Hi Tim. > > Nope not had any need to yet. > > Why are they gross then? > "Gross", as in: -High latency -Poor throughput -Random link connects/disconnects -Random traffic slowdowns In general, they fit the bill for 'ease of installation', but miss the mark on everything else a NIC should be. Maybe I got a bad batch, but I've tried 4 or 5 different models, all the same results. --Tim ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Monitor speed between client and server, netperf?
Hi, Want to know what is the best tools to monitor network connection speed between client PC and my server. As I need to know if the network latency. I know use zabbix to monitor CPU/member and others of server. However, 1. For the connection speed monitor is there any tools can do this? 2. I tried netperf, it's good. I have to write a cron job in my client PC to report the speed? is this a correct way to do? 3. If use netperf and cron job do connection speed test every 5 mins, is that impact my server network throughput as I guess it is sending really data between server and client. Could you help to point me a right way to move on, thank you very much. Best Regards, Su Heng ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E
On Fri, 17 Aug 2012, Tim Nelson wrote: *snip* > "Gross", as in: > > -High latency > -Poor throughput > -Random link connects/disconnects > -Random traffic slowdowns > > In general, they fit the bill for 'ease of installation', > but miss the mark on everything else a NIC should be. > > Maybe I got a bad batch, but I've tried 4 or 5 different > models, all the same results. As a test case, have you tried booting from a recent Live CD version of Linux, like Parted Magic: http://partedmagic.com/doku.php?id=screenshots It's also included on the UBCD: http://www.ultimatebootcd.com/index.html If you can get this onboard NIC working OK from Parted Magic, then at least you know it's not the NIC hardware. You might find the hardware identification routines in the Parted Magic distro can give you some helpful pointers too. HTH Keith --- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] --- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E
Hey, Keith, I may have missed your answer to this - have you tried tcpdump while trying to send, once it looks good? Does ethtool ever think there's a link? mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel D425KT Motherboard / Realtek RTL8105E
- Original Message - > Hey, Keith, > >I may have missed your answer to this - have you tried tcpdump >while > trying to send, once it looks good? Does ethtool ever think there's a > link? > I'm the OP, and no I haven't done a capture yet. Not a bad idea, thanks! Ethtool does indeed report a link, and it shows the proper modes for the interface (10mbit full/half duplex and 100mbit full/half duplex). --Tim ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] KVM Setup for Win7 Pro on CentOS 5.x
On Thu, Aug 16, 2012, Theo Band wrote: >On 08/16/2012 06:36 PM, Bill Campbell wrote: ... >> + Set up network bridging on the private LAN so that the Windows system >> is accessible via OpenVPN connections from the outside world and by >> users on the LAN to run a client/server accounting application. >>> I have done KVM VLANs but I am not sure if it can be done from the >>> virt-manager. Experiment and see how far you can go. >> I will be digging into this later today. So far I've found the >> file /var/lib/libvirt/network/default.xml and see a vibr0 >> interface defined. >> >> The documentation I found yesterday described setting up briding, >> but hopefully virt-manager has a nicer way to do it. >This I find the most difficult part. I have done it a couple of time and >made myself a HOWTO. You need to fill in some IP figures of course. I >assume a fixed IP address, but DHCP should work as well. The setup >creates a bridge and adds and existing interface (ifcfg-ethx) to that >bridge. After that you can use the bridge for the VMs: I got things installed yesterday, adding a routed network section using virt-manager linked to the private interface, eth1. I left the default NAT interface as-is. After rebooting the machine, two bridge devices, virbr0 and virbr1 appear in 'ifconfig' output with the appropriate IP addresses (192.168.122.1 and 192.168.100.1 respectively). The 'route -n' command shows reasonable routes for the VMs. I am thoroughly confused by the documentation I've found so far, much of which seems to be out of date. When the Windows VM is active with the network virbr1 defined with virt-manager and all other things default, a 'vmnet0' device appears in 'ifconfig' output. I can ping the IPs on the private lan (192.168.101.0/24 in this case), but cannot get to the outside world, nor can hosts on the LAN ping the VM's assigned IP address 192.168.100.114. If I shut down the VM, manually run 'brctl addif virbr1 eth1', then start the VM things change: + The IP address assigned to the VM is in the 192.168.101.0/24 block instead of 192.168.100.0/24 defined in virt-manager. + I can ping the outside world from the VM. + I can ping other hosts in 192.168.101.0/24, but *NOT* the Linux boxes IP address. + I cannot ping anything in 192.168.101.0/24 from the command line on the Linux host (logged in with ssh on the public interface). + The command 'brctl show' displays vmnet0 and eth1 vir virbr1. I'm more than a bit confused at this point. My main goal is to get LAN and OpenVPN access to the Windows VM. I really don't care about Internet access from the Windows VM, although Microsoft really wants it to get updates and such. >KVM >=== >yum install kvm virt-manager qemu bridge-utils >#create bridge for virt-machine >cat > /etc/sysconfig/network-scripts/ifcfg-br0 << _END_ >DEVICE=br0 >TYPE=Bridge >IPADDR=192.168.48.X >NETMASK=255.255.255.0 >GATEWAY=192.168.48.1 >BOOTPROTO=none >ONBOOT=yes >DELAY=0 >NOZEROCONF=true >NM_CONTROLLED=no >_END_ > >Edit /etc/sysconfig/network-scripts/ifcfg-ethx : >ONBOOT=yes >BRIDGE=br0 >NM_CONTROLLED=no > >service network restart >___ >CentOS mailing list >CentOS@centos.org >http://lists.centos.org/mailman/listinfo/centos > -- Bill -- INTERNET: b...@celestial.com Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way Voice: (206) 236-1676 Mercer Island, WA 98040-0820 Fax:(206) 232-9186 Skype: jwccsllc (206) 855-5792 Lord, the money we do spend on Government and it's not one bit better than the government we got for one third the money twenty years ago. Will Rogers ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] tigervnc-server-module crashes after EL 6.3 update
On 08/17/2012 01:40 PM, Cal Webster wrote: > On Thu, 2012-08-16 at 17:01 -0500, Johnny Hughes wrote: >> On 08/16/2012 11:43 AM, Cal Webster wrote: >>> On Wed, 2012-08-15 at 13:56 -0500, Johnny Hughes wrote: On 08/15/2012 09:47 AM, Cal Webster wrote: > On Tue, 2012-08-14 at 20:55 -0500, Johnny Hughes wrote: >> On 08/14/2012 05:23 PM, Cal Webster wrote: >>> We began experiencing failed vnc connections to the console display on >>> servers that have been updated to EL 6.3. No such failures have occurred >>> on similar connections to EL 6.2 servers. >>> >>> On the client machine a normal vncviewer display appears with the >>> expected graphical login until the mouse pointer is moved within the >>> boundaries of the vncviewer window. At this point the window closes and >>> an error message appears in both a pop-up window and in the terminal >>> window in which the session was initiated stating "read: Connection >>> reset by peer (104)". >>> >>> On the server end, a core dump is generated and a abrt bug report is >>> created. >>> >>> /var/log/messages >>> -- >>> Aug 14 11:00:30 jato2 abrt[11411]: File '/usr/bin/Xorg' seems to be >>> deleted >>> Aug 14 11:00:30 jato2 abrt[11411]: Saved core dump of pid 7892 >>> (/usr/bin/Xorg) to /var/spool/abrt/ccpp-2012-08-14-11:00:30-7892 >>> (42041344 bytes) >>> Aug 14 11:00:30 jato2 abrtd: Directory 'ccpp-2012-08-14-11:00:30-7892' >>> creation detected >>> -- >>> >>> This bug has been reported in the CentOS bug tracker here: >>> >>> 0005824: tigervnc-server-module keep crashing >>> http://bugs.centos.org/view.php?id=5824 >>> >>> However, this appears to be a bug upstream. The source RPM provided with >>> CentOS is identical to that of upstream with no modifications. Also, >>> there is an upstream bug reported that appears to have the same >>> symptoms. I have added a comment to the upstream bug report (listed >>> below) if anyone wishes to see the details. >>> >>> tigervnc-server-module crashes with dual screen setup >>> https://bugzilla.redhat.com/show_bug.cgi?id=820443 >>> >>> >>> >>> We have verified that rebuilding the unmodified source RPM for tigervnc >>> produces a tigervnc-server-module RPM that does not suffer from this >>> bug. >>> >>> Removing the original tigervnc-server-module package and replacing it >>> with the rebuilt one fixes the problem. >>> >>> I've duplicated the problem on 2 EL 6.3 x86_64 single-head display >>> machines and have verified the fix. >>> >>> Tomorrow, I'll duplicate the problem on a dual-head x86_64 machine that >>> currently still works after updating to EL 6.2 then confirm the the fix. >>> >> Did you rebuild the SRPM using mock or directly on a physical machine >> with rpmbuild? > No mock, just a simple "rpmbuild -ba SPEC/tigervnc.spec" OK, if you find that this solves your problems for sure, I will build the SRPM outside of mock and see if it is different. >>> I've confirmed the same faulty behavior for the update to 6.3 on our >>> dual-head systems. >>> >>> Also confirmed is that replacing the 6.3 base tigervnc-server-module rpm >>> with the rebuilt one does fix the problem on the dual-head systems. >>> >>> One disturbing difference between single and dual headed systems is that >>> on the dual-head systems Xorg generates a core dump and completely >>> freezes up when the mouse movement is detected. Single-head systems just >>> fail to connect. This complication could be somehow caused by our >>> proprietary "ATI FirePro 2270" drivers, though. Once the rebuilt module >>> is installed the systems run fine. >>> >>> I've also updated the upstream bug report. >> can you see if either or both of these work for you: >> >> http://people.centos.org/hughesjr/tigervnc/ >> >> One set was built inside of mock, the other outside of mock in a virtual >> machine with only the build requirements of the SRPM installed. > Both builds work without problems on single and dual-head systems here. > As with all the other tests, I only replaced the tigervnc-server-module > package on each host. > > I've also confirmed that i686 platforms suffer from the same bug. These > too, however, are easily remedied by replacing the base > tigervnc-server-module RPM with a locally re-build one. > > ./Cal Thanks for testing. I will build a new version for release with an incremented version and get you to test those before for release if you would do so for me. Thanks, Johnny Hughes signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] vi defaults in 6.x
On Fri, 2012-08-17 at 11:02 -0500, Les Mikesell wrote: > On Fri, Aug 17, 2012 at 10:35 AM, John Doe wrote: > >>> > When I use copy/paste text into a window running vi, if there is a > single line starting with '#', in the pasted content, it adds a > >> # to > all subsequent lines and indents each an additional level. Is there > some way to eliminate this bizarre behavior, preferably globally and > permanently so I don't have to repeat some change for every > machine/user where I might log in? > >>> > >>> If you do not want to change the defaults, you could temporarily call vim > >>> without the initializations: > >>>vim -u NONE ... > >> > >> That's the effect I want, since I log into a lot of different machines > >> and paste stuff into scripts. But, it doesn't seem to work. With > >> 'vim -u NONE /tmp/test.pl' it still does the auto-comment stuff. > > > > Works for me at least to avoid "crazy" double auto-indent... > > And it turns off syntax highlighting too. > > But I have no auto-comment in either modes... > > That's interesting - I don't think I've ever changed any defaults. > I'm using the text mode version in a gnome-terminal window in case > that makes a difference. Of course, if you don't care for vim, you can always use the old, simple version by using the command "/bin/vi" instead of "vim" and that should do away with most of the enhancements. > -- Ron Loftin relof...@twcny.rr.com "God, root, what is difference ?" Piter from UserFriendly ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] tigervnc-server-module crashes after EL 6.3 update
On 08/17/2012 01:40 PM, Cal Webster wrote: > On Thu, 2012-08-16 at 17:01 -0500, Johnny Hughes wrote: >> On 08/16/2012 11:43 AM, Cal Webster wrote: >>> On Wed, 2012-08-15 at 13:56 -0500, Johnny Hughes wrote: On 08/15/2012 09:47 AM, Cal Webster wrote: > On Tue, 2012-08-14 at 20:55 -0500, Johnny Hughes wrote: >> On 08/14/2012 05:23 PM, Cal Webster wrote: >>> We began experiencing failed vnc connections to the console display on >>> servers that have been updated to EL 6.3. No such failures have occurred >>> on similar connections to EL 6.2 servers. >>> >>> On the client machine a normal vncviewer display appears with the >>> expected graphical login until the mouse pointer is moved within the >>> boundaries of the vncviewer window. At this point the window closes and >>> an error message appears in both a pop-up window and in the terminal >>> window in which the session was initiated stating "read: Connection >>> reset by peer (104)". >>> >>> On the server end, a core dump is generated and a abrt bug report is >>> created. >>> >>> /var/log/messages >>> -- >>> Aug 14 11:00:30 jato2 abrt[11411]: File '/usr/bin/Xorg' seems to be >>> deleted >>> Aug 14 11:00:30 jato2 abrt[11411]: Saved core dump of pid 7892 >>> (/usr/bin/Xorg) to /var/spool/abrt/ccpp-2012-08-14-11:00:30-7892 >>> (42041344 bytes) >>> Aug 14 11:00:30 jato2 abrtd: Directory 'ccpp-2012-08-14-11:00:30-7892' >>> creation detected >>> -- >>> >>> This bug has been reported in the CentOS bug tracker here: >>> >>> 0005824: tigervnc-server-module keep crashing >>> http://bugs.centos.org/view.php?id=5824 >>> >>> However, this appears to be a bug upstream. The source RPM provided with >>> CentOS is identical to that of upstream with no modifications. Also, >>> there is an upstream bug reported that appears to have the same >>> symptoms. I have added a comment to the upstream bug report (listed >>> below) if anyone wishes to see the details. >>> >>> tigervnc-server-module crashes with dual screen setup >>> https://bugzilla.redhat.com/show_bug.cgi?id=820443 >>> >>> >>> >>> We have verified that rebuilding the unmodified source RPM for tigervnc >>> produces a tigervnc-server-module RPM that does not suffer from this >>> bug. >>> >>> Removing the original tigervnc-server-module package and replacing it >>> with the rebuilt one fixes the problem. >>> >>> I've duplicated the problem on 2 EL 6.3 x86_64 single-head display >>> machines and have verified the fix. >>> >>> Tomorrow, I'll duplicate the problem on a dual-head x86_64 machine that >>> currently still works after updating to EL 6.2 then confirm the the fix. >>> >> Did you rebuild the SRPM using mock or directly on a physical machine >> with rpmbuild? > No mock, just a simple "rpmbuild -ba SPEC/tigervnc.spec" OK, if you find that this solves your problems for sure, I will build the SRPM outside of mock and see if it is different. >>> I've confirmed the same faulty behavior for the update to 6.3 on our >>> dual-head systems. >>> >>> Also confirmed is that replacing the 6.3 base tigervnc-server-module rpm >>> with the rebuilt one does fix the problem on the dual-head systems. >>> >>> One disturbing difference between single and dual headed systems is that >>> on the dual-head systems Xorg generates a core dump and completely >>> freezes up when the mouse movement is detected. Single-head systems just >>> fail to connect. This complication could be somehow caused by our >>> proprietary "ATI FirePro 2270" drivers, though. Once the rebuilt module >>> is installed the systems run fine. >>> >>> I've also updated the upstream bug report. >> can you see if either or both of these work for you: >> >> http://people.centos.org/hughesjr/tigervnc/ >> >> One set was built inside of mock, the other outside of mock in a virtual >> machine with only the build requirements of the SRPM installed. > Both builds work without problems on single and dual-head systems here. > As with all the other tests, I only replaced the tigervnc-server-module > package on each host. > > I've also confirmed that i686 platforms suffer from the same bug. These > too, however, are easily remedied by replacing the base > tigervnc-server-module RPM with a locally re-build one. Would you also test that these work: http://people.centos.org/hughesjr/tigervnc/ (same link, newer files :D) NOTE: It is CentOS policy that we do not correct upstream bugs in our distributions directly ... therefore these will not be released into the main distro until upstream releases an update. I know that is a PITA for people, however, it is our policy and we can't break it. signature.asc Description: OpenPGP digital signature ___
Re: [CentOS] Monitor speed between client and server, netperf?
Try with smokeping if you want to know latency. 2012/8/17, suheng : > Hi, > > Want to know what is the best tools to monitor network connection > speed between client PC and my server. As I need to know if the network > latency. > I know use zabbix to monitor CPU/member and others of server. However, > 1. For the connection speed monitor is there any tools can do this? > 2. I tried netperf, it's good. I have to write a cron job in my > client PC to report the speed? is this a correct way to do? > 3. If use netperf and cron job do connection speed test every 5 > mins, is that impact my server network throughput as I guess it is > sending really data between server and client. > Could you help to point me a right way to move on, thank you very much. > > Best Regards, > Su Heng > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > -- Enviado desde mi dispositivo móvil Diego - Yo no soy paranoico! (pero que me siguen, me siguen) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] OT: what are all these probes from my firewall log????
fred smith wrote: > On Thu, Aug 16, 2012 at 09:20:52PM -0700, John R Pierce wrote: >> this is on your eth0 side, I'm assuming thats the WAN side of your >> firewall/gateway ?if so, then yes, I imagine its something at your >> ISP, you might ask them what these are. > > Yup, that's the WAN side of the router. I'll go yell at them, probably > tomorrow. I wouldn't bother. Depending on the demarc equipment used by your ISP and how they have their network configured, you can wind up seeing this kind of crap and there's bugger-all that you can do about it For example, with a cable modem, your assigned upstream segment might be network-A, but other people in your neighborhood might be on network-B, both serviced by the same RF carrier. You shouldn't see unicast traffic for your neighbors, but you could very well see broadcast (and dhcp is the most likely culprit). I know of a particular case where the ISP will assign statics out of one pool, dynamic IPs out of the other pool, a single modem will service machines out of both pools, and therefore you also see broadcast out of both pools. This isn't specific to cable. With both cable and DSL providers I've seen both the only-see-your-own-traffic situation and the see-your-neighbors-broadcast situation. It all depends on the equipment and the configuration. And when I mean configuration, I'm talking about for everyone in your node, if not for your whole city. So it's unlikely that your ISP will change it just for you. But if you still want to call them, fill your boots ... Devin -- He is a prime candidate for natural deselection. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] OT: what are all these probes from my firewall log????
On Fri, Aug 17, 2012 at 09:18:01PM -0600, Devin Reade wrote: > fred smith wrote: > > On Thu, Aug 16, 2012 at 09:20:52PM -0700, John R Pierce wrote: > > >> this is on your eth0 side, I'm assuming thats the WAN side of your > >> firewall/gateway ?if so, then yes, I imagine its something at your > >> ISP, you might ask them what these are. > > > > Yup, that's the WAN side of the router. I'll go yell at them, probably > > tomorrow. > > I wouldn't bother. thanks for the info. I didn't really expect to get any swift action, I kinda figured "it is what it is, like it or lump it" would be their response. but I still might drop them an email with some log excerpts just to see how they respond. I'm retired, I have plenty of time! :) > > Depending on the demarc equipment used by your ISP and how they have > their network configured, you can wind up seeing this kind of crap > and there's bugger-all that you can do about it > > For example, with a cable modem, your assigned upstream segment > might be network-A, but other people in your neighborhood might be > on network-B, both serviced by the same RF carrier. You shouldn't > see unicast traffic for your neighbors, but you could very well see > broadcast (and dhcp is the most likely culprit). I know of a > particular case where the ISP will assign statics out of one pool, > dynamic IPs out of the other pool, a single modem will service > machines out of both pools, and therefore you also see broadcast > out of both pools. > > This isn't specific to cable. With both cable and DSL providers > I've seen both the only-see-your-own-traffic situation and the > see-your-neighbors-broadcast situation. It all depends on the > equipment and the configuration. And when I mean configuration, > I'm talking about for everyone in your node, if not for your > whole city. So it's unlikely that your ISP will change it just > for you. > > But if you still want to call them, fill your boots ... > > Devin > -- > He is a prime candidate for natural deselection. > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos -- Fred Smith -- fre...@fcshome.stoneham.ma.us - "For him who is able to keep you from falling and to present you before his glorious presence without fault and with great joy--to the only God our Savior be glory, majesty, power and authority, through Jesus Christ our Lord, before all ages, now and forevermore! Amen." - Jude 1:24,25 (niv) - ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
