IRC log for #gllug on 20110315

00:21.34*** join/#gllug MessedUpHare (~stewart@cpc8-acto3-2-0-cust6.4-2.cable.virginmedia.com)
02:38.33*** join/#gllug sabinef72 (~sabinef72@sabinef72.ipv6.popipo.fr)
02:42.54*** join/#gllug Leeds (~richardc@www.scorefive.com)
03:31.22*** join/#gllug sabinef72 (~sabinef72@ns.popipo.fr)
03:53.23*** join/#gllug Azundris (callisto@tatiana.azundris.com)
09:01.37*** join/#gllug PcSett (~Don@host81-159-128-230.range81-159.btcentralplus.com)
09:21.17boudiccasBeware the Ides of March!
09:22.31morsingSo, www.tickets.london2012.com has no IPv6 addresses...
09:33.12wethrinNo, most places still don't
09:39.30morsingI am aware, but it's seriously disappointing, especially after the Chinese Olympics IPv6 success
09:39.53morsingAnd "most places" = 99.997%
09:40.28morsingAnd bear in mind that IPv4 address space will actually run out before the Olympic games start...
09:44.16halisort of
09:44.28halii just put in a RIPE application for some space
09:44.50haliits harder than it used to be but they still have a fair amount of spare space for "real" business use
09:45.55morsinghali: Yes, let's squeeze the last bit out of a dying standard instead of planning for the future... Have worked since 1200 BC
09:47.03haliwe've had IPv6 space and IPv6 peering enabled for about 2 years now
09:47.09haliNONE of our clients does
09:47.13haliso it's pretty pointless so far
09:47.42halibut it's there if they want it
09:48.02halii think most of our ISPs have had it for 5+ years ... close to no traffic though
09:48.04morsingI'm not saying it's your fault - the ISPs need to be the main drive behind it and it doesn't help that consumer routers don't do IPv6
09:48.21halii agree with you, it's an impeding problem
09:48.30halidid you read the customer router ipv6 study?
09:48.37morsingNo?
09:48.41halidone by ARIN or someone like that
09:48.54halithey tested loads of home routers and something like 5% passed their tests
09:49.13halianother good example is MacOS X .. even the new lion version doesn't have full ipv6 dhcpd support
09:49.20halidhcpcd*
09:49.27morsingDebian is actually pretty crap at IPv6
09:49.42morsingIPv6 shouldn't use DHCP anyway
09:49.53morsingThat's what router advertiments are for
09:51.24morsingOut of our Ricoh printer, X-box, Wii, PS3 and D-link print server, guess how many supports IPv6?
09:52.46morsingMy laptop and our PC at home is on IPv6 but I can't disable IPv4 because traffic that doesn't go through the proxy can't be translated.
09:59.09*** join/#gllug zooz (~zooz@host86-163-12-128.range86-163.btcentralplus.com)
10:25.58antiphaseRA is horseshit
10:26.14antiphasewhich is why DHCPv6 is happening
10:41.12*** join/#gllug flips_and_rails (~stu@2001:630:12:1058:218:feff:fe6a:be1b)
10:53.01*** join/#gllug Nafallo_ (~nafallo@ubuntu/member/nafallo)
11:29.35jpdsmorsing: Blame Akamai anyway.
11:41.19Copeis going to the 'Move Over IPv4' party next week
11:43.45morsingCope: The one which website isn't on IPv6?
11:44.08Copewhy would you expect eventbrite to be on IPv6?
11:44.15Copeyou are a wanker sometimes, morsing
11:44.26morsing?
11:47.02Copesorry, morsing
11:47.07Copeun-called-for
11:47.11Copehttp://bringonipv6.com/
11:47.13morsing'tis ok. Beer?
11:47.15Copeis what you mean
11:47.17Copeisn't it
11:47.21morsingOh, I see. Yes
11:47.48morsingWhat's Move over IPv4 then? And what's eventbrite?
11:48.11AndyMillarproblem is, ipv6 sucks
11:48.19Copeit's just an event about ipv4 / ipv6 stuff
11:48.31antiphasehttp://lmgtfy.com/?q=move+over+ipv4
11:48.50Copei don't know much about it, but a friend of mine is on the panel, so i'm going along too
11:49.32CopeI mean - I don't know much about IPv6 implementation, advantages, disadvantages etc
11:49.42Copeinterested to get some perspectives
11:50.16antiphaseIt's the same as IPv4 with more bits
11:50.37Coperolls eyes
11:51.09antiphaseThey added some more bells and whistles that are mostly no longer relevant because it's not 20 years ago any more
11:51.49antiphaseIt sounds flippant to compare them so glibly, but realistically the implementations will be very similar
11:51.58antiphasePeople like familiarity
11:52.03Copenods
11:53.51Copeis hungry
11:56.20morsingIPv6 is easier to implement and use but more difficult to remember the addresses unfortunately
12:00.49AndyMillarit also doesn't have NAT
12:00.52AndyMillarwhich is a pain
12:01.12antiphaseFail
12:01.18antiphaseNAT is for gaylords
12:01.26AndyMillarI don't want to put windows machines on the internet
12:01.31antiphaseUse a firewall then
12:01.35antiphaseNAT isn't a firewall
12:01.35AndyMillarespecially as rhel5/centos5 doesn't have conntracking working
12:02.58morsingNAT is nice sometimes... And it's annoying you can't do intercepting proxies with IPv6
12:04.37antiphaseThe only use for NAT is in alleviating address shortage, and it should DIAF
12:04.58antiphaseAnyone caught implementing NATv6 is likely to have their internet licence revoked
12:05.51antiphasewonders if he has made his point
12:05.57morsingantiphase: They need to implement some other form of prerouting then
12:06.06antiphaseWhat does that mean?
12:06.16*** join/#gllug Leeds (~richardc@pcd253019.netvigator.com)
12:06.17morsingTo support intercepting proxies
12:06.31antiphaseDo you mean transparent web proxying, for example?
12:06.43morsing? Yes...
12:06.55antiphaseI don't see why the situation would be any different with IPv6
12:07.03morsing?
12:07.06morsingTry it, then
12:07.15morsingIPv6 can't do it
12:07.25antiphasewtfs a bit
12:07.59antiphaseAre you suggesting that people with routable IPv4 addresses are currently unable to use transparent proxies?
12:08.05morsingNo
12:08.24morsingI'm saying IPv6 can't do it
12:08.31antiphaseOr that an HTTP proxy is unable to make a request on behalf of another machine for some reason
12:08.37morsing?
12:08.48morsingPREROUTING is essentially a NAT thing
12:08.53antiphaseYou also think that SLAAC is a good idea and that DHCPv6 shouldn't exist
12:08.53morsingSo not supported
12:09.10antiphasegives up
12:09.22morsingI understand it can be tricky to understand
12:09.31antiphaseEvidently
12:10.06wethrindon't see why you couldn't use a transparent proxy
12:10.47wethrinjust tell your router to redirect any requests from an appropriate set of IP addresses to your proxy
12:11.09wethrinsame way certain ISPs do proxying
12:11.12antiphaseTransparent proxying is usually done with policy routing in the network
12:11.34antiphaseIt's nothing to do with iptables NAT chains
12:12.15antiphasewonders how the crusty old AIX-using men would do it
12:12.31antiphaseSteam powered proxies!
12:13.31haliAIX has actually had decent ipv6 support since version 4.something :)
12:27.09AndyMillarantiphase: ok, given you seem to like the idea of bridging firewalling and all that jaz; fancy explaining why my stateful firewall doesn't work? :-p
12:32.14*** join/#gllug dick_turpin (~dick_turp@host217-34-163-30.in-addr.btopenworld.com)
12:32.27antiphaseYou need more cowbell
12:32.39dick_turpinRelease the hounds!
12:45.47*** join/#gllug gmarkall (~graham@dyn1214-109.wlan.ic.ac.uk)
12:51.54Copeuse pf, hth, hand
12:51.59wethrinyay for pf
12:52.32Copepf is very good indeed :)
12:53.12wethrinindeed
12:54.39antiphasepff
12:54.56Copeantiphase <3 ipchains
12:55.02AndyMillarok, given I'm running centos 5.6
12:55.18AndyMillarno, 5.5
12:55.30Coperun openbsd in a kvm?
12:55.46Copechuckles, sorry antiphase
12:55.47Copegah
12:55.48CopeAndyMillar:
12:56.44CopeI just wouldn't start from there... I prefer pf or even ipfilter to iptables, so I wouldn't build a firewall using linux
12:57.33wethrinindeed
12:57.48antiphaseI found pf horribly confusing on the single occasion I tried to use it about 5 years ago
12:57.54antiphaseiptables ftw
12:58.15wethrinI've found iptables/ipchains/ipOMGWTFBBQ to be horribly confusing
12:58.26Copei think pf has improved a lot; when I first used it... 7 years ago? whenever wethrin showed it to me... the docs were ropey
12:58.30Copethey're very good now
12:58.44Copeand the dsl (for want of a better word) is very clear
12:58.49wethrin7 years ago is probably about when they switched from ipf to pf
12:58.58Copenods at wethrin
12:59.29Copeanyway! none of this helps AndyMillar
12:59.34CopeAndyMillar: what's the actual problem?
12:59.42antiphaseiptables seems to win on account of the commands just being a set of conditions to match, rather than some weird language that implies things
12:59.50antiphaseI can't really say though because I know fuck all about pf :P
12:59.55Copenods at antiphase
13:00.09Copeyes - pf is a packet filtering DSL
13:01.47Copeiptables/netfilter is more like setting up a series of logic gates to achieve pseudo-stateful packet inspection into the linux kernel
13:01.57Copeif that makes sense
13:03.22Copepass log on $ext_if inet proto tcp from any to $loadbalancers port $webports keep state (max-src-conn 100, max-src-conn-rate 15/5, overload <abusive_hosts> flush)
13:03.40antiphasegoes blind
13:03.49Copetry doing that in iptables and making it readable
13:04.02antiphaseThat looks nearly as horrible as tc
13:05.01Copeyeah that's kinda long
13:05.03Copepass on $ext_if inet proto { udp tcp } from $ldap_allowed to $ldapservers port 389
13:05.03antiphaseI wonder if anyone has tried to write a converter
13:05.15wethrinYes.
13:05.20wethrinI don't think it worked wonderfully, though
13:05.53Copeplus carp and pfsync are just amazing
13:06.05Copegod only knows how you'd do that with iptables
13:06.28antiphaseMaybe no-one has ever needed to
13:06.49Copeno-one has ever needed to implement failover firewalls with an implementation of VRRP?
13:07.07Copeyes maybe thats' because no-one in their right mind would use iptables for serious firewalling?
13:07.10Cope</troll>
13:07.40antiphaseThere's always a difficult decision for people to make; by the time you really need proper networking stuff, it seems common for people to buy commercial solutions
13:07.49Copeyeah
13:08.13Copei actually started using pf properly becuase our not inexpensive cisco firewalls sucked balls
13:08.14antiphaseRather than rely on some crackpot system dreamt up by someone who subsequently leaves
13:08.43Copei've used and quite liked checkpoint ng
13:08.50Copebut that's just ipfilter really
13:09.04Copei've used juniper netscreens - they're great
13:09.10Copebut they're also ipf under the hood
13:09.26Copei've used ciscos and hated them
13:10.18Copebut pf was very cost effective, performed well, and could be nicely managed by puppet
13:14.02AndyMillarCope: problem: stateful ip6tables rules aren't matching, so I can't block unbound connections via ipv6
13:14.36CopeAndyMillar: you in the centos channel ever?
13:14.45AndyMillarsometimes
13:14.59AndyMillarwhat have I missed?
13:15.54CopePretty sure centosian said something about ip6tables and statefulness a month or two ago; he knows iptables really well, if you want to hit someone up who is likely to help rather than troll like me.
13:16.50Copez00dax: you remember? ...
13:22.17z00daxthere is/was a problem with state/ip6tables a while back in centos5
13:23.59antiphaseYou could use Debian instead :P
13:26.04*** join/#gllug dick_turpin (~dick_turp@host217-34-163-30.in-addr.btopenworld.com)
13:27.14z00dax:)
13:40.43AndyMillarz00dax: do you know if it's still a problem? :/
13:42.21Copez00dax: Isn't it just that netfiler in the available upstream kernels doesn't support stateful IPv6 firewalling?
13:43.08z00daxCope: yup
13:43.20z00daxchecks if 5.6 resolves this
13:51.03z00daxthere are a bunch of patches into the 5.6 kernel that might be relevant
13:51.10z00daxi dont have a machine to test on right now though
13:56.13AndyMillarhmm, I might have a play
14:13.47*** join/#gllug sabinef72 (~sabinef72@sabinef72.ipv6.popipo.fr)
14:19.59*** join/#gllug __marcus_ (~marcus@lenny.uk-debtcollection.com)
14:20.12*** join/#gllug cbz (chriseb@vortex.ukshells.co.uk)
14:37.19*** join/#gllug sabinef72 (~sabinef72@ns.popipo.fr)
17:21.29*** part/#gllug dick_turpin (~dick_turp@host217-34-163-30.in-addr.btopenworld.com)
18:42.12*** join/#gllug Hamzah (~mhamzahkh@genesis.home.hamzahkhan.com)
19:05.13*** join/#gllug Hamzah (~mhamzahkh@genesis.home.hamzahkhan.com)
19:05.46*** part/#gllug yaMatt (~yaMatt@li99-88.members.linode.com)
19:11.06*** join/#gllug Mohan (~nixh0st@unaffiliated/mohan)
19:17.10*** join/#gllug Mohan (~nixh0st@unaffiliated/mohan)
19:44.42*** join/#gllug Hamzah (~mhamzahkh@genesis.home.hamzahkhan.com)
19:45.55*** join/#gllug gmarkall (~graham@84.45.235.192)
20:30.30*** join/#gllug __marcus_ (~marcus@lenny.uk-debtcollection.com)
23:36.02*** join/#gllug Leeds (~richardc@pcd253019.netvigator.com)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.