[00:10] *** mnathani_ has joined #arpnetworks [02:13] *** mnathani_ has quit IRC () [02:50] @weather akl [02:50] Auckland International, New Zealand: Clear 41°F (5°C), Humidity: 87%, Wind: From the North at 4 MPH -- For more details including the forecast and almanac, see http://www.wunderground.com/cgi-bin/findweather/getForecast?query=-37.00805664,174.79167175 or re-request this with: @weather -v akl [03:08] http://www.theregister.co.uk/2015/06/30/windows_10_wi_fi_sense/ [03:08] Title: "UH OH: Windows 10 will share your Wi-Fi key with your friends' friends • The Register" [04:09] android does too [04:09] at least, via NFC [04:09] i have to giggle at this router consituting IPv6 ready in the stock firmware [04:10] sure, you can give LAN interfaces an IPv6, and ping it and access it's webui.. but it doesnt talk IP6CP or so RA or the like [04:12] grody: The Windows 10 thing is a lot more special than that. It sends your wireless passwords to MS, who then load it into the phones/laptops of all your Facebook friends so they can use the same wifi [04:13] eeek [04:13] i know googles stores wifi passwords and restores them when you link a new phone to your account [04:14] but sharing like that != good [04:14] i have a dedicated wifi for friends and guests [04:14] they can keep their crappy devices isolated away from mine [04:15] And the (only?) way to prevent MS doing this for your wifi is to rename your SSID [04:16] i know with Google if you don't want them to map your wifi for location, you have to add _nomap to the end of your SSID [04:17] i can see that getting m$ in a lot of trouble here [04:17] Google got in shit just for technically wardriving [04:18] grody: So if you let one guest with a Windows 10 device use your wifi, you are also automatically allowing their mum, their colleagues and their crazy ex-girlfriend to connect to your network too. [04:18] yea thats not cool [04:18] also potentially illegal over here [04:19] *** rendrag has quit IRC (Ping timeout: 246 seconds) [04:25] plett, yea.. microsoft sharing wifi passwords of private wireless networks will get blasted [04:26] I'm not sure. The news stories about it are almost two weeks old now and there doesn't seem to be any outrage [04:26] imagine that one person is a known pest, he talks his way into getting guest access - you dont track your guests as you trust them, that guest just shared your wifi password to a cell of sorts [04:27] probably because people don't see the downside to such a feature [04:29] "Microsoft also adds that Wi-Fi Sense will only provide internet access, and block connections to other things on the wireless LAN:" [04:29] sure, right, ok [04:30] grody: pretty fucking gross [04:30] i had to read that twice as i didn't believe what i was actually reading [04:30] i don't sign into windows 10 with msn [04:31] i used some obscure email login for windows 10 [04:32] nobody would have that contact :> [04:36] hmm, is hardware NAT switch based NAT or something? [04:36] surely that == bad [04:37] yeh it's on the switch [04:37] it's got hooks into iptables somehow [05:01] crap i hate this rebuilding the edge thing [05:01] i never realised that the simplicity of border routing was so bloody stupidly complex [05:01] * grody curses himself for wanting to minimize hardware use [05:02] didn't realise my PPPoE router is also a smart switch too [06:17] *** rendrag has joined #arpnetworks [07:49] re: wi-fi sense, it's off by default and you have to enable it and then actively allow it to share stuff. otherwise, it does nothing. [07:49] stupid feature for a PC regardless, but also not a big deal if you don't actually use it. [08:29] tbh, if you want to steal wifi passwords.. work for google [08:30] you have to opt into it [08:30] so you consent [08:30] if you don't want it, don't enable it. full stop. [08:30] kneejerk stuff like that makes my head hurt. it exists as a feature for people who want it. if you don't, don't use it. not hard. [08:45] still.. i can see so many ways that could be (ab)used [08:47] although on a good note, openwrt is working this router pretty well [08:47] that's good [08:47] wifi performance is questionable, as always :/ [08:48] if only build dd-wrt was as simple [08:50] i haven't used dd-wrt for a long time. found that they let some business customer customizations into their codebase in the form of hardcoded firewall rules and management logins. tried reporting it to them responsibly, they never replied. reported it on their forums and got banned [08:50] this was 5-6 yrs ago [08:52] hah [08:52] and their tendency to mark every device they could as "supported", even if that meant that radio performance was 5% of what it should be, or that it crashes or whatever [08:52] public disclosure usually changes attitude [08:52] yea, they didn't fix it for almost 3 months [08:52] someone else reported it later and was also banned, but they fixed it shortly after [08:53] their attitude was "so some stuff from a customer got in our code base. big deal. shit happens" etc [08:54] plett, why don't A&A just use openwrt as a codebase for basic shipped routers and something like this n600 [08:55] Because it would be impossible to support [08:55] aww :( [08:56] just had to flip my hilink into serial mode to utilize the 3G modem (the horrid USB ethernet NATs) [08:56] Any specific device that exists now and supports openwrt won't be available in a year's time, so we would have dozens of different hardware devices which we need to make work [08:56] true [08:57] that doesn't sound fun [08:57] tbh.. this thing i can see being unreplaced for some time [08:57] those technicolors are just horrid [08:57] And reflashing it will instantly void any support we get from the manufacturer [08:57] ugh, i've heard about technicolor router/modem things [08:58] awww noo [08:58] im gonna lose my 100% connection uptime so far for july [08:58] PPP session has been rocking for 16 days now :( [08:58] doh [08:59] The technicolors work fine for their intended purpose - which is ISP managed devices. They are quite horrible if the end user is trying to set them up manually, so don't do that [08:59] i did notice in the tplink default firmware after update, it actually offered SLAAC and DHCPv6 for LAN and WAN [09:00] the cellular cantenna + router technicolor stuff sounded pretty bad [09:00] it seemed to work on the LAN front.. no idea if it'd so PPP IP6CP [09:00] or RFC4638 [09:00] the two devices, one nats the other andfor a long time would crash if you passed any sort of IPSEC (iirc) through it [09:01] there was a long-running thread about that specific set of devices on verizon wireless' site for almost a year before it finally got patched [09:01] technicolors are probably the most common ISP chucked routers here too [09:01] ah [09:01] although BT and Virgin have some "super" hub efforts [09:01] i had no idea they made that sort of equipment til my friend ended up w/something from verizon wireless [09:02] im mostly tp-link for embedded here [09:02] low cost, good quality [09:03] they use arris (motorola) a lot w/cable here [09:03] and uhh, actiontec i think w/dsl in my market [09:03] broadcom is very common here [09:03] but haewei and alcatel iirc is getting back in [09:05] hmmm [09:05] im second guessing putting 3G failover on the open [09:05] thinking i should keep it on the pfsense [09:05] That's what she said!! [09:05] no, she seriously didn't [09:05] especially after what i bought on ebay last night [09:07] crap, cant find the link now.. basically an older duo 2 2.2GHz dual core effort 2/ 2GB RAM and a 32GB SSD and dual 1Gbit intel pro NIC [09:07] mini ITX style too [09:26] BryceBot: no [09:26] Oh, okay... I'm sorry. 'thinking i should keep it on the pfsense' [09:42] *** easymac has quit IRC (Remote host closed the connection) [09:43] *** easymac has joined #arpnetworks [10:14] hmm, i seem to have cut short on needs on building openwrt for this thing [10:14] so used to 4M flash [10:14] added just about everything i'd thought i'd need, and my flash file is only 5.7MB big [10:15] might just have to see if this enough space to play with freifunk [15:11] 4M flash is really bloody annoying [15:12] did you add vim, tcpdump etc? [15:12] i wonder if there's something inbetween vim and busybox vi. i can't use busybox vi :) [15:18] Pfft who really needs vi? All I need is cat :p (Sure, it's inconvenient... but it works.) [15:22] the firewall config [15:22] grody: sounds ideal.. for hardware [15:22] well nearly ideal, i prefer i3ish as they use less power [15:22] which often translates to lower noise [15:23] i'd like to see them having 2+gb of flash myself :) [15:23] and using a much more full system [15:42] i erm squeezed in *cough*nano*cough* [15:43] tcpdump seems small enough to fit into the 4M flash - depends how you build [15:44] ive gotten quite skilled at building a complete enough openwrt with limited space [15:53] *** dj_goku has quit IRC (Read error: Connection reset by peer) [15:56] *** easymac has quit IRC (Ping timeout: 276 seconds) [15:56] *** easymac has joined #arpnetworks [15:56] *** easymac has quit IRC (Changing host) [15:56] *** easymac has joined #arpnetworks [15:59] *** dj_goku has joined #arpnetworks [15:59] *** dj_goku has quit IRC (Changing host) [15:59] *** dj_goku has joined #arpnetworks [16:23] hrm [16:24] i wonder if i can blag extra data on this typo [16:29] went to apply for a 1GB 3G service, and it states "This bundle will give you 10240MB of allowance" [16:39] heh [16:39] yeh [16:39] they should honour it :)) [16:40] yeah i got tcpdump and vim into 4mb i think [16:40] d-link adsl modem [16:40] but couldn't do anything else :/ [16:40] i hate how you can't upgrade withotu rebuild with limited flash [19:47] *** relrod has quit IRC (Ping timeout: 256 seconds)