#raspberrypi IRC Log

Index

IRC Log for 2014-02-14

Timestamps are in GMT/BST.

[18:29] -hobana.freenode.net- *** Looking up your hostname...
[18:29] -hobana.freenode.net- *** Checking Ident
[18:29] -hobana.freenode.net- *** Found your hostname
[18:29] -hobana.freenode.net- *** No Ident response
[18:29] -NickServ- This nickname is registered. Please choose a different nickname, or identify via /msg NickServ identify <password>.
[18:29] -NickServ- You have 30 seconds to identify to your nickname before it is changed.
[18:29] -NickServ- You are now identified for DataBot.
[18:29] -MemoServ- You have 2 new memos.
[18:29] -MemoServ- To read them, type /msg MemoServ READ NEW
[18:29] * RaspberryPiBot (~PircBot@unaffiliated/datagutt/bot/databot) has joined #raspberrypi
[18:29] * Topic is 'Unofficial RaspberryPi IRC channel but "Blessed" by the Foundation as the ONE channel. Logs @ http://srv.datagutt1.com <> Channel Rules: http://tiny.cc/h7za1w <> Getting help on IRC: http://tiny.cc/p9za1w <>'
[18:29] * Set by ShiftPlusOne!~Shift@unaffiliated/shiftplusone on Sun Aug 04 19:59:52 CEST 2013
[18:29] * JMichaelX (~james@unaffiliated/jmichaelx) has joined #raspberrypi
[18:31] * ABC-XYZ (~abc@unaffiliated/abc-xyz) has joined #raspberrypi
[18:32] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) has joined #raspberrypi
[18:33] * Moon_Man (~Moon_Man@76.9.195.46) has joined #raspberrypi
[18:34] * Moon_Man (~Moon_Man@76.9.195.46) Quit (Remote host closed the connection)
[18:38] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) Quit (Read error: Connection reset by peer)
[18:39] * trisi (~trisi@216-67-63-154-rb3.nwc.dsl.dynamic.acsalaska.net) Quit (Ping timeout: 272 seconds)
[18:41] * basti (~IceChat9@xdsl-89-0-158-13.netcologne.de) has joined #raspberrypi
[18:42] * trisi (~trisi@209-193-56-37-rb1.fai.dsl.dynamic.acsalaska.net) has joined #raspberrypi
[18:42] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) has joined #raspberrypi
[18:42] * _cheney (~cheney@nat.sierrabravo.net) Quit (Read error: Connection reset by peer)
[18:43] * _cheney (~cheney@nat.sierrabravo.net) has joined #raspberrypi
[18:44] * cjw-17 (~chris@24.222.73.6) Quit (Ping timeout: 272 seconds)
[18:47] * leucos (~leucos@erafw.erasme.org) Quit (Quit: Leaving.)
[18:47] <zipper> Hey guys I think I have it fixed.
[18:47] <zipper> Matt: ^
[18:47] <zipper> ShorTie: ^
[18:47] <zipper> Anyone?
[18:48] * GenBurnside (~GenBurnsi@12.150.118.194) has joined #raspberrypi
[18:48] <zipper> I have two partitions now
[18:48] <zipper> /dev/mmcblk0p1 90M 24M 66M 27% /run/media/urbanslug/2300-4E18
[18:48] <zipper> /dev/mmcblk0p5 1.7G 406M 1.2G 27% /run/media/urbanslug/b471cde8-2a15-44e7-acce-e9a2a54511a6
[18:48] <zipper> I assume the rest us unallocated
[18:48] <zipper> s/us/is
[18:48] <shiftplusone> looks right
[18:48] <zipper> shiftplusone: So uh
[18:48] <zipper> The whole
[18:48] * zoktar (~zoktar@unaffiliated/zoktar) Quit (Read error: Connection reset by peer)
[18:49] <zipper> < Matt> zipper: yeah, basically what we're gonna walk you through is editing the networking config files on the card to give your Pi a static IP address
[18:49] <Matt> ah, good stuff
[18:49] <zipper> shiftplusone: ^
[18:49] <Matt> /dev/mmcblk0p5 is the one you care care about here
[18:49] * GenBurnside (~GenBurnsi@12.150.118.194) Quit (Client Quit)
[18:49] <Matt> that's the one with your root filesystem for the pi
[18:49] * cumana (~koomahnah@unaffiliated/cumana) Quit (Ping timeout: 252 seconds)
[18:50] <zipper> I have cd-d into it
[18:50] <zipper> I am in it
[18:50] <zipper> You know what I mean
[18:50] <zipper> Yes it does seem to have all that should be in /
[18:51] * zoktar (~zoktar@unaffiliated/zoktar) has joined #raspberrypi
[18:51] * xCP23x (~xCP23x@2.25.249.168) Quit (Ping timeout: 245 seconds)
[18:52] <zipper> but whoever said that RPis should have HDMI should know that over billions of people in this planet are living in extreme poverty
[18:52] * basti (~IceChat9@xdsl-89-0-158-13.netcologne.de) Quit (Ping timeout: 245 seconds)
[18:52] <zipper> and I assume they were made to help these people
[18:52] <Matt> zipper: that's why it also does composite video out
[18:53] <shiftplusone> ^
[18:53] <Matt> that's what the rca phono connector is for
[18:53] <shiftplusone> HDMI is for us one percenters.
[18:53] <Matt> that should attach to pretty much any TV made in the last 20 years
[18:53] <zipper> shiftplusone: Well many people have HDMI
[18:53] <zipper> but I am not friends with those people. Kenya is kinda
[18:53] <zipper> kinda cool
[18:54] <zipper> composite video out?
[18:54] <zipper> wow yes
[18:54] * basti (~IceChat9@xdsl-89-0-185-71.netcologne.de) has joined #raspberrypi
[18:54] <Matt> hell, I've even got an RF modulator here that takes composite video and L/R audio in and put it in NTSC VHF channel 3
[18:54] <zipper> Back to the topic please
[18:54] <Matt> which is attached to a 30 year old TV
[18:54] <zipper> So I am in /dev/mmcblk0p5
[18:55] <Matt> right, yes
[18:55] * YamakasY (~yamakasy@62.58.32.94) Quit (Ping timeout: 260 seconds)
[18:55] <Matt> cd into etc/networking
[18:55] <Matt> or etc/network
[18:55] * Matt doesn't actually use arch :)
[18:56] <shiftplusone> If you need help with arch, look at their wiki
[18:56] <Matt> actually, that might not even be the right place for arch :)
[18:56] <shiftplusone> it has everything
[18:56] <Matt> what you are going to need is a IPv4 netblock to use for your network
[18:56] <shiftplusone> /etc/network/interfaces is a debian thing
[18:56] <zipper> Oh my I don't see /etc/networking but there is https://gist.github.com/urbanslug/9005761
[18:56] <zipper> Matt: ^^
[18:56] <Matt> https://wiki.archlinux.org/index.php/Network_configuration
[18:57] <Matt> specifically, https://wiki.archlinux.org/index.php/Network_configuration#Manual_connection_at_boot_using_systemd
[18:57] <Matt> except where they say /etc/... you wanna substitute /run/media/urbanslug/b471cde8-2a15-44e7-acce-e9a2a54511a6/etc/...
[18:57] <Matt> cause you're modifying your pi's filesystem, not your laptops :)
[18:58] <zipper> So uh I should copy that stuff?
[18:58] <shiftplusone> Matt, what's the goal here?
[18:58] <zipper> Matt: ^
[18:58] <zipper> Matt: I am crap at networking
[18:58] <Matt> now as for IP addresses, given that you're using 192.168.43.x on your phone, we'll need a different network for the pi
[18:59] <Matt> in the intrests of staying away from the typical ones used by routers, let's go with 192.168.100.x
[18:59] <Matt> we'll put the pi on 192.168.100.2 and your laptop on 192.168.100.1
[18:59] <Matt> netmask will be 255.255.255.0
[18:59] <zproc> I have one of those RS232/ Max3232 serial port to ttl http://www.ebay.co.uk/itm/New-MAX3232-RS232-Serial-Port-To-TTL-Converter-Module-DB9-Connector-3-3-5V-Input-/221326032896?pt=UK_Sound_Vision_Other&hash=item33880f4000 where could i find where to plug them?
[18:59] <Matt> shiftplusone: he's got a pi, but no screen for it; so he wants to set it up to ssh into it
[19:00] <shiftplusone> and no router or something?
[19:00] <Matt> his laptop is connected to the 'net via a wifi hotspot on his phone
[19:00] <Matt> and his pi has no wifi
[19:00] <zproc> okay i think i foud
[19:00] <zproc> found*
[19:00] <shiftplusone> got it
[19:00] <Matt> and I've gotta run - it's 1pm
[19:01] * [Saint_] (~saint@rockbox/staff/saint) has joined #raspberrypi
[19:02] * [Saint] (~saint@rockbox/staff/saint) Quit (Ping timeout: 246 seconds)
[19:03] * GenBurnside (~GenBurnsi@12.150.118.194) has joined #raspberrypi
[19:03] * GenBurnside (~GenBurnsi@12.150.118.194) Quit (Remote host closed the connection)
[19:04] * eephyne (~eephyne@eephyne.dyndns.org) Quit (Ping timeout: 248 seconds)
[19:04] * ruben-ikmaak (~ikmaak@541A275B.cm-5-3a.dynamic.ziggo.nl) has joined #raspberrypi
[19:05] * cumana (~koomahnah@unaffiliated/cumana) has joined #raspberrypi
[19:05] <zipper> Matt: Wait dude
[19:06] <zipper> My gateway is my phone's IP?
[19:06] * GenBurnside (~GenBurnsi@12.150.118.194) has joined #raspberrypi
[19:06] <zipper> 192.168.43.1
[19:06] * Encrypt (~Chuck-nor@AMontsouris-553-1-66-234.w92-151.abo.wanadoo.fr) Quit (Quit: Quitte)
[19:06] <zipper> "< zipper> 0.0.0.0 192.168.43.1 0.0.0.0 UG 0 0 0 wlo1"
[19:07] * GenBurnside (~GenBurnsi@12.150.118.194) Quit (Client Quit)
[19:09] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) Quit (Read error: Connection reset by peer)
[19:09] * GenBurnside (~GenBurnsi@12.150.118.194) has joined #raspberrypi
[19:11] * g2nightmare (~matt@209.145.88.131) has joined #raspberrypi
[19:11] * SpeccyMan (~nick@94.197.112.152.threembb.co.uk) Quit (Read error: Connection reset by peer)
[19:12] <zipper> shiftplusone: Can you help?
[19:13] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) has joined #raspberrypi
[19:13] <shiftplusone> Nuh, I don't know what Matt's plan was. I just use NetworkManager, which is not of much help if your laptop doesn't run it. I don't know your situation.
[19:14] * g2nightmare (~matt@209.145.88.131) has left #raspberrypi
[19:14] <zipper> Oh man
[19:17] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) Quit (Read error: Connection reset by peer)
[19:17] * cumana (~koomahnah@unaffiliated/cumana) Quit (Read error: Operation timed out)
[19:18] * dik_dak (~dik_dak@pool-100-2-182-75.nycmny.fios.verizon.net) has joined #raspberrypi
[19:19] <zipper> This is what I have https://gist.github.com/urbanslug/9006131
[19:20] * SpeccyMan (~nick@94.196.70.242.threembb.co.uk) has joined #raspberrypi
[19:20] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) has joined #raspberrypi
[19:24] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) Quit (Read error: Connection reset by peer)
[19:27] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) has joined #raspberrypi
[19:28] <zipper> I can ping the IP but I can't ssh into it via port 22
[19:29] * beond (~macuser@c-67-188-42-108.hsd1.ca.comcast.net) has joined #raspberrypi
[19:30] * linuxstb (~linuxstb@unaffiliated/linuxstb) has joined #raspberrypi
[19:32] <zipper> I have this issue I can ping my RPi IP but I cannot ssh into it I get the following error `sh: connect to host 192.168.100.2 port 22: Connection refused'
[19:36] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) Quit (Read error: Connection reset by peer)
[19:37] * Hydra (~Hydra@46-65-54-87.zone16.bethere.co.uk) has joined #raspberrypi
[19:38] * eephyne (~eephyne@eephyne.dyndns.org) has joined #raspberrypi
[19:39] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) has joined #raspberrypi
[19:43] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) Quit (Read error: Connection reset by peer)
[19:43] <zipper> ShorTie: Do you live?
[19:45] <zipper> FFFFFFFFFFFFFFFFFFFFF
[19:46] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) has joined #raspberrypi
[19:50] * leucos (~leucos@81-65-119-172.rev.numericable.fr) has joined #raspberrypi
[19:53] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) Quit (Read error: Connection reset by peer)
[19:53] * sco` (~ross@unaffiliated/sco/x-3425046) Quit (Read error: Connection reset by peer)
[19:56] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) has joined #raspberrypi
[19:57] * likarish (~likarish@75-144-16-201-sffolsom.ca.hfc.comcastbusiness.net) Quit (Remote host closed the connection)
[19:59] * likarish (~likarish@75-144-16-201-sffolsom.ca.hfc.comcastbusiness.net) has joined #raspberrypi
[19:59] * m8 (~m@unaffiliated/m8) Quit (Quit: Sto andando via)
[20:00] * dreamreal (~jottinge@redhat/dreamreal) Quit (Ping timeout: 260 seconds)
[20:01] * dreamreal (~jottinge@redhat/dreamreal) has joined #raspberrypi
[20:01] * Orion__ (~Orion_@205.118.211.29) has joined #raspberrypi
[20:02] * SebSemmi (~SebSemmi@e178199024.adsl.alicedsl.de) has joined #raspberrypi
[20:04] * thebeav (~thebeav@unaffiliated/thebeav) Quit (Ping timeout: 246 seconds)
[20:07] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) Quit (Read error: Connection reset by peer)
[20:07] * thebeav (~thebeav@unaffiliated/thebeav) has joined #raspberrypi
[20:09] * daphee (~quassel@v22013051655012590.yourvserver.net) has joined #raspberrypi
[20:09] <iiie> zipper: 6131 is your laptop? and you're connected in via serial to the rpi?
[20:09] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) has joined #raspberrypi
[20:09] * taza (~zap@unaffiliated/taza) has joined #raspberrypi
[20:10] <zipper> iiie: No ethernet
[20:11] <zipper> A cable running from my laptop to RPi
[20:11] <iiie> zipper: right, so you're connected in via serial right?
[20:11] <zipper> iiie: I don't think I know what serial is
[20:11] * likarish (~likarish@75-144-16-201-sffolsom.ca.hfc.comcastbusiness.net) Quit (Remote host closed the connection)
[20:12] <iiie> how are you getting output from the pi? what's the cable?
[20:12] <iiie> it's an ethernet cable?
[20:13] * mgottschlag (~quassel@reactos/tester/phoenix64) has joined #raspberrypi
[20:13] <zipper> iiie: I am not sure I am getting output but it did light up the PWR FDX LNK and 100
[20:13] <zipper> iiie: Yes but I can't SSH into it
[20:13] * Mustache (~TopHat@p579B5CE9.dip0.t-ipconnect.de) has joined #raspberrypi
[20:14] <zipper> iiie: Did you see my gists?
[20:14] <iiie> Only the one ending in 6131
[20:14] <iiie> the other expired
[20:14] <Matt> zipper: sorry about that
[20:14] <Matt> had to run to a lunch meeting
[20:14] <zipper> https://gist.github.com/urbanslug/9006466
[20:14] * Matt has a day job you know
[20:14] <zipper> https://gist.github.com/urbanslug/9006131
[20:15] * double-you (~Miranda@178-27-16-123-dynip.superkabel.de) has joined #raspberrypi
[20:15] * koell (~galactica@91.141.1.15.wireless.dyn.drei.com) has joined #raspberrypi
[20:15] <Matt> ok, you're most of the way there :)
[20:16] <zipper> Matt: What is lacking?
[20:16] <Matt> broadcast should be 192.168.100.255
[20:16] <Matt> gateway is going to be 192.168.100.1
[20:16] <Matt> i.e. your laptop
[20:16] <zipper> broadcast is what I had wrong it seems
[20:16] <Matt> if you want internet access from your pi, we need to add some iptables rules to your laptop to route traffic for you
[20:17] <Matt> but that doesn't access getting to your pi from your laptop
[20:17] * he1kki (~heikki@border.bitcoinia.net) has joined #raspberrypi
[20:17] <zipper> Matt: Let me first successfully ssh into it
[20:17] <Matt> hehe
[20:18] <Matt> once you get broadcast sorted you should be pretty much there
[20:18] * [SkG] (~sconde@unaffiliated/skg/x-897332) has joined #raspberrypi
[20:18] <Matt> oh, and you need to configure an IP on your laptop's ethernet interface too
[20:18] <Matt> but that's easy
[20:18] <zipper> Oh man now this thing won't mount
[20:18] <zipper> brb
[20:18] <iiie> zipper: are you sure you're running ssh on the pi?
[20:18] <Matt> iiie: he needs the rest of his network configured first :)
[20:19] <Matt> iiie: it's complicated by the fact he doesn't have a router in the mix
[20:19] <Matt> so there's no dhcp server
[20:19] <iiie> configuring the pi side is easy with boot/config.txt though
[20:19] <Matt> he's not got a serial connection
[20:19] <Matt> he's not got a tv, monitor, or keyboard
[20:19] <iiie> if he has an sd card reader
[20:19] <Matt> this is where we're at :)
[20:20] <Matt> he's got pi connected to laptop via a patch cable and his laptop connected to a wifi hotspot on his phone for internet access
[20:21] * ryanteck (~ryan@fsf/member/Ryanteck) has joined #raspberrypi
[20:21] <zipper> iiie: I have not installed ssh on the pi
[20:21] <Matt> so basically he needs a static IP on his pi, a static IP on his laptop's eth0, and some iptables fun to nat traffic from the pi
[20:21] <zipper> I assume it comes with archlinux-arm
[20:23] * CJD14 (sid24135@gateway/web/irccloud.com/x-bofngvozqcixahpb) Quit (Ping timeout: 264 seconds)
[20:23] <zipper> Successful ping to 192.168.100.2
[20:24] <Matt> did you assign 192.168.100.1 to your laptop?
[20:24] <zipper> still "ssh: connect to host 192.168.100.2 port 22: Connection refused"
[20:24] <Matt> to eth0 specifically
[20:24] <zipper> Matt: I was supposed to create a similar file in my laptop?
[20:24] <Matt> depends how you're configuring your network on there
[20:24] <Matt> chances are on a modern desktop you're using network-manager
[20:25] <Matt> how did you configure your wifi?
[20:25] * Matt runs ubuntu on most of his boxes these days
[20:25] <ozzzy> I moved from Linux to Win8.1
[20:26] <Matt> and the rest of the servers I manage are redhat, centos, SLES, or debian
[20:26] <zipper> Updated https://gist.github.com/urbanslug/9006131
[20:26] * CJD14 (sid24135@gateway/web/irccloud.com/x-uqnwcafpuatrgqzu) has joined #raspberrypi
[20:26] <Matt> zipper: how did you setup your wifi on your laptop
[20:28] <zipper> I use wifi-menu to connect
[20:30] <shiftplusone> you run arch on your laptop?
[20:30] <zipper> On my comp the ethernet interface is enp37s0
[20:30] <zipper> shiftplusone: Yes arch on laptop arch + kde
[20:30] * \mSg_mini (mSg@unaffiliated/msg/x-4576342) has joined #raspberrypi
[20:30] <shiftplusone> Why aren't you just using these instructions then? https://wiki.archlinux.org/index.php/Internet_Sharing
[20:31] <Matt> shiftplusone: you wanna walk him through setting up his laptop to forward traffic?
[20:32] <shiftplusone> nuh, I am not familiar with the process enough
[20:32] <shiftplusone> I usually let NetworkManager do it for me
[20:32] <Matt> hell, "sudo ifconfig enp37s0 192.168.100.1/24" will set an IP, so long as dhcpcd/dhclient isn't running on the interface
[20:32] <Matt> whoops
[20:32] <Matt> excuse my language
[20:32] * Matt tuts
[20:33] * \mSg (mSg@unaffiliated/msg/x-4576342) Quit (Ping timeout: 245 seconds)
[20:33] * \mSg_mini is now known as \mSg
[20:33] <zipper> I use netctl
[20:33] * espiral (maze@unaffiliated/espiral) Quit (Disconnected by services)
[20:34] * espiral (maze@unaffiliated/espiral) has joined #raspberrypi
[20:34] <zipper> Matt: What will `sudo ifconfig enp37s0 192.168.100.1/24' do?
[20:35] * Viper (~Viper@unaffiliated/outofcontrol/x-1373891) Quit (Quit: Free Software, Free Hardware, Free Culture, Free Spectrum)
[20:35] <Matt> it should
[20:36] <zipper> It should what?
[20:36] <Matt> oh, sorry
[20:37] <Matt> it configures network interface "
[20:37] <zipper> Oh man
[20:37] <Matt> it configures network interface "enp37s0" with the ip address 192.168.100.1 with the netmask 255.255.255.0
[20:37] <zipper> I ran it and now I get `ssh: connect to host 192.168.100.2 port 22: No route to host'
[20:37] <zipper> I can't remember what IP I had before
[20:37] <zipper> FML
[20:38] <Matt> nah, you know the IP the pi has, because you configured it
[20:38] <zipper> I mean the IP my computer had
[20:38] <zipper> What IP did that change btw?
[20:39] * zipper is retarded
[20:39] <zipper> The blog post guy did it so easily.
[20:39] * paskl^0ff is now known as paskl
[20:40] <Matt> zipper: you probably didn't have any IP on that interface before
[20:40] <Matt> this is why I said you really need to understand a bit about networking to start with
[20:40] <Matt> so you actually understand what you're setting up, rather than blindly following directions
[20:40] <zipper> Matt: Yes I have never needed a fixed IP on ethernet
[20:40] <zipper> Makes sense
[20:41] <zipper> I used DHCP where I just plugged stuff to routers with DHCP and it worked
[20:41] <Matt> I'm sure there are lots of intros out there, but here's my quick networking 101
[20:41] * Squarepy (~Squarepy@unaffiliated/squarepy) Quit (Ping timeout: 245 seconds)
[20:42] <Matt> in the IP world, every network interface that passes traffic has an IP address (not entirely true, but close enough)
[20:43] <zipper> Yes
[20:43] <Matt> IPv4 addresses look like aaa.bbb.ccc.ddd - IPv6 addresses you can worry about later :)
[20:43] * Out`Of`Control (~Viper@unaffiliated/outofcontrol/x-1373891) has joined #raspberrypi
[20:43] <johnc-> I want IPv6!!
[20:43] <Matt> they have a host part and a network part - the network part is on the left, and the host part on the right as you read it
[20:44] <Matt> exactly how much of the addresses is each is determined by the netmask
[20:44] <zipper> aaa.bbb is the network part
[20:44] * psilocide (~unknown@198.47.45.65) has joined #raspberrypi
[20:44] <IT_Sean> again... that is determined by the hostmask
[20:45] <Matt> which in the example we have on your network is 255.255.255.0
[20:45] <Matt> or /24
[20:45] <Matt> that means that aaa.bbb.ccc. is the network and ddd is the host
[20:45] <zipper> Matt: Host like server?
[20:45] <Matt> host like host :)
[20:45] <Matt> any system on the network
[20:46] <Matt> laptop, desktop, phone, printer, etc
[20:46] <zipper> Oh I see
[20:46] <zipper> Makes sense
[20:46] <Matt> when you configure a network interface, you tell it the IP address and the netmask
[20:46] <Matt> that means it knows what the local network is
[20:46] <zipper> netmask?
[20:47] <Matt> so it knows that if you try and send traffic to another host on the same "netblock", that it should send it directly to that system
[20:47] <Matt> the "255.255.255.0"
[20:47] <Matt> in this example
[20:47] <zipper> ok
[20:48] <Matt> technically, it's representing 4 bytes of data (32-bits)
[20:48] <Matt> 255 is 11111111
[20:49] <Matt> but that's me getting sidetracked :)
[20:49] <zipper> ok
[20:49] <Matt> we can come back to that if you want to know exactly how a netmask works :)
[20:49] <zipper> Good thing to know
[20:49] <Matt> at this point, it's good enough to know that the netmask allows it to work out what the network is
[20:50] <zipper> And in this case the netmask is 255.255.255.0 I feel like it should have /254 for all IPs it can support
[20:51] <Matt> ok, the /xx notation is a shorthand
[20:51] <Matt> when you say /24, that means "24 1s"
[20:51] <Matt> so 11111111111111111111111100000000
[20:51] <Matt> i.e. 255.255.255.0
[20:52] <zipper> Oh
[20:52] <Matt> so let's say your network is 192.168.100.0/24, that means your IPs are going to range from 192.168.100.0 to 192.168.100.255
[20:52] <Matt> now, there are two reserved IPs on every network
[20:52] <Matt> the first one is the "network address"
[20:52] <Matt> and the last one is the "broadcast address"
[20:53] <Matt> so that means that your usable IPs are 192.168.100.1 to 192.168.100.254
[20:54] <zipper> 24 bits wow
[20:54] <Matt> now, technically, you can only send data directly to systems on the same network as you
[20:54] <zipper> I see
[20:54] <Matt> so if you want to send data to another network, you have to tell the system where to send it to get there - this is where routers come in
[20:55] <zipper> Like my phone right now is acting like a router?
[20:55] <Matt> exactly
[20:55] <zipper> Go on
[20:55] <Matt> routers (or gateways) have more than one network interface
[20:55] <Matt> so they can send (route) traffic from one interface to the other
[20:56] <Matt> every system has something called a "routing table" - that's like a little address book that tells the system where to send traffic
[20:57] <Matt> that's what you were looking at when you ran "netstat -rn" later (-r means show the routing table, -n tells it you don't want to resolve IPs to DNS names)
[20:57] <zipper> And by system we mean hosts?
[20:57] <Matt> yup
[20:57] * koell (~galactica@91.141.1.15.wireless.dyn.drei.com) Quit (Ping timeout: 248 seconds)
[20:57] <zipper> ok go on
[20:57] <Matt> there are four things in that table that we care about for this discussion - network, netmask, destination, and interface
[20:58] <Matt> network and netmask as exactly as I just described
[20:58] <IT_Sean> Matt: If i were you, i'd be charging him for this. :p
[20:58] <Matt> destination is the IP of a system on a locally attached network to send that traffic to, and interface is physically what port it goes out of
[20:58] <Matt> normally your system will work out interface for you
[20:59] <Matt> if the destination is "0.0.0.0" that means the network is local, and you don't have to send to a router first
[20:59] * [Saint_] is now known as [Saint]
[20:59] <Matt> is the network and netmask are "0.0.0.0" that's a special case called the "default route", which means "if you don't find any other matching routes - send it here"
[21:00] * jorge_lo (~anonymous@cpe-74-71-0-246.nyc.res.rr.com) has joined #raspberrypi
[21:00] <Matt> IT_Sean: hey, hopefully other folk in the channel get something from this too :)
[21:01] <zipper> Oh man someone here is really disturbing me
[21:01] <Matt> so you can either set IPs and routes manually, which is what we're doing on the pi
[21:02] <Matt> or you can punch all the information into a DHCP server, and let it hand out IPs and other network information automatically
[21:02] * jorge_lo (~anonymous@cpe-74-71-0-246.nyc.res.rr.com) Quit (Client Quit)
[21:02] <Matt> which is what your phone is doing
[21:03] * Armand (~martin@185.24.99.51) Quit (Quit: Leaving)
[21:04] * Vibe (~Vibe@gateway/tor-sasl/vib3) Quit (Ping timeout: 240 seconds)
[21:04] <zipper> Matt: I am used to DHCP server handing out IPs
[21:05] <zipper> by matching routes you mean?
[21:06] <Matt> well routes come afterwards
[21:06] * Vibe (~Vibe@gateway/tor-sasl/vib3) has joined #raspberrypi
[21:06] <zipper> Ok there is this one thing I need to understand. We use IPv4. So we can only have like 255.255.255.255 public IPs
[21:06] <zipper> Ok my question is offtopic
[21:06] <Matt> that's correct, in fact, it's even less than that
[21:07] <Matt> cause a whole bunch are reserved
[21:07] <Matt> anything in the range 10.x.x.x, 172.16-23.x.x, and 192.168.x.x are reserved for private use
[21:07] <zipper> Matt: So how can we have so few public IPs with so many of us on the internet?
[21:07] <Matt> 127.x.x.x is for loopback devices
[21:08] <zipper> Does it mean that when I view my public IP I view my ISPs IP?
[21:08] <Matt> 239.x.x.x (actually, there's more than just 239, but I forget the range) is reserved for "multicast"
[21:08] <Matt> yup
[21:08] <Matt> see, this is exactly the problem we currently have
[21:08] <Matt> the world has run out of ipv4 addresses
[21:08] <zipper> we?
[21:08] <zipper> Oh I see
[21:08] <Matt> "we" being the world as a whole :)
[21:09] <Matt> the way we get round it is by doing something called NAT (Network Address Translation) - that's how internet connection sharing works
[21:09] <zipper> So when I request a page from IP x.x.x.x How does their IP know which sub-IP I am referring to exactly.
[21:09] <Matt> you basically hide an entire network of local systems behind a single external IP
[21:10] <Matt> ok, now we go up a level to TCP :)
[21:10] <zipper> I mean how does their ISP
[21:10] <Matt> every connection you open has a source port and a destination port
[21:10] <Matt> that's a number between 1 and 65535
[21:10] <Matt> you'll recognise common server ports like 80 (http) and 443 (https)
[21:10] <zipper> Wait pause
[21:10] <Matt> ssh is 22
[21:10] <Matt> etc
[21:11] <zipper> Feels like there is a lot to learn man. Will I successfully ssh into this thing?
[21:11] <zipper> Matt: Ok let's go on talking about ports.
[21:11] <Matt> so when you open that connection, your local pc allocates an available local port (typically somewhere high, above 32000) to use as the source port, and opens up a connection to the specified port on the destination
[21:11] * jorge_lo (~anonymous@cpe-74-71-0-246.nyc.res.rr.com) has joined #raspberrypi
[21:12] <Matt> hey, you're the one who asked about NAT :)
[21:12] <zipper> Matt: let's go on learning
[21:12] <zipper> teching
[21:12] <zipper> *or teaching
[21:12] <Matt> so your pc sends out a packet that starts off something like "from: 192.168.100.2:32123, to: 123.123.123.123:80, nexthop: 192.168.100.1, ...."
[21:13] <zipper> Because that is my router
[21:13] <zipper> the .1
[21:13] <Matt> so that's your local IP (192.168.100.2) and port (32123 - picked at random from the available ports)
[21:13] <Matt> where you want connect to (123.123.123.123 port 80)
[21:13] <Matt> and where the packet goes next - i.e. your router on 192.168.100.1
[21:13] * eephyne (~eephyne@eephyne.dyndns.org) Quit (Ping timeout: 252 seconds)
[21:14] <Matt> your router sees that, matches it against the local firewall to make sure it's allowed to forward that traffic
[21:14] <zipper> Matt: if it's allowed it forwards it.
[21:15] <Matt> then here's the fun part - it makes a note of the source and destination IPs and ports, then it *changes* the source IP and port
[21:15] <Matt> it allocated a source port from it's free ports, and changes the source IP to that port and *its* external IP
[21:15] <zipper> Matt: Oh boy, changing data is dangerous but go on
[21:16] <Matt> then it sends on the packet to its default gateway (your ISP)
[21:16] * thebeav (~thebeav@unaffiliated/thebeav) Quit (Ping timeout: 245 seconds)
[21:16] <Matt> so say your external IP is 64.12.23.34
[21:16] * Butcho (Butcho@cpe-065-184-077-062.ec.res.rr.com) has joined #raspberrypi
[21:16] <Matt> the packet comes in "from: 192.168.100.2:32123, to: 123.123.123.123:80, nexthop: 192.168.100.1, ...."
[21:16] <zipper> So the router has a router, the ISP
[21:16] <Matt> and it goes out "from: 64.12.23.34:62340, to: 123.123.123.123:80, nexthop: 64.12.23.1, ...."
[21:17] <zipper> Meaning the ISP also has a limited number of IPs to give it's clients or it will keep having other routers under it
[21:17] <Matt> when the packet finally gets to 123.123.123.123:80, it shows as being from 64.12.23.34, so that's where the reply goes
[21:18] <Matt> when that reply gets back to your router, your router looks at its NAT table, and goes "this is actually meant for 192.168.100.2" and it changes the *destination* IP and port
[21:18] * Encrypt (~Chuck-nor@AMontsouris-553-1-66-234.w92-151.abo.wanadoo.fr) has joined #raspberrypi
[21:19] * SebSemmi (~SebSemmi@e178199024.adsl.alicedsl.de) Quit (Quit: brb)
[21:19] <Matt> so it comes into your router as "from: 123.123.123.123:80, to: 64.12.23.34:62340, ..."
[21:19] * thebeav (~thebeav@unaffiliated/thebeav) has joined #raspberrypi
[21:19] <Matt> and it leaves your router as "from: 123.123.123.123:80, to: 192.168.100.2:32123, ..."
[21:19] <Matt> zipper: yeah, ISPs do have limited numbers of IPs, but at the moment they have enough
[21:20] <Matt> but as customer numbers increase, that's going to be a problem
[21:20] <Matt> and we get into all kinds of nastyness
[21:20] * zproc (~zproc@laf31-6-82-241-3-109.fbx.proxad.net) Quit (Quit: zproc)
[21:20] <IT_Sean> Hence IPV6, but, that's a whole 'nother ball of cheese
[21:20] <Matt> yup :)
[21:20] <Matt> ipv6 addresses are 128 bits long, compared to ipv4's 32
[21:21] <Butcho> Any recommendations for python programming tutorials based on the raspberry pi?
[21:21] * rylinaux (~Ryan@ryan-clancy.com) has joined #raspberrypi
[21:21] <Matt> so there are *lot* more of them :)
[21:21] <zipper> So for a NAT table to know which IP the request is meant from
[21:22] <Matt> zipper: NAT is all dynamic - on a linux machine it's all managed through iptables
[21:22] * zproc (~zproc@laf31-6-82-241-3-109.fbx.proxad.net) has joined #raspberrypi
[21:22] <zipper> It checks source and looks to know which requested to it.
[21:22] <Matt> generally you don't need to worry too much about it - you just setup firewall rules to say that traffic is allowed to be forwarded from these IPs out, and that it should be NATed to this address
[21:22] <Matt> and iptables and netfilter in the kernel do the rest
[21:23] <Matt> but there, you just got routing and NAT 101, all rolled in together :)
[21:23] <Matt> it's a lot to take in
[21:23] <zipper> Which alternatives are there to NAT?
[21:23] <zipper> The new kernel will have nsftables
[21:23] <zipper> It's already out
[21:23] <zipper> Ok offtopic
[21:23] <zipper> Matt: lol it is
[21:24] <ShorTie> most of that junk is in the header, each router either adds or subtract to the header depending on the direction it is going
[21:24] * psilocide (~unknown@198.47.45.65) Quit (Ping timeout: 245 seconds)
[21:24] * andatche (~andatche@mule.andatche.com) Quit (Ping timeout: 260 seconds)
[21:24] <Matt> and linux changes its firewall subsystem every few years :)
[21:25] <Matt> iptables/netfilter is the 3rd incarnation :)
[21:25] <Matt> first there was ipfwadm, then ipchains, then iptables
[21:26] <zipper> Matt: I still don't see why I can't find my RPi man :C Since in this case I am not using my phone when sending data to my RPi
[21:26] <Matt> right
[21:26] <Matt> I have a sneaky feeling that your pi isn't picking up the network configuration
[21:26] <zipper> Matt: Wow I thought this was the first change
[21:26] <Matt> but that's practically impossible to debug without putting a keyboard and screen on it
[21:26] <zipper> I've been talking about it like I understand it
[21:26] <Matt> or getting a compatible serial cable
[21:27] <Matt> some sort of console anyway
[21:27] <zipper> Matt: before I set my ethernet IP I was able to ping 192.168.100.2
[21:27] <Matt> yeah
[21:27] <Matt> because your routing table had no entry for 192.168.100.0/24, so it was going out the default route to your phone
[21:28] <Matt> and probably find your phone was passing it out to your ISP, which is configured incorrectly and has networking gear in that range
[21:28] * jorge_lo (~anonymous@cpe-74-71-0-246.nyc.res.rr.com) Quit (Quit: jorge_lo)
[21:28] <zipper> you mean it was going through my phone and my phone was then looking for that 192.168.100.2 IP
[21:28] <Matt> it's generally considered back practice to route 192.168.x.x (and the other private netblocks) outside your network
[21:28] <Matt> yup
[21:28] <Matt> your phone was probably passing it on to your ISP
[21:28] <Matt> and your ISP was using it
[21:29] <Matt> I can actually hit 192.168.100.1 from here - it's my cable modem
[21:29] <zipper> Yeah sounds like my ISP is doing something wrong
[21:29] * psilocide (~unknown@198.47.45.65) has joined #raspberrypi
[21:29] * intothev01d (~intothev0@unaffiliated/intothev01d) Quit ()
[21:29] <zipper> So I was getting the 192.168.100.2 from my routers router
[21:29] <Matt> yup
[21:30] * andatche (~andatche@mule.andatche.com) has joined #raspberrypi
[21:30] * jorge_lo (~anonymous@cpe-74-71-0-246.nyc.res.rr.com) has joined #raspberrypi
[21:30] * trickyhero (~trickyher@d4-50-215-4.try.wideopenwest.com) has joined #raspberrypi
[21:30] <zipper> Matt: If my ISP was not using it we would've looked further out.
[21:31] <Matt> depending on how their stuff is configured
[21:31] <Matt> it probably wouldn't have gone any further
[21:31] <Matt> 192.168.x.x and the other private subnets are nominally non-routable when you get out onto the internet
[21:31] <zipper> Ok but after setting my ethernet IP to 192.168.100.1 how did that change how I find 192.168.100.2
[21:32] * cumana (~koomahnah@unaffiliated/cumana) has joined #raspberrypi
[21:32] <Matt> well now you have a local IP on 192.168.100.x
[21:32] <Matt> so it sends the traffic directly out that interface
[21:32] <Matt> if you want the next level of exactly how traffic flows around, I can explain how that technically works
[21:32] <Matt> but we get into the next layer down networking
[21:33] * knob (~knob@76.76.202.245) Quit (Quit: Leaving)
[21:33] <zipper> I think I need a book :C
[21:34] <zipper> but yes I also have a feeling the Pi is not picking it up
[21:36] <Matt> like I said - there's lots online :)
[21:36] <zipper> So yes I have "confirmed" the rpi isn't picking up settings
[21:36] <zipper> https://gist.github.com/urbanslug/9006466
[21:36] * eephyne (~eephyne@eephyne.dyndns.org) has joined #raspberrypi
[21:36] <zipper> nmap finds just 192.168.100.1
[21:37] <zipper> Maybe because ethernet might not be eth0 on the RPi
[21:37] * yedderson (~yedderson@unaffiliated/yedderson) has joined #raspberrypi
[21:37] <yedderson> helloo
[21:37] <Matt> it actually gets pretty intresting :)
[21:37] <zipper> network@eth0
[21:37] <Matt> ever heard of a MAC address, or hardware address?
[21:38] <zipper> Matt: Yes I am familiar with that
[21:38] * Butcho (Butcho@cpe-065-184-077-062.ec.res.rr.com) Quit (Ping timeout: 260 seconds)
[21:38] <Matt> ok, so every network adapator has a MAC address, and it's factory configured to be globally unique
[21:38] <Matt> that's technically what gets used to send traffic from one system to another on the local network
[21:39] <Matt> and you do a lookup using a protocol called ARP
[21:40] <Matt> which is broadcast traffic - i.e. ARP packets are sent to every machine on the local network
[21:40] <yedderson> have anyone used the SPI device with Python ?
[21:41] <Matt> so say you're on 192.168.100.1, and you want to send traffic to 192.168.100.2, the first thing that happens is your pc sends out an ARP packet that says "who has 192.168.100.2, tell 192.168.100.1", with its mac address as the source
[21:41] * Ariadeno (~Ariadeno@010.233.dsl.concepts.nl) has joined #raspberrypi
[21:42] <MarcN> yedderson, no, but I've used i2c
[21:42] <Matt> when 192.168.100.2 sees that request, it responds with its mac address
[21:42] <zipper> Matt: So I can't use ARP to get the IP?
[21:43] <Matt> nope, ARP gets you the MAC address for a specified IP
[21:43] <Matt> there are tools like arp-scan which work in a similar way to nmap
[21:44] <Matt> you pass it a range of IPs to scan, and it ARPs for all of them
[21:44] <zipper> I can broadcast to 192.168.100.* on arp?
[21:44] <zipper> You just answered my question
[21:46] <Matt> I'm not overly hopeful it'll find your pi tho
[21:46] <zipper> Matt: I have a feeling the issue is the interface name.
[21:47] <zipper> I asked where I can find interface name from SD and said I had no network/switch/dhcp server and got "<@leming> so unplug it from your laptop and plug it into a switch on your network"
[21:48] * tombrough (~tom@cpc4-newt3-0-0-cust54.newt.cable.virginm.net) has joined #raspberrypi
[21:48] <Matt> yeah, you can't easily
[21:48] <zipper> I say "There is no switch" I get "<@leming> go buy one"
[21:48] <zipper> I'm broke goddamnit
[21:49] <zipper> I bought my RPi for like $110
[21:49] <zipper> The taxes and shipping stuff
[21:49] <zipper> argh
[21:49] <Matt> if arch has an rc.local, you could try adding "ifconfig -a >/root/interfaces.out" to it
[21:49] <Matt> that'll dump the current network interface config to a file called /root/interfaces.out
[21:49] <Matt> and /etc/rc.local gets executed at boot
[21:49] <Matt> assuming arch uses it
[21:50] <ShorTie> nop
[21:50] <Matt> no? oh well :)
[21:50] <Matt> stupid new fangled inits...
[21:50] <zipper> ShorTie: Do you run arch?
[21:50] <Matt> mmm, I love kickstart :)
[21:50] * SebSemmi (~SebSemmi@p57A093E6.dip0.t-ipconnect.de) has joined #raspberrypi
[21:50] <ShorTie> i play with it now and then
[21:51] * Nefarious_`PC (~Nefarious@unaffiliated/nefarious---/x-0774223) has joined #raspberrypi
[21:51] * Nefarious_`PC (~Nefarious@unaffiliated/nefarious---/x-0774223) has left #raspberrypi
[21:51] <zipper> ShorTie: What do you suggest I do?
[21:51] * Ariadeno (~Ariadeno@010.233.dsl.concepts.nl) Quit (Read error: Connection reset by peer)
[21:51] <zipper> I am so screwed
[21:51] <ShorTie> but i use my router to set static ip's for my rPi's so i know where they are after a re-image
[21:52] <ShorTie> na, patients is all you need
[21:52] <Matt> and a little ingenuity I suspect
[21:53] <Matt> zipper: there's definitely no old TV around there with a composite in on the back?
[21:53] <ShorTie> switch will not do any thing for you
[21:54] <zipper> Matt: What about installing a DHCP server on my laptop?
[21:54] <yedderson> my RPI crashes when on hight network or disk load
[21:54] <shiftplusone> yedderson, bad supply. Got a multimeter?
[21:54] <Matt> zipper: that all depends on whether your pi is trying dhcp on boot
[21:54] <Matt> actually, you can check for that pretty easilly
[21:54] <yedderson> shiftplusone: yep
[21:55] <zipper> Matt: By default it should
[21:55] <shiftplusone> yedderson, there are two points on the pi labelled TP1 and TP2. Measure the voltage across them.
[21:55] <shiftplusone> yedderson, when it goes unstable.
[21:55] <Matt> guessing you've never used tcpdump or wireshark :)
[21:56] <ShorTie> zipper, have you set a static ip address in /etc/network/interfaces yet ??
[21:56] <yedderson> shiftplusone: 4.74
[21:56] * Ariadeno (~Ariadeno@010.233.dsl.concepts.nl) has joined #raspberrypi
[21:56] <shiftplusone> yedderson, does it drop further with higher network activity?
[21:56] <Matt> ShorTie: thought we decided that that wasn't arch
[21:56] <Matt> and that was debian/ubuntu specific
[21:56] <yedderson> shiftplusone: I need to mesure it then
[21:57] <ShorTie> we did, i was out shopping, lol.
[21:57] <zipper> no /etc/network
[21:57] <shiftplusone> 4.74 is on the low side, but should still be stable, so I am guessing it drops further than that
[21:57] <zipper> <@leming> our install comes preconfigured for dhcp, just make use of that
[21:57] <zipper> Matt: ^
[21:57] <zipper> Matt: I have used wireshark
[21:57] * applegekko (~applegekk@gateway/tor-sasl/applegekko) Quit (Remote host closed the connection)
[21:57] <Matt> if you run a wireshark dump on your wired NIC, and then boot the pi
[21:58] <yedderson> I runnig everything with Nice so it dosn't break
[21:58] <Matt> you'll see if it's sending anything
[21:58] <Matt> you should see DHCP DISCOVER packets
[21:58] <zipper> Matt: The bloody RPi lights up all over when I plug in ethernet
[21:58] <IT_Sean> um... some LEDs should come on... that's normal.
[21:58] <ShorTie> this might help https://wiki.archlinux.org/index.php/Network_configuration#Static_IP_address
[21:58] * applegekko (~applegekk@gateway/tor-sasl/applegekko) has joined #raspberrypi
[21:58] <yedderson> shiftplusone: do you know a method to stress test the sd ?
[21:59] * SpeccyMan (~nick@94.196.70.242.threembb.co.uk) Quit (Ping timeout: 248 seconds)
[21:59] <shiftplusone> yedderson, nope
[21:59] <zipper> ShorTie: I don't know what my etheret interface is called e.g eth0
[22:00] <yedderson> shiftplusone: I don't think it needs more than 5v
[22:00] <zipper> ShorTie: I need to edit files I can'r run commands on the Pi
[22:01] <shiftplusone> yedderson, it doesn't need more than 5V, but it needs to be close enough to 5V over the entire power range.
[22:01] <shiftplusone> yedderson, if your supply can't deal with a higher load and starts to drop the voltage, that's a problem.
[22:01] <shiftplusone> and 4.74 is pushing it when it comes to proper operation
[22:02] <zipper> If I install a dhcp server on my comp will it just give whatever is on my ethernet port an IP without further need for my input?
[22:02] <ShorTie> have you thought about maybe giving up on arch and using raspbian maybe ??
[22:03] <ShorTie> any perticular reason your hung up on arch ??
[22:03] <ShorTie> raspbian has a bunch of special sauce just for the rPi
[22:04] <Matt> you can install a dhcp server, but you have to be very careful to do two things: 1) make sure it doesn't start on boot; and 2) configure it to only use your wired network interface
[22:04] * jlf` is now known as jlf
[22:05] <zipper> Matt: This doesn't explain how
[22:05] <zipper> https://wiki.archlinux.org/index.php/Dhcpd#Configuration
[22:05] <Matt> no, it doesn't :)
[22:05] <Matt> interface is a commandline flag to dhcpd, and I don't know how you set that in arch
[22:06] * Pr070cal (~Pr070cal@97e0e6e6.skybroadband.com) has joined #raspberrypi
[22:06] <Matt> under debian/ubuntu, it's in /etc/default/dhcpd and on RHEL/CentOS it's /etc/sysconfig/dhcpd
[22:06] <zipper> Matt: Down there it says Listening on only one interface
[22:07] <Matt> yeah, that doesn't actually describe it correctly
[22:07] <Matt> that just tells it to only pay attention on a specific network
[22:07] <ShorTie> your getting into way more then is needed and just adding in total confusion
[22:07] <Pr070cal> hi ive been working on my pi today i wrote to the sdcard now the sdcard when i put it back in my machine says read-only write protected
[22:07] <yedderson> shiftplusone: the lowest value I measured is 4.54, and it crashes
[22:07] <Matt> technically, so long as you only configure stuff in a subnet 192.168.100.0/24 {} block, you *should* be ok, but it's not good practice
[22:07] <Pr070cal> so i put another card in put it in the pi and now thats read-only
[22:07] * revele (~john.doe@d54c18ca6.access.telenet.be) has joined #raspberrypi
[22:08] <shiftplusone> yedderson, there you go, that's terrible.
[22:08] <Pr070cal> two cards in one day i cant now write to
[22:08] <shiftplusone> yedderson, it could either be the supply or the cable attached to the supply
[22:08] <yedderson> shiftplusone: it's an orignal Samsung travel charger
[22:09] <shiftplusone> yedderson, for how many mA?
[22:10] <shiftplusone> I have a samsung charger (700mA) and that works fine. You got something fancy on the USB side? If not, it could very well be the cable.
[22:10] <zipper> Matt: Why not IP 192.168.100.0/24?
[22:10] <yedderson> shiftplusone: 1A
[22:10] <zipper> and how do undo that IP I gave my eth0?
[22:10] <zipper> or it doesn't matter?
[22:10] <ShorTie> cause that is not a valid ip address maybe
[22:10] * scarolan (~seancarol@cpe-70-112-52-158.austin.res.rr.com) Quit (Ping timeout: 265 seconds)
[22:10] <Matt> zipper: if you wanna be safe, re-image your SD card :)
[22:11] <Matt> but you do need a static IP on your laptop's wired ethernet port
[22:11] <Matt> otherwise running a dhcp server isn't going to help )
[22:11] <Matt> :)
[22:11] <yedderson> shiftplusone: it must be a bug, it works fine on FreeBSD
[22:11] <shiftplusone> yedderson, no, it's clearly a power supply issue.
[22:11] <zipper> Matt: I was thinking just removing the files I added
[22:11] <Matt> sure, if you like
[22:11] <Matt> but by the sounds of it, it's not picking them up anyway
[22:11] * pksato (~PEBKAC@unaffiliated/pksato) has joined #raspberrypi
[22:12] <shiftplusone> There's no bug that's going to eat your volts.
[22:12] * kcj (~casey@unaffiliated/kcj) has joined #raspberrypi
[22:12] <zipper> Matt: I assume because I used eth0 and it's not called eth0
[22:13] <yedderson> shiftplusone: can you mesure your rpi voltage to see if it drops, I runned 'apt-get install python-setuptools'
[22:13] <Matt> I don't understand why arch can't just call it eth0...
[22:13] <Matt> that's the linux standard way of doing things...
[22:13] <shiftplusone> yedderson, I don't need to. I know my supply and the pi very well. It runs at 4.95V and drops to 4.9ish at full load.
[22:14] <Matt> we're not BSD... :)
[22:14] * badass (~badass@unaffiliated/badass) Quit (Quit: Leaving...)
[22:14] <ShorTie> it's udev200 that did away with eth0
[22:14] <ShorTie> not arch
[22:14] <Matt> why?
[22:14] <Matt> see, this is why I dislike bleeding edge stuff
[22:14] <ShorTie> i forget
[22:14] <yedderson> shiftplusone: can you get it working on the usb port of your pc ?
[22:15] <ShorTie> that is why i said to go with raspbian
[22:15] <shiftplusone> yedderson, only if I disconnect the wifi stick.
[22:15] <yedderson> shiftplusone: what about the ethernet ?
[22:15] <shiftplusone> yedderson, but that's irrelevant, as it will depend on the PC and/or hub.
[22:15] <zipper> I'll use this range of IPs 139.96.30.100/24
[22:15] <zipper> Matt: I'll use this range of IPs 139.96.30.100/24
[22:15] <Matt> path specific network names?
[22:16] * timewa1ker (~timewalke@eth0.nu) Quit (Ping timeout: 245 seconds)
[22:16] <shiftplusone> yedderson, what about it?
[22:16] <Matt> zipper: no, do not use anything outside 192.168.x.x, 10.x.x.x, or 172.16-24.x.x
[22:16] <Matt> those are the only subnets you should use for a private network
[22:16] <zipper> Matt: It won't conflict with my phone?
[22:16] <Matt> 139.96.30.100 will belong to someone out on the net
[22:16] <Matt> nope
[22:16] <Matt> cause your phone is on 192.168.42.x (IIRC)
[22:17] * timewa1ker (~timewalke@eth0.nu) has joined #raspberrypi
[22:17] <yedderson> shiftplusone: because I couldn't get it working on my pc usb port either
[22:17] <zipper> Matt: 10.10.10.10/24 ?
[22:17] <Matt> actually, National Electric Vehicle Sweden AB
[22:17] * minum (~minum@38.99.52.154) has joined #raspberrypi
[22:17] <Matt> that's who owns 139.96.30.100
[22:17] <Matt> 10.10.10.10 is fine
[22:18] <zipper> From the site it says "The first 3 bytes of this address cannot be exactly the same as those of another interface"
[22:18] <zipper> So yeah I guess it's all good in this hod
[22:18] <zipper> *hood
[22:18] <shiftplusone> yedderson, the other thing that could be happening is that you tripped your polyfuse. You can measure the voltage across F3 (bear the power input) to check.
[22:19] <ShorTie> zipper, got any buddies around that might have a router laying around you could borrow for a little bit
[22:20] * owenmurr (~owenmurr@109.175.201.0) has joined #raspberrypi
[22:20] <Matt> zipper: all that's doing is setting the local ip on your network interface
[22:21] <Matt> "ip addr add... dev eth0" does the same thing as "ifconfig eth0..." but with the newer commands :)
[22:21] <yedderson> shiftplusone: how to check the f3 ?
[22:22] * S0-2 (~sgra@unaffiliated/sgra) has joined #raspberrypi
[22:22] <shiftplusone> yedderson, refer to images here http://elinux.org/R-Pi_Troubleshooting#Troubleshooting_power_problems
[22:23] <shiftplusone> well, the text as well, since it addresses your problem fully
[22:23] * shiftplusone vanishes
[22:24] <yedderson> shiftplusone: btw, 4.74 was with my ethernet plugged in
[22:25] * NIN101 (~core@n900.quitesimple.org) Quit (Quit: good night)
[22:25] <yedderson> shiftplusone: I got 4.94
[22:25] * SgrA (~sgra@unaffiliated/sgra) Quit (Ping timeout: 272 seconds)
[22:26] * sphenxes (~sphenxes@91-119-120-123.dynamic.xdsl-line.inode.at) Quit (Quit: Leaving)
[22:27] * sphenxes (~sphenxes@91-119-120-123.dynamic.xdsl-line.inode.at) has joined #raspberrypi
[22:29] * Moon_Man (~Moon_Man@76.9.195.46) has joined #raspberrypi
[22:30] * eephyne (~eephyne@eephyne.dyndns.org) Quit (Ping timeout: 260 seconds)
[22:32] * eephyne (~eephyne@eephyne.dyndns.org) has joined #raspberrypi
[22:36] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) Quit (Read error: Connection reset by peer)
[22:37] * YeahRight (morgoth@5249A753.cm-4-2c.dynamic.ziggo.nl) Quit (Ping timeout: 245 seconds)
[22:39] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) has joined #raspberrypi
[22:39] * SebSemmi (~SebSemmi@p57A093E6.dip0.t-ipconnect.de) Quit ()
[22:40] * KindOne (KindOne@colchester-lug/silly-fool/donut) Quit (Ping timeout: 265 seconds)
[22:41] * jfrousval (~jfrousval@ARouen-651-1-361-51.w109-209.abo.wanadoo.fr) Quit (Quit: jfrousval se d├ęconnecte)
[22:42] * kwrazi (~kwrazi@220-245-146-175.static.tpgi.com.au) Quit (Ping timeout: 256 seconds)
[22:43] * KindOne (KindOne@colchester-lug/silly-fool/donut) has joined #raspberrypi
[22:44] * GenBurnside (~GenBurnsi@12.150.118.194) Quit (Quit: Leaving)
[22:44] * jorge_lo (~anonymous@cpe-74-71-0-246.nyc.res.rr.com) Quit (Quit: jorge_lo)
[22:46] * SpeccyMan (~nick@94.196.67.251.threembb.co.uk) has joined #raspberrypi
[22:47] <zipper> When I say 10.10.10.10/24 I mean 10.10.10.10 to 10.10.10.10.250?
[22:47] * jorge_lo (~anonymous@cpe-74-71-0-246.nyc.res.rr.com) has joined #raspberrypi
[22:47] <ShorTie> No
[22:48] <zipper> ShorTie: What does it mean?
[22:50] * ppq (~ppq@unaffiliated/ppq) Quit (Quit: ppq)
[22:50] <ShorTie> the 24 means the network is the first 3 numbers
[22:51] <ShorTie> you need to get back to the KISS method i think
[22:52] <ShorTie> can i ask again why you are so hung up on arch for the rPi ??
[22:54] <Matt> zipper: 10.10.10.10/24 means 10.10.10.10 with netmask 255.255.255.0
[22:55] <zipper> Now that I have 192.168.100.0 * 255.255.255.0 U 0 0 0 enp37s0
[22:55] <zipper> and
[22:55] * YeahRight (morgoth@5249A753.cm-4-2c.dynamic.ziggo.nl) has joined #raspberrypi
[22:55] <zipper> 10.10.10.0 * 255.255.255.0 U 0 0 0 enp37s0
[22:55] <zipper> I think I need to get rid of one
[22:56] <zipper> the 192 one since it's valid
[22:56] * xCP23x (~xCP23x@2.25.249.168) has joined #raspberrypi
[22:56] <Matt> the /24 means the netmask in binary is 24 1s, followed by 0s out to 32, i.e. 11111111111111111111111100000000
[22:56] * xCP23x (~xCP23x@2.25.249.168) Quit (Read error: Connection reset by peer)
[22:56] <Matt> and if you take that binary value and break it into 4 chunks, i.e. 11111111 11111111 11111111 00000000
[22:57] <Matt> then translate that from binary into decimal, you get 255 255 255 0
[22:57] <yedderson> how to read from /dev/spidev0.0 ?
[22:57] <Matt> see how it works now? :)
[22:57] * ShorTie thinkz, count 1's and you will figure out the 24
[22:58] * IT_Sean (~Ult_Ubunt@applefritter/IRCStaff/UltimateMacUser1) Quit (Quit: IT_Sean vanishes in a puff of logic)
[22:59] <zipper> Ok dhcp server set up now to test it
[22:59] * zipper crosses fingers
[23:00] <zipper> How do I check which IPs are assigned?
[23:01] * raskolnik (4a6edea5@gateway/web/freenode/ip.74.110.222.165) has joined #raspberrypi
[23:01] <raskolnik> Hi, I'm having an issue with CUPS on the pi not actually printing anything
[23:02] <zipper> SUCCEESSS!!!!!!!
[23:02] <zipper> :d
[23:02] <zipper> :d
[23:02] * lord4163 (~lord4163@81-232-61-81-no226.tbcn.telia.com) Quit (Quit: lord4163)
[23:02] <zipper> :D
[23:02] <zipper> :D
[23:02] <zipper> I meant D not d
[23:02] <zipper> screw happiness lol
[23:02] * agnostic (alex@2600:3c03::f03c:91ff:feae:5f66) has left #raspberrypi
[23:02] <Encrypt> zipper, http://r33b.net/
[23:03] <zipper> So why was setting up DHCP bad?
[23:03] * atouk (~kvirc@ool-457e23d5.dyn.optonline.net) has joined #raspberrypi
[23:05] * Alina-malina (Alina-mali@unaffiliated/alina-malina) Quit (Read error: Connection reset by peer)
[23:05] <Matt> you just wanna be careful you disable it before you go jumping on someone else's network :)
[23:05] * Alina-malina (Alina-mali@unaffiliated/alina-malina) has joined #raspberrypi
[23:05] <zipper> Matt: Yes it's not on by default
[23:05] <Matt> or you'll become persona non-grata very quickly :)
[23:05] * scarolan (~seancarol@cpe-70-112-52-158.austin.res.rr.com) has joined #raspberrypi
[23:06] <zipper> Good time to check what the ethernet interface was
[23:06] <zipper> Matt: What would happen if I did that?
[23:06] <zipper> I'd start dishing out IPs?
[23:06] <Matt> yes
[23:07] <raskolnik> So I have CUPS running and it can see the printer fine, and acts like it's sending jobs to the printer (and will mark them as complete), but nothing is actually printed
[23:08] * SpeccyMan (~nick@94.196.67.251.threembb.co.uk) Quit (Quit: Leaving)
[23:08] <zipper> What do you make of this sorcery? It looks very eth0 to me https://gist.github.com/urbanslug/9010425
[23:08] <Matt> yup, definitely eth0
[23:09] <zipper> So what was the issue? hmmmm
[23:09] <Matt> that's a good question
[23:09] <Matt> see why it's easier to have a local console? :)
[23:09] <zipper> I want to figure it out.
[23:09] <zipper> Matt: local console?
[23:10] <zipper> What sucks is how much electronics cost :(
[23:12] <Matt> kb/monitor or serial cable
[23:13] <Matt> https://www.adafruit.com/products/954 is the kind of serial cable we're talking about
[23:13] <zipper> Matt: Yes I do. I guess I could get a modern TV but I don't want to because I still live with my old man
[23:14] <zipper> Matt: That seems to come out pf GPIO to usb
[23:15] <Matt> doesn't your old TV have composite in?
[23:15] <zipper> It does
[23:15] <Matt> so why not use that?
[23:15] <zipper> but no extra keyboard at the time and I was impatient
[23:16] <zipper> I don't need a GUI
[23:16] <Matt> heh, it's still easier to troubleshoot networking when you're local :)
[23:16] <zipper> YET
[23:16] <zipper> Matt: True
[23:16] <zipper> but I feel like this way I learned so much more
[23:16] <Matt> oh, quite probably true :)
[23:16] <zipper> Even though you did like everything lol
[23:17] <Matt> so long as some of it stuck :)
[23:17] <zipper> Matt: Actually a lot of it stuck
[23:18] <zipper> I still don't believe my comp on wifi doesn't conflict with my dhcp server
[23:18] * raskolnik (4a6edea5@gateway/web/freenode/ip.74.110.222.165) Quit (Quit: Page closed)
[23:18] <Matt> if you set it up right, it won't
[23:18] <zipper> Though I know they are on different interfaces
[23:18] <Matt> cause it's on different network interfaces
[23:18] <zipper> I didn't do much setting up
[23:18] <Matt> and nwo you can go google "tcp/ip introduction" and do some reading :)
[23:19] <zipper> Matt: Clearly I need to learn about networks
[23:19] <zipper> Why not learn about NAT first?
[23:19] <zipper> I want to know about local networks like in my house
[23:19] <ShorTie> take some CCNA classes
[23:22] <zipper> ShorTie: That sounds like WORK!
[23:22] <zipper> I'm still learning me a haskell
[23:22] * jorge_lo (~anonymous@cpe-74-71-0-246.nyc.res.rr.com) Quit (Quit: jorge_lo)
[23:23] * mrueg (~mrueg@gentoo/developer/mrueg) Quit (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.)
[23:23] * mrueg (~mrueg@gentoo/developer/mrueg) has joined #raspberrypi
[23:23] <ShorTie> ya, learning is work
[23:23] <zipper> OMFG my comp acts like a router for my RPi
[23:23] <ShorTie> zipper you need to read the topic!
[23:23] <zipper> So everything but my RPi is a DHCP router
[23:24] <zipper> ShorTie: Sorry
[23:24] * jorge_lo (~anonymous@cpe-74-71-0-246.nyc.res.rr.com) has joined #raspberrypi
[23:25] * Mustache (~TopHat@p579B5CE9.dip0.t-ipconnect.de) Quit ()
[23:26] * lupinedk is now known as Lupinedk
[23:27] * MidnighToker (~Toker@unaffiliated/midnightoker) has joined #raspberrypi
[23:30] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) Quit (Read error: Connection reset by peer)
[23:31] * basti (~IceChat9@xdsl-89-0-185-71.netcologne.de) Quit (Ping timeout: 260 seconds)
[23:31] * trickyhero (~trickyher@d4-50-215-4.try.wideopenwest.com) Quit (Quit: Leaving)
[23:32] * basti (~IceChat9@xdsl-89-0-185-71.netcologne.de) has joined #raspberrypi
[23:32] <Matt> right, well I think I've got a working zfs based server here
[23:33] <Matt> let's see if anything breaks after a dist-upgrade
[23:34] <yedderson> when I 'modprobe spidev' it's not showing in lsmod
[23:34] * _BigWings_ (~Thunderbi@modemcable167.12-130-66.mc.videotron.ca) has joined #raspberrypi
[23:35] * double-you (~Miranda@178-27-16-123-dynip.superkabel.de) Quit (Quit: ja)
[23:35] <ShorTie> maybe look in dmesg for clues
[23:36] <yedderson> should I do that in order to use the device ?
[23:37] <yedderson> nothing in dmesg
[23:38] * felipealmeida (~user@179.210.237.70) Quit (Remote host closed the connection)
[23:39] * Encrypt (~Chuck-nor@AMontsouris-553-1-66-234.w92-151.abo.wanadoo.fr) Quit (Quit: Quitte)
[23:39] <ShorTie> sure your not looking for spi-bcm2708
[23:39] <rikkib> Have you adjusted the blacklist?
[23:39] <ShorTie> that is blacklisted by defualt in raspbian
[23:39] <rikkib> /etc/modprob.d
[23:40] <rikkib> /etc/modprobe.d
[23:40] <rikkib> remove the spi device
[23:40] * thebeav (~thebeav@unaffiliated/thebeav) Quit (Read error: Connection reset by peer)
[23:40] <yedderson> what the difference between spidev and spi-bcm2708 ?
[23:40] * Ariadeno (~Ariadeno@010.233.dsl.concepts.nl) Quit (Quit: HydraIRC -> http://www.hydrairc.com <- Wibbly Wobbly IRC)
[23:41] <ShorTie> . /etc/modprobe.d/raspi-blacklist.conf to be more exact
[23:41] <yedderson> what should I black list and why ?
[23:41] <rikkib> it is blacklisted
[23:41] <yedderson> ah ok
[23:42] <rikkib> Comment the line
[23:42] <rikkib> ######
[23:42] * elgrecoFL (Jezzz@unaffiliated/elgrecofl) Quit (Excess Flood)
[23:42] * zproc (~zproc@laf31-6-82-241-3-109.fbx.proxad.net) Quit (Quit: zproc)
[23:42] <rikkib> You can also add the module to /etc/modules to load it on boot
[23:42] <rikkib> spi-bcm2708
[23:43] * elgrecoFL (Jezzz@unaffiliated/elgrecofl) has joined #raspberrypi
[23:43] * minimec (~martin@unaffiliated/minimec) has joined #raspberrypi
[23:43] <rikkib> but I think it auto loads if you remove from blacklist
[23:44] <rikkib> reboot after editing the blacklist
[23:44] <yedderson> rikkib: do I need to reboot ?
[23:44] <yedderson> rikkib: I have spi-bcmxxxx loaded but not spidev
[23:44] <ShorTie> or just modprobe it
[23:44] <ShorTie> you can modprobe it at any time
[23:45] <ShorTie> blasklist just keeps it from loading at boot
[23:45] <yedderson> it doesn't modprobe
[23:45] <yedderson> no messages
[23:46] <ShorTie> does it show up in lsmod
[23:46] <yedderson> ShorTie: no
[23:46] <rikkib> ls /dev
[23:46] * IT_Sean (~IT_Sean@applefritter/IRCStaff/UltimateMacUser1) has joined #raspberrypi
[23:46] <yedderson> ShorTie: just the spi-bcm2708
[23:47] <rikkib> that is all
[23:47] <rikkib> ls /dev
[23:47] <yedderson> rikkib: I have the /dev/spidev0.
[23:47] <rikkib> that is it
[23:47] <ShorTie> spi-bcm2708 is in lsmod ??
[23:48] <rikkib> and 0.1
[23:48] <yedderson> ok that's good
[23:48] <rikkib> ru test program
[23:48] <rikkib> run
[23:48] <ShorTie> it will not show anything on the command line
[23:48] <rikkib> What are you talking to?
[23:48] <ShorTie> but will show up in dmesg and lsmod
[23:49] <yedderson> rikkib: a mcp2302, an adc
[23:49] <rikkib> wiringPi supports that I think
[23:49] <ShorTie> that will not show up anywhere i believe
[23:49] * revele (~john.doe@d54c18ca6.access.telenet.be) Quit (Ping timeout: 252 seconds)
[23:50] * revele (~john.doe@d54c18ca6.access.telenet.be) has joined #raspberrypi
[23:50] <yedderson> rikkib: I didn't tried that yet, I'm trying with py-spidev
[23:50] <rikkib> ok
[23:50] <rikkib> wiringPi makes writing a C program easy
[23:51] <rikkib> Gordaon has done most of the work for you
[23:53] <yedderson> rikkib: I've compiled spidev_test.c how to execute it ?
[23:54] <rikkib> ./name
[23:54] <yedderson> sudo ./spidev_test doesn't work
[23:54] <rikkib> dot slash
[23:54] <yedderson> I dit that
[23:54] <rikkib> spi need root
[23:54] <rikkib> set a password
[23:54] <yedderson> It doesn't tab complete, but the file is there
[23:55] <rikkib> Do you know about Linux security
[23:55] <rikkib> Is you RPi on a private IP and firewalled
[23:55] <yedderson> a little bit I guess
[23:56] <rikkib> sudo passwd root
[23:56] <yedderson> my rpi is connected to my router, no firewall
[23:56] <rikkib> Hmmm
[23:56] <rikkib> use a good password
[23:56] <rikkib> strong
[23:57] <yedderson> ok
[23:57] <yedderson> weak
[23:57] <rikkib> letters numbers upper case special char
[23:57] <yedderson> why ??
[23:57] * MarcN (~marc@c-67-189-152-205.hsd1.nh.comcast.net) Quit (Read error: Operation timed out)
[23:57] <ShorTie> did you edit spidev_test.c by chance ??
[23:57] <rikkib> Good practise
[23:57] <yedderson> ShorTie: no
[23:57] <ShorTie> http://www.brianhensley.net/2012/07/getting-spi-working-on-raspberry-pi.html
[23:57] <ShorTie> might need to be
[23:58] <rikkib> wiringPi
[23:59] <yedderson> ShorTie: :*

These logs were automatically created by RaspberryPiBot on irc.freenode.net using the Java IRC LogBot.