| === Trixar_za is now known as Trix[a]r_za | ||
| Squirm | morning | 05:12 |
|---|---|---|
| Kilos | morning guys | 05:25 |
| magespawn | good morning early birds | 05:29 |
| Kilos | hey magespawn | 05:29 |
| magespawn | whats up Kilos | 05:29 |
| magespawn | ? | 05:30 |
| Kilos | same old here, and there? | 05:30 |
| magespawn | pretty much, have a transfer today so going to be on the road for awhile | 05:31 |
| Kilos | transfer of aminals | 05:31 |
| magespawn | no people, from richards bay to thanda | 05:31 |
| Kilos | thanda? | 05:32 |
| magespawn | or Thanda, a private game reserve | 05:32 |
| Kilos | aha | 05:32 |
| Kilos | you like a taxi service as well | 05:32 |
| magespawn | yes sometimes | 05:33 |
| Kilos | hehe | 05:33 |
| Kilos | hope you got better road manners than the rest of the taxis around | 05:33 |
| magespawn | but i think it costs a little more for somebody like me that your average taxi | 05:33 |
| magespawn | well i hope so to | 05:33 |
| magespawn | too | 05:33 |
| Kilos | go safe lad and enjoy | 05:34 |
| Kilos | when you leaving magespawn ? | 05:38 |
| magespawn | only at 12:00 | 05:38 |
| Kilos | ah thats good | 05:38 |
| Kilos | have you any idea how to tell ubuntu to allow another wired pc to use your 3g connection | 05:39 |
| Kilos | do they get linked here or what | 05:39 |
| magespawn | not sure, you would have to share the connection somehow | 05:40 |
| magespawn | maybe look in network manager | 05:40 |
| Kilos | ya i made wired shared to others but 3g dont go with | 05:41 |
| Kilos | i will try find more info from you guys friend | 05:41 |
| magespawn | https://help.ubuntu.com/community/Internet/ConnectionSharing | 05:42 |
| Kilos | ty | 05:42 |
| magespawn | have had problems sharing a connection, seems a bit flaky | 05:43 |
| magespawn | but i might be doing something wrong | 05:43 |
| Kilos | lol | 05:43 |
| Kilos | oh well well get there sometime | 05:43 |
| magespawn | http://learnedstuffs.wordpress.com/2012/06/09/internet-connection-sharing-on-ubuntu-12-04/ | 05:44 |
| magespawn | you are using 12.04 now? | 05:44 |
| Kilos | gracias | 05:44 |
| Symmetria | hrm | 05:54 |
| Symmetria | does anyone know how accurate ftime() is under linux? | 05:54 |
| Kilos | lo Squirm | 05:54 |
| Symmetria | or more specifically, does anyone know how to get down to millisecond (and preferably nanosecond) clock accuracy in ANSI C in Linux if ftime() isnt the way to do it | 05:55 |
| Squirm | morning Symmetria | 05:55 |
| Squirm | and I don't know | 05:55 |
| Symmetria | morning squirm, kilos etc :) sorry for the early questions, just getting frustrated at something | 05:55 |
| Kilos | sjoe Symmetria you really wanna cut it fine | 05:56 |
| Symmetria | kilos heh, busy writing a network testing app | 05:56 |
| Kilos | what you wanna check in nanosecs | 05:56 |
| Symmetria | that requires a high degree of accuracy | 05:56 |
| Kilos | ah | 05:56 |
| Symmetria | and lol, even nanoseconds isnt that accurate :) you know they have managed to get atomic clocks synched to an accuracy of 10^16th of a second? :) | 05:57 |
| Symmetria | *THATS* accurate | 05:57 |
| Kilos | wow | 05:57 |
| Symmetria | lol, they wanna get it to down to 10^18th of a second but the fiber distances you need to accomplish that are... insane :) | 05:57 |
| Kilos | hmm they dont believe in " Môre is nog n dag" | 05:58 |
| magespawn | maybe they do, they just want to know exactly when it starts | 05:59 |
| Kilos | haha | 05:59 |
| Symmetria | heh kilos there are actually pretty good reasons for high accuracy clocks, mostly in the astronomy field | 05:59 |
| Symmetria | but they hit a problem after they managed the 10^16th thing | 05:59 |
| Kilos | aha | 05:59 |
| Symmetria | under standard time definitions, you can only drop to 9 billionths of a second | 06:00 |
| Symmetria | :P so now they are trying to get the definition of a second redefined to cater for the 10^16th of a second | 06:00 |
| Symmetria | :p | 06:00 |
| Symmetria | cause thats outside of conventional definitions | 06:00 |
| Symmetria | but right now I'll be happy if I can get down to the millisecond level, and exstatic if I can get down to the nanosecond level | 06:02 |
| magespawn | what are you measuring Symmetria? | 06:02 |
| Kilos | dont you know anyone at nasa | 06:02 |
| Symmetria | magespawn the theory behind what Im developing is almost a type of ping tool, except, its dual ended and measures both forward and verse path latencies, as well as a host of other things based on packet size and number of packets on the wire and itterations through the loop it creates | 06:04 |
| Symmetria | heh, it gets a little tricky though, and it requires that the servers also have properly synched clocks :p | 06:05 |
| Symmetria | (though clock synching is easy, we're busy putting up some GPS based NTP servers for testing purposes, a number of them) | 06:05 |
| magespawn | i think i understood maybe 1 word in 2 in that paragraph | 06:09 |
| Symmetria | magespawn lol basically, Im injecting a number of packets on one side, they send to the other side, the other side (provided the clocks are properly synched), can read the time stamp at time of sending outta the packet, figure out how long it took to get there, then reverse the source/destination address, change the time stamp and send it back | 06:11 |
| Symmetria | and you get a forward and reverse path latency reading | 06:11 |
| Symmetria | then, it flips back and forth through a set number of times to get a baseline | 06:12 |
| magespawn | double ping? multiple ping? with accurate synced time stamps | 06:12 |
| Symmetria | magespawn, ping reads RTT | 06:13 |
| Symmetria | (round trip time) | 06:13 |
| Symmetria | I dont want round trip time, I want forward time and reverse time | 06:13 |
| Symmetria | to check for path a-symmetry | 06:13 |
| Symmetria | and I want to be able to check that through a range of packet sizes and with a set number of packets on the wire similtaneously | 06:14 |
| magespawn | this only does it in one direction until it gets sent back? | 06:14 |
| Symmetria | magespawn basically, the theory behind what Im looking at is this | 06:15 |
| magespawn | sorry lagged a bit there | 06:15 |
| Symmetria | machine a creates a packet, it puts a payload in the packet including the starting time right before transmit | 06:15 |
| Symmetria | it sends it to machine b | 06:15 |
| Symmetria | machine b looks at the timestamp in the packet and compares it to its own clock | 06:16 |
| Symmetria | and says "it took X number of milliseconds for me to get this packet" | 06:16 |
| Symmetria | thats the forward time | 06:16 |
| Symmetria | then it flips the source and destination address and sends it back with a new timestamp | 06:16 |
| Symmetria | and machine a goes "it took X number of milliseconds for it to get from machien b to machine a" | 06:16 |
| Symmetria | thats the reverse path time | 06:16 |
| Symmetria | then, it repeats that process X number of times until either the packet goes missing on the wire or until it finishes its itterations in a loop which gives it a baseline | 06:18 |
| Symmetria | its tricky though, because the servers have to have very accurate clock synchs for it to work | 06:19 |
| magespawn | or else you could add/subtract to the transit time just because of a diffrence in time | 06:20 |
| Symmetria | exactly :) | 06:21 |
| Symmetria | heh, looking at putting down 4 stratum-1 servers for synch in africa though | 06:24 |
| Kerbero | o | 06:32 |
| Kerbero | and you're going to keep them in sync with gps? | 06:33 |
| Kerbero | it would be really interesting to see the result of your pings | 06:33 |
| Kilos | hi Kerbero | 06:36 |
| Kerbero | hi kilos | 06:36 |
| Symmetria | Kerbero yeah | 06:42 |
| Kerbero | Symmetria: do you have any technical specs on how that is done | 06:44 |
| Kerbero | as one can't use a normal gps/rs232 port to get that accurate times from the gps | 06:44 |
| Kerbero | ^ nmea strings | 06:45 |
| superfly | *yawn* | 06:45 |
| superfly | what a wet day | 06:45 |
| Symmetria | Kerbero Im trying to figure that out at the moment :) doing some reading | 06:45 |
| Kerbero | but i guess one would be able to use the rts etc lines on the serial port to input a clock line from the gps | 06:45 |
| Symmetria | Kerbero you can actually buy a gps that is a timing specific gps that is a PCI board | 06:47 |
| Symmetria | gps's from what I read are calbirated either for navigation OR for time, they arent the same, and the timing specific gps's you can get as seperate boards | 06:48 |
| magespawn | would you need one per server? | 06:49 |
| Symmetria | magespawn if you had the servers both synched to multiple stratum-1 ntp servers, they should be in sync enough to allow this | 06:50 |
| Symmetria | since ntp compensates for latency between themselves and the ntp servers | 06:50 |
| magespawn | ahh right that answers the nest question | 06:50 |
| inetpro | good mornings | 07:07 |
| magespawn | hey inetpro | 07:08 |
| magespawn | no meetings? | 07:08 |
| inetpro | eh | 07:10 |
| inetpro | magespawn: at the moment? no | 07:10 |
| inetpro | time for a cuppa coffee | 07:10 |
| inetpro | Maaz: coffee on | 07:11 |
| * Maaz washes some mugs | 07:11 | |
| magespawn | well at least things are looking up on that front then | 07:11 |
| inetpro | lol | 07:11 |
| magespawn | Maaz coffe please | 07:11 |
| Maaz | magespawn: Go get it yourself! | 07:11 |
| magespawn | hah | 07:11 |
| magespawn | Maaz coffee please | 07:11 |
| Maaz | magespawn: Alrighty | 07:11 |
| Kilos | Maaz, coffee please | 07:11 |
| Maaz | Kilos: Okay | 07:11 |
| Kilos | hi inetpro | 07:11 |
| inetpro | Kilos: hi | 07:12 |
| inetpro | at least you guys are still awake | 07:12 |
| Kilos | lol | 07:12 |
| Kilos | i go sort sheep | 07:12 |
| inetpro | or should I rather say alive and kicking | 07:12 |
| Kilos | we need more rain | 07:12 |
| inetpro | Kilos: remember to check for the ticks | 07:13 |
| Kilos | im not catching every one and lifting tails to look | 07:13 |
| inetpro | :-) | 07:13 |
| Kilos | hehe | 07:14 |
| Maaz | Coffee's ready for inetpro, magespawn and Kilos! | 07:15 |
| Kilos | Maaz, ty | 07:15 |
| Maaz | You are welcome Kilos | 07:15 |
| magespawn | Maaz ty botsnack | 07:16 |
| Maaz | thanks, magespawn | 07:16 |
| magespawn | Maaz botsnack | 07:34 |
| Maaz | Yay, at last someone thinks about me as well | 07:34 |
| Symmetria | hrm | 07:38 |
| Symmetria | anyone awake who can do me a favour? | 07:40 |
| Symmetria | http://pastebin.com/AL8p6YFw <== someone take that code, compile it on a linux box, and run it, and lemme know how many itterations per second its claiming and what cpu you are using | 07:40 |
| magespawn | depends on what, so ask away? | 07:40 |
| Symmetria | (I only have one box I can test on, and I wanna make sure that on another box Im getting different results) | 07:40 |
| Symmetria | this old server Im testing on is giving me like, 15k runs per millisecond | 07:41 |
| tonberryE352 | he pastebins are sloow | 07:41 |
| tonberryE352 | that or our it broke something again | 07:41 |
| Symmetria | (and yeah, I know that code is not particularly accurate in what it does, but *shrug* its an ok test of the function) | 07:42 |
| Symmetria | Tonberry lol I can email you the code if you want | 07:43 |
| tonberryE352 | it loaded fine the second time | 07:43 |
| tonberryE352 | strange intermittent issue we seem to be having | 07:43 |
| tonberryE352 | looks like some tcp connections just never connect or do anything | 07:44 |
| Symmetria | heh | 07:44 |
| tonberryE352 | browser will just keep loading until timeout | 07:44 |
| Symmetria | what sorta results re you getting from that code | 07:44 |
| tonberryE352 | but stop and refresh and it shows instantly | 07:44 |
| tonberryE352 | feels like gprs.. | 07:44 |
| tonberryE352 | Executed 27620 increments in 1 milliseconds | 07:45 |
| tonberryE352 | Executed 28366 increments in 1 milliseconds | 07:45 |
| tonberryE352 | Executed 28041 increments in 1 milliseconds | 07:45 |
| tonberryE352 | End time: 1348213520.331 | 07:45 |
| tonberryE352 | seems to stay more or less around that increment count | 07:46 |
| tonberryE352 | model name : Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz | 07:46 |
| tonberryE352 | for my cpu | 07:46 |
| Symmetria | hrm | 07:49 |
| Symmetria | ok well, if its pretty consistant thats good | 07:49 |
| tonberryE352 | you are testing how many times you can increment a number in a millisecond? | 07:50 |
| Symmetria | tonberry was actually just screwing with millisecond timers :) | 07:50 |
| tonberryE352 | ah | 07:50 |
| tonberryE352 | you can get microsecond time with gettimeofday btw | 07:54 |
| Symmetria | tonberry heh various documents on why that isnt accurate though | 07:55 |
| tonberryE352 | i assumed as much | 07:55 |
| Kerbero | i have seen a setting in my bios about fine precision timers | 07:55 |
| Kerbero | *high | 07:56 |
| tonberryE352 | question then is if the kernel knows or cares about them | 07:56 |
| Kerbero | indeed | 07:56 |
| inetpro | oh shucks, I forgot me coffee | 08:03 |
| inetpro | thanks Maaz | 08:03 |
| Kilos | hehe | 08:03 |
| Symmetria | heh Tonberry I still have no clude how to get down to below millisecond timing | 08:09 |
| Symmetria | would be kinda cool if I could get to nanosecond :p | 08:09 |
| tonberryE352 | nano on a pc will be a massive pain i think | 08:10 |
| Symmetria | lol, I still wanna know how those guys got to 10^16th of a second | 08:10 |
| Symmetria | and actually understand it | 08:10 |
| tonberryE352 | with the right hardware anything is possible | 08:12 |
| inetpro | Symmetria: tell us if you find out | 08:16 |
| Symmetria | inetpro lol, there is a paper on it online somewhere, will find it | 08:18 |
| Symmetria | but its so far beyond my comprehension maths wise | 08:18 |
| Symmetria | they were using optical crap to do it | 08:18 |
| inetpro | I just would not know why you'd get into that much detail, so it's beyond m comprehension as well | 08:19 |
| Symmetria | inetpro heh, I can explain that fairly easily, do you know what eVLBI is? | 08:19 |
| inetpro | no | 08:19 |
| Kilos | old peeps dont mind being milliseconds late | 08:19 |
| Symmetria | (its just one example of where you need it) | 08:19 |
| Symmetria | umm ok, eVLBI is whats known as extra very long baseline inteferometary (sp?) | 08:20 |
| Symmetria | its a branch of astronomy science | 08:20 |
| Symmetria | basically, what they do is point a bunch of radio telescopes to the same point in the sky and collect white noise | 08:20 |
| Symmetria | then, they send the white noise to a supercomputer that overlays the signals over each other | 08:20 |
| Symmetria | now, white noise cancels white noise | 08:20 |
| Symmetria | so, whatever is LEFT is an image of sorts | 08:21 |
| Symmetria | but that noise has to be overlaid very carefully, and that requires timing to figure out the overlay | 08:21 |
| Symmetria | the more accurate the timing, the more accurate the overlay, the better definition on the image | 08:21 |
| Symmetria | heh there are numerous branches of science that use that kinda timing | 08:23 |
| Symmetria | ok gotta take doggy to the vet quick :) back in a bit | 08:24 |
| inetpro | Symmetria: ahh, makes sense | 08:27 |
| Kerbero | basically what the SKA will do | 08:29 |
| Kerbero | and some other old dishes throughout africa | 08:29 |
| inetpro | sounds like an interesting challenge | 08:41 |
| === Trix[a]r_za is now known as Trixar_za | ||
| Symmetria | Start time: 1348219641.760 | 09:28 |
| Symmetria | Total of 152840601 itterations completed in 10000ms, average of 15284 per ms | 09:28 |
| Symmetria | End time: 1348219651.760 | 09:28 |
| Symmetria | lol | 09:28 |
| Symmetria | there, I cleaned up my code | 09:28 |
| magespawn | paste? | 09:30 |
| Symmetria | http://pastebin.com/PnMT3r0Q | 09:31 |
| Symmetria | you can change the MILLISECONDS line to specify how long you want it to run for | 09:31 |
| === Trixar_za is now known as Trix[a]r_za | ||
| Kilos | hi Trix[a]r_za psyatw | 10:30 |
| psyatw | hi Kilos | 10:32 |
| psyatw | hi Trix[a]r_za | 10:32 |
| psyatw | and everyone else | 10:32 |
| Symmetria | hrm | 11:20 |
| Symmetria | anyone here who can do me a favour and compile something and run it to send me 100 small packets, Im trying to test something | 11:20 |
| Symmetria | http://pastebin.com/nbE6nYuh | 11:21 |
| Symmetria | that code | 11:21 |
| Symmetria | :P and preferably make sure that your box has a synched clock first | 11:22 |
| Symmetria | else its not gonna work well :p | 11:22 |
| psyatw | hi Symmetria | 11:40 |
| psyatw | it appears to work on Ubuntu 10.04.4 x64 | 11:40 |
| Kerbero | Symmetria, i can | 11:49 |
| Kerbero | have only 10mins though | 11:49 |
| Kerbero | well i need to go show the undergrads how to program\ | 11:54 |
| Kerbero | Symmetria, i'll be back at 17h if you need help | 11:54 |
| psyatw | hi Kerbero | 11:57 |
| Kerbero | o | 11:58 |
| Kerbero | een nederlander | 11:58 |
| Kerbero | goedemiddag | 11:58 |
| Kerbero | ik moet nu gaan | 11:58 |
| Kerbero | doei | 11:58 |
| psyatw | doei | 11:59 |
| Symmetria | http://pastebin.com/chfCHqjC | 12:32 |
| Symmetria | for anyone interested | 12:32 |
| Symmetria | note: that code will only work if the boxes you are using are both properly ntp synched | 12:32 |
| Symmetria | if the timing is out on the boxes that code will break | 12:32 |
| zeref_work | anybody used the mechanize module in python | 13:39 |
| Symmetria | heh wheeeeeeeee | 13:48 |
| Symmetria | http://pastebin.com/kD3WvEpY | 13:48 |
| Symmetria | bug fixed code :) | 13:48 |
| Symmetria | lol havent COMPLETELY forgotten how to code it seems | 13:48 |
| Banlam | "BREAKING: I've been told that an arrest warrant for Julius Malema was issued this morning. Very reliable info. Appearing in court next week." | 13:51 |
| Banlam | http://www.news24.com/SouthAfrica/News/Breaking-Arrest-warrant-issued-for-Malema-20120921-2 | 13:51 |
| Symmetria | heh | 13:55 |
| Symmetria | that money laundering charge | 13:55 |
| Symmetria | is interesting | 13:55 |
| Banlam | will be interesting to see what happens | 13:56 |
| Symmetria | lol, he will go in, and if the courts have any sanity, be denied bail | 13:56 |
| Symmetria | :p | 13:56 |
| Banlam | hah | 13:59 |
| Symmetria | heh | 14:02 |
| Symmetria | it also means by next week | 14:02 |
| Symmetria | his assets will be frozen | 14:03 |
| Symmetria | as is standard procedure | 14:03 |
| Symmetria | at that point, if he continues to travel around, the courts will have grounds to ask who is funding it | 14:03 |
| zeref_work | hrrrmmmm | 14:09 |
| zeref_work | Zuma is funding his travelling tendencies | 14:09 |
| Symmetria | not a chance | 14:12 |
| Symmetria | zuma wants malema at the bottom of the limpopo river | 14:12 |
| Symmetria | :p | 14:12 |
| zeref_work | lol | 14:12 |
| zeref_work | trial will go on forever | 14:13 |
| zeref_work | will prob be found uilty | 14:13 |
| zeref_work | malema will claim sudden illness | 14:13 |
| zeref_work | *guilty | 14:14 |
| zeref_work | NOT 1 day in jail | 14:14 |
| Squirm | ooooh, New Mumford and Sons :D | 15:28 |
| Symmetria | hrm | 16:50 |
| Symmetria | anyone awake? | 16:50 |
| Kerbero | yes? | 16:53 |
| Symmetria | Kerbero | 16:56 |
| Symmetria | do me a favour | 16:56 |
| Symmetria | make sure your box is ntp synched | 16:56 |
| Symmetria | then... | 16:56 |
| Symmetria | download this: | 16:56 |
| Symmetria | http://pastebin.com/KrncXZTW | 16:56 |
| Symmetria | compile it | 16:56 |
| Kerbero | 1. duh | 16:56 |
| Symmetria | and run it with ./client 196.32.210.12 500 50 | 16:56 |
| Symmetria | :) | 16:57 |
| Kerbero | :~$ sudo service ntp stop | 16:58 |
| Kerbero | * Stopping NTP server ntpd [ OK ] | 16:58 |
| Kerbero | :~$ sudo ntpdate ntp.sun.ac.za | 16:58 |
| Kerbero | 21 Sep 18:57:57 ntpdate[1038]: adjust time server 146.232.128.1 offset 0.001488 sec | 16:58 |
| Kerbero | :~$ sudo service ntp start | 16:58 |
| Kerbero | * Starting NTP server ntpd [ OK ] | 16:58 |
| Symmetria | did it run? | 16:58 |
| Symmetria | you might be firewalled sending that shit :( | 16:59 |
| Symmetria | cause I aint seeing packets :p | 16:59 |
| Kerbero | need to compile still | 16:59 |
| Symmetria | aaahh | 16:59 |
| Symmetria | lol | 16:59 |
| Symmetria | that would be why | 16:59 |
| Symmetria | :) | 16:59 |
| Symmetria | it should compile clean under linux, its broken under fbsd :P | 16:59 |
| Symmetria | because fbsd doesnt include ftime() | 16:59 |
| Kerbero | ok here we go | 16:59 |
| Symmetria | *hrm* ok, do me a favour, ping that ip address | 17:00 |
| Kerbero | ran | 17:00 |
| Symmetria | and tell me what times you getting | 17:00 |
| Kerbero | jip it pings | 17:00 |
| Symmetria | what latency? | 17:00 |
| Kerbero | 207-209 | 17:00 |
| Symmetria | *HRM* interesting | 17:00 |
| Symmetria | lower latency from you -> me then from me -> you | 17:01 |
| Symmetria | your forward latency is around 90 - 100 | 17:01 |
| Kerbero | wow | 17:01 |
| Kerbero | hmm | 17:01 |
| Kerbero | just a sec | 17:01 |
| Symmetria | Received packet. Packet delay calculated at 91 ms | 17:01 |
| Symmetria | Received packet with 82 bytes of data with sequence number 498, padding size is 50 | 17:01 |
| Symmetria | Received timestamp 1348246822:998 | 17:01 |
| Symmetria | Received packet. Packet delay calculated at 91 ms | 17:01 |
| Symmetria | Received packet with 82 bytes of data with sequence number 499, padding size is 50 | 17:01 |
| Symmetria | Received timestamp 1348246823:48 | 17:01 |
| Symmetria | Received packet. Packet delay calculated at 99 ms | 17:01 |
| Kerbero | can i run again? | 17:01 |
| Symmetria | go for it | 17:01 |
| Symmetria | heh, whatever you did stabilized the latency / dropped it slightly | 17:02 |
| Symmetria | 89 - 90 pretty constant | 17:02 |
| Kerbero | indeed | 17:02 |
| Symmetria | :P you can dig through that code and figure out how it works, though I wanna put code in both sides to actually do some clock negotiation | 17:02 |
| Kerbero | ye | 17:03 |
| Symmetria | rather than relying on the ntp clocks being right | 17:03 |
| Symmetria | but I have no idea how to code that clock negotiation (yet) | 17:03 |
| Kerbero | but you see my clock is not out more than 2ms | 17:03 |
| Symmetria | *nod* | 17:04 |
| Symmetria | the problem is, mine may be, because the closest stratum-1 servers I have are at least 30 ms away | 17:04 |
| Kerbero | hmm | 17:04 |
| Symmetria | +ntp1.tdc.fi .PPS. 1 u 31 64 377 33.237 -1.958 1.661 | 17:04 |
| Symmetria | +ntp2.tdc.fi .PPS. 1 u 26 64 377 31.939 -1.853 1.694 | 17:04 |
| Symmetria | *ntp.meerval.net .GPS. 1 u 30 64 377 23.410 -7.253 2.462 | 17:04 |
| Kerbero | ntp.sun is 2ms away | 17:04 |
| Symmetria | what stratum is ntp.sun? | 17:05 |
| Kerbero | no idea | 17:05 |
| Kerbero | definitely not 1 | 17:05 |
| Kerbero | :P | 17:05 |
| Symmetria | do an ntpq -p | 17:05 |
| Symmetria | :p | 17:05 |
| Kerbero | *maties1.sun.ac. 196.25.1.1 3 u 45 64 177 0.977 -0.459 0.508 | 17:05 |
| Symmetria | ouch | 17:05 |
| Symmetria | lemme give you some .za 1's | 17:05 |
| Symmetria | ntp server 146.64.8.7 | 17:06 |
| Symmetria | ntp server 146.64.58.41 | 17:06 |
| Symmetria | use those 2 | 17:06 |
| Symmetria | they are both in .za and both stratum-1s | 17:06 |
| Symmetria | oh, and stratum1.neology.co.za has address 41.73.40.11 | 17:06 |
| Symmetria | there :p you can run 3 | 17:06 |
| Symmetria | :) | 17:06 |
| Kerbero | well i doubt that ntpd will sync with them immediately | 17:08 |
| Symmetria | almost immediately :) | 17:08 |
| Symmetria | it take under 5 seconds :) | 17:08 |
| Kerbero | ok | 17:08 |
| Symmetria | if you run a ntpq -p you will see if they are synched :) | 17:08 |
| Symmetria | if they arent they will say .INIT. | 17:08 |
| Kerbero | ahh | 17:09 |
| Kerbero | delay offset and jitter are all 0 | 17:09 |
| Kerbero | ntpd will build that up over time i guess | 17:09 |
| Symmetria | it still saying INIT on them? | 17:09 |
| Symmetria | or what? | 17:09 |
| Kerbero | yes | 17:10 |
| Symmetria | ok it aint inited yet | 17:10 |
| Symmetria | should change in a coupla seconds | 17:10 |
| Symmetria | unless your firewalling blocks it | 17:10 |
| Kerbero | it's stellenbosch.... | 17:10 |
| Kerbero | yes | 17:11 |
| Symmetria | LOL so still on init? | 17:11 |
| Kilos | hi smile | 17:42 |
| smile | hi Kilos :p | 17:42 |
| smile | brb :) | 17:43 |
| Symmetria | kilos wanna help me test something? I got some tests from kerbero, but I want some more tests :) | 17:59 |
| Kilos | ok | 17:59 |
| Kilos | just dont ask me to compile stuff | 18:00 |
| Symmetria | http://pastebin.com/KrncXZTW <=== haha you need to compile that :p | 18:00 |
| Kilos | tell me how and lets go | 18:00 |
| Symmetria | ok, get that shit off pastebin, and stick it in a text file | 18:00 |
| Kilos | i dunno what compile is | 18:00 |
| Symmetria | then type gcc -o client textfile | 18:00 |
| Symmetria | :p | 18:00 |
| Kilos | ok sec | 18:00 |
| Symmetria | just make sure you copy it from the raw paste so you dont get all the line number bullshit in it :) | 18:00 |
| Kilos | wow that pastebin is slow | 18:02 |
| Kilos | paste it to slexy.org rather | 18:02 |
| Kilos | nm it opened | 18:02 |
| Symmetria | :) | 18:03 |
| Kilos | in place of textfile i gotta put path hey | 18:05 |
| Symmetria | well, whhat file did you save the stuff in | 18:05 |
| Symmetria | cause its that filename you change textfile to | 18:05 |
| Kilos | its on my desktop | 18:05 |
| Symmetria | then yeah you put the full path to the filename | 18:05 |
| Kilos | grr | 18:07 |
| Kilos | /home/miles/Desktop/textfile: file not recognized: File format not recognized | 18:08 |
| Kilos | collect2: ld returned 1 exit status | 18:08 |
| Symmetria | nono, gimme the full command you are typing | 18:08 |
| Symmetria | to compile that textfile | 18:08 |
| Symmetria | it should be gcc -o client /home/miles/Desktop/textfile | 18:08 |
| Symmetria | which should make a file called client | 18:08 |
| Kilos | gcc -o client ~/Desktop/textfile | 18:09 |
| Symmetria | ok did that work | 18:10 |
| Symmetria | it should have made a file called client | 18:10 |
| Kilos | nope | 18:10 |
| Kilos | gcc -o client /home/miles/Desktop/textfile | 18:10 |
| Kilos | /home/miles/Desktop/textfile: file not recognized: File format not recognized | 18:10 |
| Kilos | collect2: ld returned 1 exit status | 18:10 |
| Symmetria | is it just the text from the pastebin in that textfile | 18:11 |
| Kilos | yeah i copied the bottom window | 18:11 |
| Symmetria | *HRM* lemme email you the file as an attachment :) | 18:11 |
| Symmetria | whats your email address | 18:12 |
| Kilos | msdomdonner@gmail.com | 18:12 |
| Kilos | when i open your file it has coloured text in it | 18:13 |
| magespawn | Symmetria perhaps have Kilos cd to where the file is | 18:13 |
| magespawn | hey Kilos | 18:13 |
| Kilos | yes | 18:13 |
| Symmetria | kilos I emailed you client.c | 18:13 |
| Symmetria | :) | 18:13 |
| Kilos | ok i got client.c on desktop | 18:14 |
| Symmetria | ok, now try gcc -o client /home/miles/Desktop/client.c | 18:15 |
| Kilos | what now | 18:15 |
| Kilos | lol | 18:15 |
| Symmetria | and tell me what it says | 18:15 |
| Kilos | /home/miles/Desktop/client.c: In function ‘main’: | 18:15 |
| Kilos | /home/miles/Desktop/client.c:58: warning: format ‘%s’ expects type ‘char *’, but argument 2 has type ‘char (*)[20]’ | 18:15 |
| Symmetria | thats fine, you can ignore that :) | 18:16 |
| Symmetria | did it make a file called client? | 18:16 |
| Kilos | where? | 18:16 |
| Symmetria | in the directory where you ran that gcc command | 18:16 |
| Symmetria | there should be a file called client | 18:16 |
| Kilos | on Desktop? | 18:17 |
| Symmetria | if there is, type ./client 196.32.210.12 50 50 and it should start spewing out a bunch of stuff | 18:17 |
| Symmetria | well, what directory where you in when you typed the gcc command? | 18:17 |
| Kilos | cli on desktop | 18:18 |
| Symmetria | if you ran that from terminal, just go back to teh same terminal window and type the ./client 196.32.210.12 50 50 command | 18:18 |
| Symmetria | yeah go back to cli | 18:18 |
| Kilos | no client file here | 18:18 |
| Symmetria | to the same place | 18:18 |
| Symmetria | *HRM* | 18:18 |
| Symmetria | ok, go back to the cli in desktop | 18:18 |
| Symmetria | and type gcc -o client client.c && ls -l client | 18:18 |
| Symmetria | and tell me what it says | 18:18 |
| Symmetria | :) | 18:18 |
| Kilos | miles@P4:~$ gcc -o client client.c && ls -l client | 18:19 |
| Kilos | gcc: client.c: No such file or directory | 18:19 |
| Kilos | gcc: no input files | 18:19 |
| Symmetria | *HRM* | 18:19 |
| Symmetria | oh you arent in desktop | 18:19 |
| Kilos | hehe | 18:19 |
| Kilos | oh where am i | 18:19 |
| Symmetria | you're in your home directory :) | 18:19 |
| Symmetria | type cd ~/Desktop | 18:19 |
| Symmetria | and then rerun the gcc -o client client.c && ls -l client | 18:19 |
| Symmetria | :p | 18:19 |
| Symmetria | heh the ~$ says you were in your base home directory :) | 18:20 |
| Kilos | client.c: In function ‘main’: | 18:20 |
| Kilos | client.c:58: warning: format ‘%s’ expects type ‘char *’, but argument 2 has type ‘char (*)[20]’ | 18:20 |
| Kilos | -rwxr-xr-x 1 miles miles 7795 2012-09-21 20:20 client | 18:20 |
| Symmetria | aha | 18:21 |
| Symmetria | now type ./client 196.32.210.12 50 50 | 18:21 |
| Symmetria | :) | 18:21 |
| Kilos | its green | 18:21 |
| Symmetria | in the cli window in the ~/Desktop directory | 18:21 |
| Symmetria | :) | 18:21 |
| Kilos | holy moly | 18:21 |
| Kilos | how much of that you wanna see | 18:21 |
| Symmetria | heh, wait, need you to run it again :) then will see it on my side, lemme just get back to the server | 18:22 |
| Symmetria | ok run the same command again | 18:22 |
| Symmetria | and tell me when you've run it :) | 18:22 |
| Symmetria | aahh there we go | 18:22 |
| Symmetria | I see it | 18:22 |
| Kilos | done | 18:22 |
| Symmetria | :) ok, firstly, your clock is out | 18:22 |
| Symmetria | uumm | 18:23 |
| Symmetria | type ntpdate stratum1.neology.co.za | 18:23 |
| Kilos | give command to sync it | 18:23 |
| Symmetria | that should sync it at least temprorarily | 18:23 |
| Symmetria | :) | 18:23 |
| Symmetria | then rerun the command :) | 18:23 |
| Symmetria | I recon you're about 700ms out before the ntpdate command | 18:23 |
| Symmetria | (700ms slow) | 18:24 |
| Kilos | ok synced here comes the run thing | 18:24 |
| Symmetria | once you've run that ntpdate command, it should sync, and when you rerun the client command, the readings should be more accurate | 18:24 |
| Symmetria | k | 18:24 |
| Symmetria | bingo :) | 18:24 |
| Symmetria | Received packet. Packet delay calculated at 75 ms | 18:24 |
| Symmetria | Received packet with 74 bytes of data with sequence number 48, padding size is 50 | 18:24 |
| Symmetria | Received timestamp 1348251881:858 | 18:24 |
| Symmetria | Received packet. Packet delay calculated at 64 ms | 18:24 |
| Symmetria | Received packet with 74 bytes of data with sequence number 49, padding size is 50 | 18:24 |
| Symmetria | Received timestamp 1348251881:908 | 18:24 |
| Symmetria | Received packet. Packet delay calculated at 75 ms | 18:24 |
| Symmetria | you have a pretty low outbound latency to europe :) | 18:24 |
| Kilos | dont tell me | 18:25 |
| Kilos | fix it | 18:25 |
| Symmetria | heh, the problem with this is the clock shift between yourself and myself | 18:25 |
| Symmetria | kilos lol, actually low is good | 18:25 |
| Symmetria | high would suck :) | 18:25 |
| Kilos | oh haha | 18:25 |
| Symmetria | heh, what thats basically saying is its taking 75 1000ths of a second | 18:26 |
| Symmetria | for a packet to go from you to london | 18:26 |
| Kilos | whew | 18:26 |
| Symmetria | providing the clock syncs are accurate on both sides :) | 18:26 |
| Symmetria | heh, you have some jitter on your client though which isnt so nice | 18:27 |
| Symmetria | Received packet. Packet delay calculated at 68 ms | 18:27 |
| Symmetria | Received packet with 74 bytes of data with sequence number 37, padding size is 50 | 18:27 |
| Symmetria | Received packet. Packet delay calculated at 77 ms | 18:27 |
| Symmetria | Received packet with 74 bytes of data with sequence number 38, padding size is 50 | 18:27 |
| Symmetria | heh ideally, you want something that has a very consistant delay | 18:27 |
| Symmetria | cause that variation in delay is whats called jitter | 18:28 |
| Symmetria | (It wont have a negative effect on you, but in certain situations that can be nasty) | 18:28 |
| Symmetria | kilos heh, basically, what that software you ran does | 18:28 |
| Kilos | what is causing it | 18:28 |
| Symmetria | is get the time your machine | 18:28 |
| Symmetria | then stick it into a udp packet | 18:28 |
| Symmetria | and then the udp packet to me | 18:28 |
| Symmetria | I then compare that timestamp to the timestamp on my server | 18:28 |
| Symmetria | and calculate the difference | 18:28 |
| Kilos | is your server in london | 18:29 |
| Symmetria | your machine sends one packet every 50 milliseconds for however many number of packets you tell it (50 is what you ran on the cli) | 18:29 |
| Symmetria | yeah | 18:29 |
| Symmetria | then the other setting (the second 50 you specified) is the packet size | 18:29 |
| Symmetria | we basically pad the packets by 50 data bytes just to make it a more realistic test | 18:29 |
| Symmetria | (well, its a pad of 50, actual packet size is 74 bytes) | 18:30 |
| Kilos | magespawn, you watching this | 18:30 |
| Symmetria | as I say, the PROBLEM with that code is that it relies on the clocks being identically synched | 18:30 |
| Symmetria | and thats extremely difficult to do because of asymmetrical routing to the ntp servers | 18:30 |
| Symmetria | (ntp works by getting a time from the ntp server, working out the latency between you and the ntp server, dividing the latency by 2, adding that to the time its got and setting the time) | 18:31 |
| Symmetria | (though using multiple servers it kinda averages them and it gets better accuracy) | 18:31 |
| Kilos | so where did we sync my time | 18:32 |
| Symmetria | to johannesburg | 18:32 |
| Kilos | ah | 18:32 |
| Symmetria | ntpdate will synch it but not very accurately, to get high accuracy you need to install ntpd | 18:32 |
| Kilos | if you want time synced more accuratley why not sync to the same server on both sides | 18:32 |
| Symmetria | apt-get install ntp, then edit the config in /etc/ntp.conf and replace the server lines in there | 18:32 |
| smile | * doei! :) | 18:33 |
| Symmetria | kilos heh, because the latency between the time server and your ntp client has a noticeable effect | 18:33 |
| Kilos | ah | 18:33 |
| Symmetria | and if you're using stratum-1 servers, the clocks on those servers are probably within 2 1000ths of a second anyway | 18:33 |
| Symmetria | (a stratum-1 server = its setting its clock via a GPS receiver) | 18:33 |
| Kilos | eish i cant even think that small man | 18:33 |
| Kilos | you cant snap your fingers that fast | 18:34 |
| Symmetria | the only thing really more accurate than a stratum-1 server is an atomic clock and lol, if you think a thousandth of a second is small, thats still huge | 18:34 |
| smile | good night, Kilos :) | 18:34 |
| Symmetria | kilos, lol, they managed to sync 2 atomic clocks to an accuracy of 10^16 of a second | 18:34 |
| Kilos | night smilsleep tight | 18:34 |
| Symmetria | thats 100000000000000000th of a second :P | 18:35 |
| Kilos | that is rather on the accurate side hey | 18:35 |
| Symmetria | lol, they wanna get it to 10^18 but I dont see them doing it any time soon | 18:35 |
| Symmetria | the complexity of getting to the 10^16th is already crazy and requires like, 900 kilometer long optical fiber links to work with | 18:36 |
| Symmetria | (they know the exact speed of light through optical fiber so they can use long lengths of fiber and time delays and dispersion etc to get accuracy) | 18:36 |
| Kilos | how can that work on the internet | 18:36 |
| Symmetria | lol, well, thats something people are working on :P | 18:37 |
| Symmetria | there are entire papers on this | 18:37 |
| Kilos | cant work i think | 18:37 |
| Symmetria | heh, on the general internet no, it doesnt work 2 well | 18:37 |
| Symmetria | but they have uses for it | 18:37 |
| Kilos | service providers with mess up in between | 18:37 |
| Symmetria | wait lemme find this | 18:38 |
| Symmetria | http://www.ces.net/events/2012/cef/p/Comparison%20of%20clocks%20using%20optical%20fiber%20links%20in%20recent%20results%20and%20future%20projects.pdf | 18:40 |
| Symmetria | http://www.ces.net/events/2012/cef/p/Time%20transfer%20by%20using%20SONET%20connections%20between%20SP%20and%20Mikes%20in%20experiences%20and%20results.pdf | 18:40 |
| Symmetria | both of those are interesting :) | 18:40 |
| Symmetria | the first one you probably need a maths degree to understand half of it though :P | 18:40 |
| Symmetria | its way over my head | 18:40 |
| Symmetria | oh, they got to 10^18 | 18:41 |
| Kilos | aint we got any wiz kids here | 18:41 |
| Kilos | big storm here dunno how long power will hold out | 18:42 |
| Symmetria | lol not sure we have any at that level :p | 18:42 |
| Kilos | i dont see where such accuracy can be used | 18:42 |
| Kilos | stars move in years | 18:42 |
| Kilos | if you see it tonight its in the same place tomorrow night | 18:43 |
| Symmetria | kilos heh, space time distances, overlaying of data etc | 18:43 |
| Symmetria | kilos, if you put 10 radio telescopes at the same point in the sky with the telescopes spread around the globe | 18:43 |
| Symmetria | you then take the white noise they collect | 18:43 |
| Symmetria | and you overlay it ontop of each other in a supercomputer | 18:43 |
| Symmetria | the white noise cancels itself out | 18:44 |
| Symmetria | and what you're left with is an image | 18:44 |
| Symmetria | that requires incredibly accurate time calculations to do the overlay properly | 18:44 |
| Kilos | image of what | 18:44 |
| Symmetria | and the more accurate the overlay is, the higher the resolution of what you're looking at | 18:44 |
| Kilos | same as mixing colours on a tv to make others | 18:44 |
| Symmetria | kilos well, its not really an "image" as you'd imagine, but basically, they are looking for stars that are very far away :p | 18:44 |
| Symmetria | and radio signatures and crap to find them | 18:45 |
| Symmetria | and tell how far away they are etc :) | 18:45 |
| Symmetria | and ever spoken to an astronomer? their "accuracies" can be a few million kilometers out | 18:45 |
| Symmetria | and sometimes a few hundred million kilometers | 18:45 |
| Symmetria | so they refine the clock accuracies etc to get more accurate in other measurements | 18:45 |
| Kilos | ah | 18:46 |
| Symmetria | time is a rather key component of physics from what I understand (though my understanding of physics is almost non-existant and I openly admit that) | 18:46 |
| magespawn | yes Kilos just read the logs | 18:47 |
| Kilos | sorry we missed you help there magespawn | 18:47 |
| Kilos | things go too fast for me | 18:48 |
| Kilos | cd to desktop methinks it was | 18:48 |
| magespawn | no worries | 18:48 |
| magespawn | yup | 18:48 |
| Kilos | i always battled to find the path to it | 18:48 |
| Symmetria | heh here is an interesting one | 18:48 |
| Kilos | that ~ goodie works kiff | 18:49 |
| Symmetria | apparently the speed of light through fiber changes dependant on the temp of the fiber | 18:49 |
| Symmetria | :p | 18:49 |
| Kilos | isnt the speed of light a constant | 18:49 |
| magespawn | only in a vacuum | 18:49 |
| magespawn | the density will affect the speed | 18:50 |
| Kilos | ah | 18:50 |
| magespawn | density is affected by temperature | 18:50 |
| Kilos | if we cant get data to move that fast how they gonna get spaceships to go faster even | 18:51 |
| Symmetria | heh kilos speed of light through glass for example | 18:51 |
| Symmetria | is significantly slower than the speed of light through a vaccum | 18:51 |
| magespawn | einstein's theory says it is impossible | 18:52 |
| Kilos | aha | 18:52 |
| Symmetria | (if we didnt have to deal with the slowdown through glass, the internet would run better) | 18:52 |
| magespawn | i thought fiber was hollow | 18:52 |
| Kilos | not if vodacom and company are involved | 18:52 |
| Symmetria | magespawn heh, yes, einstein's theory says moving faster than light is impossible, but he doesnt discount the possibilities of bending space/time | 18:52 |
| Symmetria | magespawn *shake* fiber is glass, the light moves through glass, which means your latency is actually worked on about 2/3rds the speed of light | 18:53 |
| magespawn | so we what is called einstien space | 18:53 |
| Symmetria | thats part of the reason why if you bend fiber 2 far | 18:53 |
| Symmetria | it breaks and cant be repaired | 18:53 |
| Symmetria | the glass shatters | 18:53 |
| Symmetria | and your fiber is fubar :) | 18:53 |
| magespawn | i always thought it was more a tube than a solid | 18:53 |
| Symmetria | no, its glass :) very very very thin glass (strands are no thicker than a human hair) | 18:54 |
| magespawn | if you could make it a tube you could make a partial vacuum and speed it up | 18:54 |
| Symmetria | :) maintaining a vaccum through it would be rough though | 18:55 |
| Symmetria | lol one of the universities whined at me once about the latency to london | 18:55 |
| Symmetria | :P I told them they had an awesome physics department, go figure out how to bend space/time | 18:55 |
| Kilos | hehe | 18:55 |
| Symmetria | and when they had, come tell me, and I'd reduce their latency using their research | 18:55 |
| Symmetria | :p they werent impressed with me | 18:55 |
| magespawn | he lol | 18:56 |
| magespawn | i am off, good night all | 18:57 |
| Kilos | night magespawn | 18:57 |
| Kilos | sleep tight | 18:57 |
| Symmetria | later man | 18:58 |
| Symmetria | :P Im pondering hw to do DWDM through a vaccum | 18:58 |
| Symmetria | cause that would be awesomenes | 18:58 |
| Kilos | lol | 18:59 |
| Kilos | you on your new pc? | 18:59 |
| Symmetria | lol back later, Im gonna go contemplate that one over a beer :P and hehe yeah I got my new pc | 18:59 |
| Symmetria | its fast as hell :) | 18:59 |
| Kilos | thats nice | 18:59 |
| Kilos | enjoy your beer | 19:00 |
| Kilos | night all . sleep tight | 19:02 |
| === Trix[a]r_za is now known as Trixar_za | ||
| === Trixar_za is now known as Trix[a]r_za | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!