code logs -> 2009 -> Sat, 11 Jul 2009< code.20090710.log - code.20090712.log >
--- Log opened Sat Jul 11 00:00:37 2009
01:26 Vornicus [Vornicus@Admin.Nightstar.Net] has quit [Quit: ]
01:29 Vornicus [~vorn@ServicesOp.Nightstar.Net] has joined #code
01:29 mode/#code [+o Vornicus] by ChanServ
01:57 TarinakyKai [~Tarinaky@Nightstar-16638.plus.com] has joined #code
01:59 Tarinaky [~Tarinaky@Nightstar-16638.plus.com] has quit [Ping Timeout]
02:19
<@Consul>
Anybody know of any typography/logo design types geeks that I can bounce something off of
02:19
<@Consul>
?
02:19
<@SmithKurosaki>
What you mean
02:19
<@SmithKurosaki>
I am kind of artsy
02:19
<@Consul>
Well, someone who knows their stuff as far as lettering is concerned, I guess.
02:20
<@Consul>
I'm designing a logo for my "band" (consisting of only me), and I just wanted to bounce it off of someone. In private, though, because I can't afford the domain yet.
02:20
<@SmithKurosaki>
ahh
02:20
<@SmithKurosaki>
Well, I can let you know what I think
02:21
<@Consul>
Can you receive DCC?
02:21
<@SmithKurosaki>
mhm
02:22
<@SmithKurosaki>
Or at least I should be able to
02:22
<@Consul>
Sending.
02:22
<@Consul>
Err, time out.
02:23
<@SmithKurosaki>
Gnar
02:23
<@SmithKurosaki>
One sec
02:24 AgentIchiro [~Smith@Nightstar-9012.dsl.teksavvy.com] has joined #code
02:24
< AgentIchiro>
Hey consul, can you try sending it again
02:25
< AgentIchiro>
I hope using the other server I have, it's set up for DCCs
02:25
<@Consul>
Timeout again.
02:25
< AgentIchiro>
I don't know what then
02:25
< AgentIchiro>
Sorry
02:25 AgentIchiro [~Smith@Nightstar-9012.dsl.teksavvy.com] has quit [Client exited]
02:26
<@SmithKurosaki>
Cool, my name is yellow instead of pink
02:28
<@Vornicus>
Looks pink here.
02:37
<@SmithKurosaki>
Ahh, I am also AI
02:37
<@SmithKurosaki>
Well, was
02:38 TarinakyKai [~Tarinaky@Nightstar-16638.plus.com] has quit [Client exited]
02:50
<@Vornicus>
Aha
02:50
<@Vornicus>
Yes, AI was yellow
02:50 * Vornicus cookies SmithKurosaki.
02:51
<@SmithKurosaki>
o.0 A cookie. Yay!
02:51
<@SmithKurosaki>
It helps me feel better
02:54
<@Consul>
Flu?
03:03
<@SmithKurosaki>
Stress induced fever and tiredness
03:03
<@Consul>
Ick
03:03
<@SmithKurosaki>
I am not vomitting or anything
03:36 Attilla [~The.Attil@92.18.70.ns-3721] has quit [Ping Timeout]
03:43 Attilla [~The.Attil@92.10.161.ns-3869] has joined #code
03:44 mode/#code [+o Attilla] by ChanServ
04:37
<@ToxicFrog>
Consul: check your firewall/router.
04:37
<@ToxicFrog>
DCC send issues are almost always on the sender's side, because of the way DCC works.
04:37
<@Consul>
ToxicFrog: I already did. I don't have it set to block anything outgoing.
04:37
<@ToxicFrog>
DCC uses incoming connections.
04:38
<@ToxicFrog>
The reciever connects to the sender.
04:38
<@Consul>
That's odd...
04:38
<@ToxicFrog>
The sender sends a CTCP DCC message to the receiver saying what host and port to connect to.
04:38
<@Consul>
So the sender sends a request for the receiver to send a request for connection?
04:38
<@Consul>
Ah, I see.
04:38
<@ToxicFrog>
The receiver then connects to that host and port to receive the actual data.
04:39
<@ToxicFrog>
So, common failure modes are:
04:39
<@ToxicFrog>
- your firewall is blocking inbound connections on the port range you're using for DCC
04:39
<@ToxicFrog>
- you opened a hole in the firewall but forgot to tell DCC to use only those ports
04:40
<@ToxicFrog>
- you are behind a NAT gateway (eg, most routers and some modems) and haven't told your IRC client what your external IP is, so it tells the receiver to connect to 192.168.1.50 or similar
04:40
<@Consul>
Yeah, I'm in my firewall settings now.
04:40
<@Consul>
Uhh
04:41
<@Consul>
Since my external IP changes, how can xchat ever know what it is?
04:42
<@ToxicFrog>
I believe modern xchats have a "determine IP automatically" option, although I don't know how well that works.
04:42
<@ToxicFrog>
Personally, I have a domain name and just tell it to use that.
04:43
<@ToxicFrog>
You can also change it yourself when your external IP changes.
04:43
<@Consul>
Argh
04:43
<@ToxicFrog>
Or use a plugin to do it automatically.
04:43
<@Consul>
This firewall stores exceptions for fixed IPs.
04:43
<@Consul>
I have DHCP set up.
04:43
<@Consul>
This is definitely not a *tonight* project.
04:43
<@ToxicFrog>
Your router/firewall doesn't support static DHCP or hash DHCP?
04:44
<@Consul>
Eh, it might be able to do static DHCP.
04:44
<@Consul>
It was free from the ISP, I'll put it that way.
04:46
<@Consul>
I can't make heads or tails of this crap interface. It looks like static DHCP might be the default. It seems to have my computer listed to use the same IP.
04:47
<@Consul>
Can I try sending you something?
04:47
<@Consul>
It's amazing how big of a hack IRC is.
04:47
<@Consul>
And yet it works.
04:47
< Namegduf>
Mostly. :P
04:48
<@ToxicFrog>
Go ahead.
04:48
<@Consul>
I'll try to find something G-rated. :-P
04:49
<@Consul>
Nothing?
04:54
<@Consul>
Okay, trying again...
04:54
<@ToxicFrog>
It worked, kind of
04:54
<@ToxicFrog>
Only not really
04:54
<@Consul>
Okay, what would cause it to "kinda work?"
04:55
<@ToxicFrog>
It connects and transfers 1k, and then drops.
04:55
<@ToxicFrog>
First one was connection reset by peer; second one was stall.
04:56
<@ToxicFrog>
I can however verify that it is reporting the correct IP; you have no worries on that score.
04:56
<@Consul>
Try #2
04:56
<@Consul>
Err #3
04:57
<@Consul>
Well, this is enough to piss me off.
04:57
<@Consul>
Is DCC TCP or UDP?
04:57
<@ToxicFrog>
Once again, it transfers 1k and then stops.
04:57
<@ToxicFrog>
It's almost like my acks aren't reaching you or something.
04:57
<@ToxicFrog>
And it's TCP.
04:59
<@ToxicFrog>
http://www.irchelp.org/irchelp/rfc/index.html
05:00
<@Consul>
This router is really pissing me off.
05:00
<@Consul>
I can't edit the rule I just made.
05:01
<@Consul>
But if I make another rule, I can edit that one.
05:04
<@Consul>
Turns out I have to deactivate it before I can edit it.
05:04
<@Consul>
Okay, #4
05:05
<@Consul>
Okay...
05:05
<@ToxicFrog>
Same thing.
05:05
<@Consul>
The literature I found said to open up 2070 to 2075 for DCC...
05:05
<@ToxicFrog>
Connects fine, recieves 1k of data, drops.
05:05
<@Consul>
That's obviously wrong.
05:05
<@ToxicFrog>
DCC doesn't use any fixed ports.
05:05
<@Consul>
I have to open up the whole damn machine?
05:05
<@ToxicFrog>
Configure your client to use any port range you see fit, and open/forward that port range accordingly.
05:06
<@ToxicFrog>
Settings, PReferences, File Transfers in xchat.
05:06
<@ToxicFrog>
I use 8010-8020.
05:07
<@Consul>
Okay, let's try this again...
05:07
<@Consul>
Umm, you're still demanding a different range than I can accept.
05:07
<@Consul>
Or do I need to restart xchat?
05:08
<@ToxicFrog>
What do you mean by "demanding a different range than you can accept"?
05:08
<@Consul>
The request from you is still coming in on 8010.
05:08
<@ToxicFrog>
Because that's what your client is asking for, according to the log.
05:08
<@ToxicFrog>
Although, let's double check this
05:09
<@ToxicFrog>
Rawlogging activated, try again
05:09
<@Consul>
I specifically told xchat the range I set in the router.
05:11
<@Consul>
Do I need to set a host port?
05:11
<@Consul>
I tried it both ways, and it didn't seem to help.
05:12
<@ToxicFrog>
Your DCC SEND packet actually looks very confusing
05:12
<@Consul>
I just set my firewall rule to 8010-8020
05:12
<@Consul>
host port 8010
05:13
<@ToxicFrog>
>> :Consul!~Consul__@Nightstar-13285.dsl.sfldmi.ameritech.net PRIVMSG ToxicFrog :DCC SEND "haruki.jpg" 199 0 41732 24
05:13
<@ToxicFrog>
<< PRIVMSG Consul :DCC RESUME haruki.jpg 0 5120 24
05:13
<@ToxicFrog>
>> :Consul!~Consul__@Nightstar-13285.dsl.sfldmi.ameritech.net PRIVMSG ToxicFrog :DCC ACCEPT haruki.jpg 0 5120 24
05:13
<@ToxicFrog>
<< PRIVMSG Consul :DCC SEND haruki.jpg 1275758210 8010 41732 24
05:13
<@SmithKurosaki>
What does that all mean>
05:13
<@ToxicFrog>
Among other things, your client seems to be sending 0.0.0.199 as the IP address and 0 as the portnumber
05:14
<@Consul>
Si even telling my router to match your port range, it doesn't work.
05:14
<@Consul>
Let me restart xchat
05:14 Consul [~Consul__@Nightstar-13285.dsl.sfldmi.ameritech.net] has quit [Quit: Leaving]
05:14
<@ToxicFrog>
Mine counteroffers with 67.38.2.9 and port 8010, although where it gets those from I don't know
05:14 Consul [~Consul__@Nightstar-13285.dsl.sfldmi.ameritech.net] has joined #code
05:14 mode/#code [+o Consul] by ChanServ
05:14
<@SmithKurosaki>
hihi
05:15
<@Consul>
For some reason, xchat is ignoring what settings I tell it to use.
05:15
<@Consul>
Crao.
05:15
<@Consul>
Err, Crap
05:15
<@ToxicFrog>
It's forgotten those settings?
05:16
<@ToxicFrog>
Or it has them, but doesn't appear to be respecting them?
05:16
<@Consul>
It doesn't seem to be respecting them.
05:16
<@Consul>
Could be a bug of xchat on Windows.
05:17
<@ToxicFrog>
As far as I can tell from the rawlog, here is what happens:
05:17
<@Consul>
It's just weird how you can get 1 packet from me each time, then get dropped.
05:17
<@ToxicFrog>
- you offer a file but specify an invalid IP and port
05:17
<@ToxicFrog>
- I ask to resume from where it left off last time
05:17
<@ToxicFrog>
- you say that's cool
05:18
<@ToxicFrog>
...oh, hang on, I think I see what might be happening
05:18
<@ToxicFrog>
Or at least, how this is working
05:18
<@ToxicFrog>
It looks like you offer an invalid IP and port, and my client makes a "connect to me instead" counteroffer with my IP and port
05:18
<@ToxicFrog>
Which works for one packet and then drops
05:18
<@ToxicFrog>
Let me try sending you something to make sure the problem isn't on my end
05:19
<@ToxicFrog>
Huh.
05:19
<@Consul>
Try it again...
05:20
<@Consul>
Yeah, I didn't tell it a real directory the first time.
05:21
<@Consul>
I think xchat on Win is just buggy.
05:21
<@ToxicFrog>
Could be.
05:21
<@ToxicFrog>
It could also be that I left Ethereal running, so try it again from your end
05:21
<@Consul>
I quite specifically told it the port range to use, and to grab my IP from the server. It just doesn't seem to care what I tell it.
05:22
<@ToxicFrog>
Try disabling get-ip-from-server and entering your real IP
05:23
<@Consul>
You'll have the file eventually...
05:24
<@ToxicFrog>
That seemed to work.
05:24
<@Consul>
Not from my end?
05:24
<@ToxicFrog>
So, it's not dcc in general that's buggy; it's get-ip-from-server.
05:24
<@Consul>
err, end.
05:24
<@ToxicFrog>
...oh, right, I was misreading it.
05:25
<@ToxicFrog>
Yeah, that didn't work.
05:25
<@ToxicFrog>
Sigh.
05:25
<@Consul>
The sad part is, every single Windows IRC client sucks hard.
05:25
<@Consul>
This xchat for Windows is the only one I like.
05:25
<@Consul>
As buggy as it is.
05:26
<@ToxicFrog>
Yeah.
05:26
<@ToxicFrog>
Which build are you using, anyways?
05:27
<@Consul>
Every single one I've tried takes up way too much screen real estate, or handles multiple networks poorly. mIRC is just made of fail all around, in my opinion.
05:27
<@Consul>
And since DCC is a rarely-used feature, guess what that means?
05:28
<@ToxicFrog>
Yeaaah.
05:29
<@ToxicFrog>
That said, may be worth trying DCC in a different IRC client to help determine whether the problem is xchat itself, or your network.
05:30
<@Consul>
Well, at least I wasn't bored the last half-hour. Thanks for the help.
05:32
<@SmithKurosaki>
I am bored. I am sad because I am bored. I am also sick
05:33
<@Vornicus>
Design a video game!
05:33
<@Consul>
I really want to go down to the basement and rearrange so I can finally put the vapor barrier down.
05:34
<@SmithKurosaki>
I am working on PE, but I can't really do anything that requires higher brain function atm
05:34
<@Vornicus>
PE?
05:34
<@SmithKurosaki>
Project Euler
05:34
<@Vornicus>
Aha
05:34
<@Vornicus>
we indeed have a channel specifically for that: #projecteuler
05:34 Doctor_Nick [~nick@Nightstar-14116.tampfl.fios.verizon.net] has quit [Client exited]
05:35
<@SmithKurosaki>
So things like coding and making complicated/reasonable mafia posts are not available atm
05:35
<@Vornicus>
It's been quiet lately because nobody's been working on any.
05:35
<@ToxicFrog>
I generally just burble about it in here
05:35
<@ToxicFrog>
SK: catch up on your watching-of-things?
05:36
<@Consul>
I've been busy trying to figure out the coefficients to a set of FIR filters.
05:36
<@SmithKurosaki>
I don't have multiple computers to do that with atm
05:36
<@Consul>
Though not right at the moment.
05:42
<@Consul>
Man, I can't wait until I'm coding neural networks in order to calculate coefficients for 32-pole IIR filters! *eyeroll*
05:43
<@SmithKurosaki>
Well, I had a laptop and my dtop. Both laptops have dies
05:43
<@SmithKurosaki>
*Died
05:46
<@Consul>
Yay, numpy and scipy!
05:48
<@SmithKurosaki>
?? Night, though
05:49
<@Vornicus>
Numpy and Scipy are numeric and scientific libraries for Python.
05:49
<@Consul>
Night, SmithKurosaki
05:49
<@Consul>
Or was that a goodnight?
05:49
<@Consul>
I'm confused.
05:49
<@Consul>
Which way is up?
06:05
<@Consul>
Bedtime. Night, all!
07:22 ErikMesoy [~erikmesoy@Nightstar-469.bb.online.no] has joined #code
07:23 Thaqui [~Thaqui@121.98.166.ns-22683] has joined #code
07:23 mode/#code [+o Thaqui] by ChanServ
07:25
< ErikMesoy>
How, if at all, can I view the directory structure (or page list, or whatever the name is) of a public website from something else than index.html, which in this case is a redirect?
09:11 ErikMesoy [~erikmesoy@Nightstar-469.bb.online.no] has quit [Ping Timeout]
09:49 You're now known as TheWatcher
10:04 AnnoDomini [AnnoDomini@Nightstar-29371.neoplus.adsl.tpnet.pl] has joined #Code
10:04 mode/#code [+o AnnoDomini] by ChanServ
10:45 Rhamphoryncus [~rhamph@Nightstar-7168.ed.shawcable.net] has quit [Quit: Rhamphoryncus]
11:14 Attilla [~The.Attil@92.10.161.ns-3869] has quit [Quit: <Insert Humorous and/or serious exit message here>]
11:28 Attilla [~The.Attil@92.9.39.ns-26488] has joined #code
11:28 mode/#code [+o Attilla] by ChanServ
12:06 You're now known as TheWatcher[afk]
13:12 ToxicFrog [~ToxicFrog@Admin.Nightstar.Net] has quit [Operation timed out]
14:22 Thaqui [~Thaqui@121.98.166.ns-22683] has quit [Client exited]
14:27 Tarinaky [~Tarinaky@Nightstar-16638.plus.com] has joined #code
16:00 TF [~ben@Nightstar-11353.customer.sentex.ca] has joined #code
16:09 Tarinaky [~Tarinaky@Nightstar-16638.plus.com] has quit [Ping Timeout]
16:12 Tarinaky [~Tarinaky@Nightstar-16638.plus.com] has joined #code
17:10 ToxicFrog [~ToxicFrog@Admin.Nightstar.Net] has joined #code
17:10 mode/#code [+o ToxicFrog] by ChanServ
17:44 TF [~ben@Nightstar-11353.customer.sentex.ca] has quit [Quit: Switching clients.]
17:45 AnnoDomini [AnnoDomini@Nightstar-29371.neoplus.adsl.tpnet.pl] has quit [Ping Timeout]
17:51 AnnoDomini [AnnoDomini@Nightstar-27819.neoplus.adsl.tpnet.pl] has joined #Code
17:51 mode/#code [+o AnnoDomini] by ChanServ
18:04 You're now known as TheWatcher
18:15 Rhamphoryncus [~rhamph@Nightstar-7168.ed.shawcable.net] has joined #code
18:41 Thaqui [~Thaqui@121.98.166.ns-22683] has joined #code
18:41 mode/#code [+o Thaqui] by ChanServ
20:25 Netsplit DeepThought.NY.US.Nightstar.Net <-> Blargh.CA.US.Nightstar.Net quits: simontwo, crem, @Consul, @Thaqui
20:25 Tarinaky [~Tarinaky@Nightstar-16638.plus.com] has quit [Connection reset by peer]
20:25 Tarinaky [~Tarinaky@Nightstar-16638.plus.com] has joined #code
20:31 Netsplit over, joins: simontwo
20:31 Netsplit over, joins: crem, Consul, Thaqui
20:31 mode/#code [+o Consul] by ChanServ
20:31 mode/#code [+o Thaqui] by ChanServ
20:32 Netsplit DeepThought.NY.US.Nightstar.Net <-> Blargh.CA.US.Nightstar.Net quits: simontwo, crem, @Consul, @Thaqui
20:55 Netsplit over, joins: simontwo, crem, Consul
20:55 Netsplit over, joins: Thaqui
20:55 mode/#code [+o Consul] by ChanServ
20:55 mode/#code [+o Thaqui] by ChanServ
20:56 Netsplit DeepThought.NY.US.Nightstar.Net <-> Blargh.CA.US.Nightstar.Net quits: simontwo, crem, @Consul, @Thaqui
21:05 GeekSoldier [~Rob@Nightstar-8573.midstate.ip.cablemo.net] has joined #code
21:05 mode/#code [+o GeekSoldier] by ChanServ
21:06 Netsplit over, joins: simontwo, crem, Consul, Thaqui
21:06 mode/#code [+o Consul] by ChanServ
21:06 mode/#code [+o Thaqui] by ChanServ
22:51 Thaqui [~Thaqui@121.98.166.ns-22683] has quit [Quit: This computer has gone to sleep]
23:35 You're now known as TheWatcher[T-2]
23:37 You're now known as TheWatcher[zZzZ]
--- Log closed Sun Jul 12 00:00:52 2009
code logs -> 2009 -> Sat, 11 Jul 2009< code.20090710.log - code.20090712.log >