01:10.03 | plarsen | howdy howdy |
01:11.25 | plarsen | ohh, just me and the stickster again ... |
01:11.46 | plarsen | stickster: do you follow novalug? |
01:12.03 | stickster | I pick and choose threads; some I read, some I don't |
01:13.02 | plarsen | did you check out the dailycutoftech link ? |
01:13.49 | plarsen | http://www.dailycupoftech.com/2007/06/19/how-photos-should-be-viewed/ |
01:13.54 | plarsen | That is WAY too impressive!!!! |
01:22.53 | stickster | Yeah, I remember hearing about that project last year when I was in Seattle |
01:23.09 | stickster | MS Research does, and buys, a lot of interesting things |
01:29.04 | plarsen | yup - they invest - but doesn't innovate ;) |
01:30.14 | plarsen | do you know if iptables has somekind of "debug" option - or do I need to ethereal everything up and look over 1-2 hours of traffic to see why things aren't working? |
01:30.21 | plarsen | I've got some wierd rejections |
01:30.42 | plarsen | They're not considered part of an eixsting connection, but they should have been (it's the return/answer message being rejected) |
01:31.57 | plarsen | rejected IN=eth1 OUT= MAC=00:18:8b:3c:0c:c1:00:15:f2:39:8d:b2:08:00 SRC=209.132.177.100 DST=10.1.1.15 LEN=52 TOS=0x00 PREC=0x00 TTL=46 ID=36007 DF PROTO=TCP SPT=443 DPT=2533 WINDOW=3129 RES=0x00 ACK URGP=0 |
01:32.44 | plarsen | that is a return message from rhn ... not sure what "df", "res" and "urgp" is about; but it's a simply response to an outgoing message |
01:36.55 | *** join/#fredlug jsmith (n=jsmith@72-255-77-7.client.stsn.net) |
01:39.51 | plarsen | ahhh, the 3rd musketeer joins the gang! |
01:40.32 | plarsen | hey, who cares if you end up with the ladies :) |
01:40.48 | jsmith | I guess I do :-) |
01:43.21 | plarsen | jsmith: got any ideas of iptables "debug" tools? |
01:43.42 | plarsen | I've got an intermiddent problem here ... that comes every 30-60 minutes and rejects ONE package that shouldn't be rejected. |
01:43.51 | jsmith | You mean, besides tcpdump? |
01:44.25 | jsmith | To be honest, I've been spoiled in my short little career, and had hardware firewalls that cost more than my house. |
01:44.38 | plarsen | hehe |
01:44.39 | jsmith | As such, I'm not a big fan of iptables |
01:44.51 | jsmith | I really ought to do more with it... but I'm lazy |
01:44.52 | plarsen | I have that, but I still lock down boxes on the internal network |
01:45.06 | jsmith | Sure... |
01:45.14 | plarsen | hmmm - I'm a pretty big fan; what do you think runs inside most of those fancy firewalls of yours ;) |
01:45.26 | plarsen | But I hate complex network routing problems :( |
01:45.29 | jsmith | tcpdump is your friend, and wireshark is worth every ounce of energy you put into learning it |
01:45.48 | jsmith | I can guarantee that the firewalls I was using didn't have iptables on the inside |
01:46.07 | jsmith | Most had ASICs (application-specific integrated circuits) doing the routing and firewalling |
01:46.25 | plarsen | hmmm - nope ;) If I wanted to do that I would use ethereal ... tcpdump doesn't give you an option to post-filter packages to investigate. But I'll rather not track 30-60 minutes (at least) worth of traffic |
01:46.46 | jsmith | Unfortunately, iptables has a hard time keeping up with several hundred megabits per second of traffic on the line |
01:46.59 | jsmith | plarsen: Capture with tcpdump, analyze later in wireshark |
01:47.24 | jsmith | plarsen: And if you know what types of packets to look for, you can filter down the capture so that it doesn't get too large |
01:48.03 | jsmith | plarsen: Or, you could setup a setup circular ring-buffers to keep the last 45 minutes worth of data... and then wait for the problem to happen, and stop logging then. |
01:49.15 | plarsen | jsmith: ohhh - that last bit sounds interesting. Got any references? |
01:50.40 | jsmith | Check out the -W flag to tcpdump |
01:50.58 | jsmith | (or, if you can get wireshark on the box that's having the problems, look at the capture options window) |
01:51.34 | jsmith | For example, you might do something like: |
01:51.55 | jsmith | tcpdump -C 50 -W 10 -w filename -i eth1 port 4569 |
01:53.18 | jsmith | That's saying "capture all the traffic to or from port 4569 on eth1, and keep 10 files worth of data, with 50 megs in each file" |
01:54.05 | jsmith | After file number 10, it will go back to file number 1 and begin writing there again. |
01:54.45 | jsmith | plarsen: So, here's my proposal... you teach me all about iptables, and I'll teach you about tcpdump |
01:56.44 | plarsen | lol - I've used tcpdump a lot ... but I've stuck to ethereal to do package analysis |
01:56.45 | plarsen | :) |
01:56.53 | plarsen | but sure - that's a deal |
01:56.56 | plarsen | I'm willing to learn more |
02:00.47 | jsmith | ngrep can be useful too... but again, you have to know what you're looking for first |
02:02.27 | plarsen | exactly! |
10:43.05 | *** join/#fredlug jsmith (n=jsmith@72-255-77-7.client.stsn.net) |
13:00.37 | *** join/#fredlug jsmith (n=jsmith@208.253.92.75) |
16:42.25 | *** join/#fredlug bit4man (n=plarsen@c-24-125-211-129.hsd1.va.comcast.net) |
16:48.25 | plarsen_work | howdy doodie |
16:50.06 | plarsen_work | Anyway to re-read xorg.conf without restarting it? |
16:58.29 | jsmith-teaching | Nope |
16:58.49 | jsmith-teaching | Edit, restart X, edit again, restart X, edit again, restart X... rinse and repeat |
16:59.16 | jsmith-teaching | Now, if you're just changing resolution/orientation, and you have the xrandr module loaded, you can use xrandr to change the resolution and rotation without a restart |
16:59.30 | jsmith-teaching | Anything else requires a restart, as I understand it |
17:10.21 | plarsen_work | jsmith-teaching, Well, that's basically what I'm trying to do. This monitor (HP w22) isn't listed, and I'm trying to setup the 1680x1050 resolution required by it. |
17:10.27 | plarsen_work | Keeps getting overwritten though .... |
17:10.46 | jsmith-teaching | What happens if you run xrandr? |
17:11.13 | jsmith-teaching | (without any options) |
17:12.31 | plarsen_work | [plarsen@oem ~]$ xrandr |
17:12.32 | plarsen_work | <PROTECTED> |
17:12.32 | plarsen_work | *0 1600 x 1200 ( 542mm x 406mm ) *60 |
17:12.32 | plarsen_work | <PROTECTED> |
17:12.32 | plarsen_work | <PROTECTED> |
17:12.32 | plarsen_work | <PROTECTED> |
17:12.34 | plarsen_work | <PROTECTED> |
17:12.36 | plarsen_work | <PROTECTED> |
17:12.38 | plarsen_work | <PROTECTED> |
17:12.42 | plarsen_work | <PROTECTED> |
17:12.44 | plarsen_work | C |
17:12.46 | plarsen_work | Current rotation - normal |
17:12.48 | plarsen_work | Current reflection - none |
17:12.50 | plarsen_work | Rotations possible - normal |
17:12.53 | plarsen_work | Reflections possible - none |
17:15.24 | jsmith-teaching | Ok... sounds like you need to add the resolution to your xorg.conf, and possibly add a modeline for that monitor |
17:16.45 | plarsen_work | <PROTECTED> |
17:16.45 | plarsen_work | <PROTECTED> |
17:16.53 | plarsen_work | I've added that - no difference. |
17:17.03 | plarsen_work | Doing a full update now, when it's done I'll restart X and see if it helps. |
17:17.53 | jsmith-teaching | Do you have any other "Modes" lines in your xorg.conf? |
17:18.00 | jsmith-teaching | If not, you may need a "modelines" line |
17:18.46 | plarsen_work | nope, no other modes |
17:19.02 | plarsen_work | Ehh, sorry yes I do |
17:19.10 | plarsen_work | Section "DRI" |
17:19.10 | plarsen_work | <PROTECTED> |
17:19.10 | plarsen_work | <PROTECTED> |
17:19.10 | plarsen_work | EndSection |
17:21.12 | plarsen_work | Since the monitor wasn't listed, this is what I ended up with: |
17:21.15 | plarsen_work | Section "Monitor" |
17:21.15 | plarsen_work | <PROTECTED> |
17:21.15 | plarsen_work | <PROTECTED> |
17:21.15 | plarsen_work | <PROTECTED> |
17:21.15 | plarsen_work | <PROTECTED> |
17:21.16 | plarsen_work | <PROTECTED> |
17:21.18 | plarsen_work | <PROTECTED> |
17:21.20 | plarsen_work | EndSection |
17:26.12 | jsmith-teaching | Have you checked the manual to see what your actual Horizontal Sync rates are? |
17:28.09 | plarsen_work | vert is to be 60 - that's what it says |
17:28.17 | plarsen_work | hori isn't set. |
17:28.22 | plarsen_work | Restarting X now :) |
17:28.25 | plarsen_work | <PROTECTED> |
17:32.38 | *** join/#fredlug plarsen_work (n=plarsen@c-24-125-211-129.hsd1.va.comcast.net) |
17:32.54 | plarsen_work | interesting ... it changed resolution, but it's not listed in the "display" mangement. |
17:46.55 | jsmith-teaching | Figures... |
17:47.07 | jsmith-teaching | My screen does the same thing... 1280x854 is not exactly standard |
17:47.43 | *** join/#fredlug plarsen_work (n=plarsen@c-24-125-211-129.hsd1.va.comcast.net) |
17:47.49 | jsmith-teaching | My screen does the same thing... 1280x854 is not exactly standard |
17:47.57 | jsmith-teaching | (repeated for plarsen's sake) |
17:48.42 | plarsen_work | hmmm - where does it get the list from? I thought that was what the screen/monitor driver was all about? |
17:49.28 | jsmith-teaching | Who knows?!? |
21:31.48 | jsmith-teaching | Not nearly long enough... |
21:32.01 | jsmith-teaching | You can do tricks like using media converters to push it over Cat5 or fiber. |
21:32.23 | jsmith-teaching | Otherwise, you get strange artifacts in the video with anything longer than about 18 feet |
21:41.23 | plarsen_work | hmmm - 18 feet?? I think it's 10 feet and it looks like shadows on the screen :( |
21:42.32 | jsmith-teaching | Yeah... poor cables |
21:42.52 | jsmith-teaching | You'll especially notice it with vertical lines where there's a high contrast between light and dark |
21:42.53 | plarsen_work | hmmm ... true true. It wasn't exactly expensive |
21:43.20 | plarsen_work | there's a slight vertical line(s) moving upwards ... I've never seen that on LCDs before ... |
21:43.26 | plarsen_work | So I'm begining to think it's the cable. |
21:43.36 | plarsen_work | I bought an extension so I can access my KVM from my desk |
21:44.35 | jsmith-teaching | Yeah... |
21:52.47 | plarsen_work | Got ideas on where to get quality cables??? |
21:56.38 | jsmith-teaching | My best ones came from a company that specifically did audio-video type services |
21:56.53 | jsmith-teaching | They used coax cables in the middle to eliminate the noise on the lines. |
22:02.51 | plarsen_work | yeah, I saw several with different filters on them, but I didn't know which if any I needed |
22:03.01 | plarsen_work | I use(d) cable'n'more |
22:03.05 | plarsen_work | Never been disappointed there before |
22:04.45 | plarsen_work | ups, correction - cables'n'more |
22:04.53 | plarsen_work | www.cablesnmore.com |