| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
| Who | What | When |
|---|---|---|
| *** | fink has quit IRC (Quit: fink) | [00:14] |
| ............................... (idle for 2h30mn) | ||
| fink has joined #arpnetworks | [02:44] | |
| schmir has joined #arpnetworks
ziyourenxiang has joined #arpnetworks | [02:56] | |
| .......... (idle for 48mn) | ||
| fink has quit IRC (Quit: fink) | [03:45] | |
| ..... (idle for 22mn) | ||
| ziyourenxiang has quit IRC (Quit: ziyourenxiang) | [04:07] | |
| ziyourenxiang has joined #arpnetworks | [04:21] | |
| .......... (idle for 45mn) | ||
| schmir has quit IRC (Remote host closed the connection) | [05:06] | |
| ....... (idle for 30mn) | ||
| schmir has joined #arpnetworks | [05:36] | |
| ....................... (idle for 1h52mn) | ||
| nesta has joined #arpnetworks | [07:28] | |
| ...... (idle for 25mn) | ||
| ziyourenxiang has quit IRC (Quit: ziyourenxiang) | [07:53] | |
| bob^^ has quit IRC (Ping timeout: 264 seconds) | [08:04] | |
| ....... (idle for 33mn) | ||
| schmir has quit IRC (*.net *.split)
bsdguy has quit IRC (*.net *.split) shatt has quit IRC (*.net *.split) koan has quit IRC (*.net *.split) schmir has joined #arpnetworks bsdguy has joined #arpnetworks shatt has joined #arpnetworks koan has joined #arpnetworks | [08:37] | |
| ..... (idle for 23mn) | ||
| bob^^ has joined #arpnetworks | [09:02] | |
| heavysixer has quit IRC (Quit: heavysixer)
robotarmy has joined #arpnetworks | [09:12] | |
| ..... (idle for 20mn) | ||
| heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer | [09:35] | |
| .... (idle for 16mn) | ||
| cubelogic has joined #arpnetworks | [09:51] | |
| ........ (idle for 38mn) | ||
| schmir has quit IRC (Remote host closed the connection)
heavysixer has quit IRC (Quit: heavysixer) | [10:29] | |
| ...... (idle for 28mn) | ||
| heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer | [11:00] | |
| bharatak has joined #arpnetworks | [11:13] | |
| ..... (idle for 24mn) | ||
| bharatak | ipv6 - so i configured my firewall to let inet6 in, i can see the system listening on tcp6, i verified from another host that ipv6 works, did i miss anything?
I need to add AAAA records and watch the logs | [11:37] |
| jpalmer | well, we can't really answer that until you let us know what you expected to happen, and what actually happened?
depending on the context, you may need to configure applications or services to USE that IPv6. | [11:38] |
| bharatak | ha - i'll just give it a go, basically web/email
i can see the ports listening.. i'll just go for it | [11:39] |
| jdoe | jpalmer: (delayed response) fair enough, I'm assuming that if you control the primary you control the secondary as well, and wouldn't do something as silly as to have them running different software.
otherwise it's your own fault, you know? ;) (re: backup mxes) | [11:41] |
| jpalmer | jdoe: poor assumption ;) years ago it was common practice to contract with another entity. many places essentially traded bacup MX services. | [11:42] |
| jdoe | then they get everything that's coming to them.
I guess what I'm saying is it's as easy or as troublesome as you make it :P | [11:43] |
| jpalmer | in this day and age, there are very few *good* reasons to run a secondary MX | [11:43] |
| jdoe | and yet they're exactly the same as they ever were...
load balancing, redundancy/availabiilty, ... | [11:45] |
| jpalmer | yep all things I've heard before, and believed for a long time. | [11:46] |
| bharatak | ah - my dns provider is having troubles - no creating AAAA record for me :( | [11:47] |
| jpalmer | believe me, I spent a long time defending the "backup MX" theory. arguing exactly the same things you are now. it took a while before I realized that those reasons are bogus, and not "good" | [11:47] |
| bharatak | i've noticed that while my primary mx is up i just get spam from the backup | [11:48] |
| jpalmer | in the days of multi-homed connections, BGP announcements, hardware load balancing, and proper mail clusters.. the above ideas are simply.. excuses.
bharatak: which dns provider? | [11:49] |
| bharatak | zoneedit | [11:50] |
| jpalmer | bharatak: ahh, I used them a while back, they are decent enough. | [11:50] |
| bharatak | multi-homed connections, bgp are great- but overkill for my small needs (5 mailboxes) | [11:51] |
| jpalmer | I currently use he.net's free dns service.. but zoneedit wasn't too bad. never saw an issue where I couldn't update records. might be a fluke. | [11:51] |
| bharatak | well - i guess a vps at arpnetworks is also overkill - but hell it's fun
they are migrating their front end - seems others are also having trouble logging in. new web-app | [11:51] |
| jdoe | jpalmer: lol. explain to me how a mail cluster is significantly different from multiple mx records... | [11:52] |
| jpalmer | bharatak: sure. but with 5 users, a backup MX is also probably overkill. RFC compliant mailservers will retry if your MX is down temporarily. so you don't lose anything | [11:52] |
| jdoe | jpalmer: bonus points if you can explain how it cuts down on maintenance in any way ;)
jpalmer: no, but your primary may remain down for some time. | [11:52] |
| bharatak | i should check out he.net, I'm thinking of getting a ipv6 tunnel for my cable modem anyway | [11:52] |
| jdoe | jpalmer: suppose I was on that arp box that was getting ddosed
jpalmer: or if hardware failed who knows how long I might be down? | [11:52] |
| jpalmer | jdoe: I think you started this conversation (again) after I explained how it can potentially reduce maintenance. I'm not much interested in circular discussions | [11:53] |
| jdoe | if you did I wasn't part of the conversation, I joined because I saw "backup mx = bad" | [11:53] |
| jpalmer | you even commented on the backup MX having the same software. so, I know you saw it. | [11:53] |
| jdoe | er, I said there was no significant problem with maintaining a backup mx.
... because the software is (assuming you're not a glutton for punishment) the same. | [11:54] |
| jpalmer | and I maintain that such an assumption cannot be made globally.
here is the bottom line. if you want a backup MX, use it. it makes no difference to me. I maintain that there are very few practical and real-world reasons to actually do so. So, *I* will not run a backup MX. | [11:55] |
| jdoe | yeah but you're saying "don't use a backup mx, use this alternative method which is functionally equivalent"
and that makes no sense. you don't get to say "YOU MIGHT NOT BE RUNNING THE SAME MTA ON THE BACKUP" if your proposed solution involves setting up a cluster running whatever you want. | [11:56] |
| jpalmer | what alternative did I say to use instead? please, feel free to put words in my mouth. | [11:57] |
| jdoe | you're the one suggesting a cluster, bgp etc.
sorry, this is getting antagonistic. Ignore me. | [11:57] |
| jpalmer | "in the days of" is by no means my telling you to use those technologies. I feel that you might be trying to skew a conversation to "win" when no such claim was made. | [11:58] |
| jdoe | I feel you might be doing the same when there's a clear implication by "in the days of" that you are suggesting they make an alternative (whether you personally use them or not) | [11:59] |
| jpalmer | we'll have to agree to disagree. use them if you want. I won't. I see almost no point in them. | [12:01] |
| jdoe | sounds good. | [12:02] |
| ......... (idle for 40mn) | ||
| *** | lucky has quit IRC (Read error: Connection reset by peer)
lucky has joined #arpnetworks | [12:42] |
| .................................................. (idle for 4h8mn) | ||
| robotarmy has quit IRC (Remote host closed the connection) | [16:50] | |
| whitefang | LS | [16:52] |
| anyone else having network issues with their VPS? | [17:03] | |
| jpalmer | whitefang: not I | [17:03] |
| whitefang | I'm getting a good 60+ms higher latency to it than I normally do. | [17:04] |
| jpalmer | maybe your host is experiencing high traffic flow for some reason? | [17:04] |
| whitefang | latency to everywhere else from where I am is normal | [17:04] |
| vcs | nope
all normal here odd, what VPS are you on | [17:07] |
| *** | vcs has quit IRC (Read error: Operation timed out)
vcs has joined #arpnetworks | [17:10] |
| vcs | think there was just a route hiccup
not sure | [17:12] |
| *** | DDevine has joined #arpnetworks | [17:13] |
| whitefang | kvm14 | [17:15] |
| vcs | im on 13
didn't notice anything till that routing hiccup | [17:20] |
| jpalmer | I'm on 13 as well.
I didn't have a routing hiccup | [17:20] |
| vcs | hmmm
maybe i have my config messed up somewhere vcs needs to dig lol | [17:20] |
| jpalmer | I'd say, if it only happened once, I wouldn't worry about it too much | [17:21] |
| vcs | well, it looked like em0 threw an error
maybe virtual hardware issue specific to OpenBSD i just upgraded to 4.8 might have something to do with it | [17:21] |
| whitefang | I think my ISP may be taking a bit of a dump. | [17:26] |
| vcs | same here actually | [17:27] |
| whitefang | although it looks like it might just be the route from here to my VPS.
I think its PCCW Global that's taking the dumb dump | [17:27] |
| vcs | lol | [17:31] |
| whitefang | ping -t ge2-5.br01.sea01.pccwbtn.net
dropping packets like crazy | [17:32] |
| jpalmer | well, to be fair. many routers put icmp in a lowwer priority queue, and will drop them when the traffic load gets high. it's not *necesarily* indicitive of a problem. (though, it's certainly suspect) | [17:33] |
| vcs | ping -t ge2-5.br01.sea01.pccwbtn.net
errr | [17:33] |
| whitefang | errr | [17:33] |
| vcs | i cant even resolve that host
lol | [17:33] |
| whitefang | 63.216.14.157
is the IP | [17:33] |
| vcs | if that means anything | [17:33] |
| whitefang | but that's the host between me and my VPS that's adding like 70ms latency more than usual; | [17:34] |
| vcs | im getting between 80-300MS | [17:34] |
| whitefang | normally I'm like 40ms away from my VPS
now I'm like 120ms with 600ms spikes | [17:34] |
| vcs | yeah
im seeing that pinging you from my home connection and arp networks so i dont think its a problem with arp | [17:34] |
| whitefang | well 63.216.14.157 is the router that's adding the delay
Ping statistics for 63.216.14.157: Packets: Sent = 259, Received = 241, Lost = 18 (6% loss), Approximate round trip times in milli-seconds: Minimum = 85ms, Maximum = 372ms, Average = 94ms that address is usually like 10ms from me at most and packet loss even prioritizing ICMP lower is no excuse for 6% loss | [17:35] |
| vcs | yeah | [17:38] |
| *** | islandfo1 is now known as islandfox | [17:46] |
| .... (idle for 16mn) | ||
| cubelogic has quit IRC (Remote host closed the connection) | [18:02] | |
| ..... (idle for 24mn) | ||
| ziyourenxiang has joined #arpnetworks | [18:26] | |
| ............. (idle for 1h4mn) | ||
| robotarmy has joined #arpnetworks
ziyourenxiang has quit IRC (Quit: ziyourenxiang) | [19:30] | |
| .......................... (idle for 2h5mn) | ||
| robotarmy has quit IRC (Remote host closed the connection) | [21:38] | |
| ........ (idle for 39mn) | ||
| robotarmy has joined #arpnetworks | [22:17] | |
| .... (idle for 15mn) | ||
| heavysixer has quit IRC (Ping timeout: 240 seconds) | [22:32] | |
| ................. (idle for 1h24mn) | ||
| DDevine has quit IRC (Remote host closed the connection) | [23:56] | |
| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |