Looking for help - Rasberry Pi - HiFiBerry Digi - Volumio

[Dave_]

SSH isn't much use to me until the Pi can be seen from another computer. Correct?

No.

 

[ifor]

SSH isn't much use to me until the Pi can be seen from another computer. Correct?

No.

Please, tell me more. I obviously no even less about SSH than I thought I did.

 

[margetti]

SSH isn't much use to me until the Pi can be seen from another computer. Correct?

No.

Well, until ifor can get an IP address on his Pi, SSH will be no good which I think is what was being asked...

EDIT - Is your "no" in reply to the first sentence or the second? Just realised I may be misinterpreting your reply...

 

[margetti]

This is where ssh comes in useful. You can normally still ssh in and use the shutdown or reboot command even if the system is locked up.

Not IME on the Pi, but maybe that's just me! :doh:

 

[Dave_]

SSH isn't much use to me until the Pi can be seen from another computer. Correct?

No.

Well, until ifor can get an IP address on his Pi, SSH will be no good which I think is what was being asked...

EDIT - Is your "no" in reply to the first sentence or the second? Just realised I may be misinterpreting your reply...

Yeah sorry, I meant no ssh isn't any use until he can get an IP Addy.

 

[margetti]

Back to the DHCP issue... a bit stumped at present, mainly due toddler demanding the most of my attention! Trying to figure out if it is the AE not giving out an address or the Pi at fault... hoping daveh can give some pertinent advice in the meantime :?

 

[Dave_]

I'd start with the most obvious and easiest and often overlooked first. H/W.

I've had network issues before and wasted hours troubleshooting and messing about with configs to find it was a dodgy cable.

Swap the Ethernet cable thats being used to connect the pi to the router, and also try a different Ethernet port on the router and go from there.

 

[margetti]

I'd start with the most obvious and easiest and often overlooked first. H/W.

I've had network issues before and wasted hours troubleshooting and messing about with configs to find it was a dodgy cable.

Swap the Ethernet cable thats being used to connect the pi to the router, and also try a different Ethernet port on the router and go from there.

Good call!

 

[ifor]

I'd start with the most obvious and easiest and often overlooked first. H/W.

I've had network issues before and wasted hours troubleshooting and messing about with configs to find it was a dodgy cable.

Swap the Ethernet cable thats being used to connect the pi to the router, and also try a different Ethernet port on the router and go from there.

Good call!

Thanks both. This is what I've done. I've unplugged the Pi and moved it to the study where I have connected it to the network using the Ethernet cable that is usually connected to the iMac. Unfortunately the Pi has no monitor attached. http://volumio.local on the iPad doesn't load a page so I assume the problem is the same. Connection is thus: router / Ethernet cable / Airport Extreme / Ethernet cable / Homeplug / mains / Homeplug / Ethernet cable / Pi.

 

[Dave_]

OK looking back through this thread at the various outputs posted I'm wondering if this is a subnet issue

DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8

DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8

DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15

DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13

DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13

No DHCPOFFERS received.

No working leases in persistent database - sleeping.

done.

Looking at the outputs margeti has posted, and checking on my network I would expect the subnet to be 255.255.255.0 not as above.

Try running ifconfig on your Mac and posts its output.

Then if you can, connect your pi back up to a monitor/network then we could try to set a static IP on the pi by editing /etc/network/interfaces.

I'm just trying to find out what the airport extremes default DHCP pool is so we can give the pi an address outside that range (but still within the same subnet) to prevent any conflicts.

EDIT - Airports assign .2 to .200 to DHCP.

 

[margetti]

Hi daveh, I thought the 255.255.255.255 was a bit strange too but had a quick look around and it does seem this is possibly a red herring....

That said I completely agree that a static address (via /etc/network/interfaces) is the way forward, providing - as you say - we avoid any IP address conflicts...

 

[Dave_]

EDIT - Airports assign .2 to .200 to DHCP.

Just to add,

Rather than assume the extreme is using defaults, if you launch airport utility click on the internet tab, and then DHCP, and note the DHCP beginning and ending addresses that will make sure we avoid any conflicts.

 

[ifor]

EDIT - Airports assign .2 to .200 to DHCP.

Just to add,

Rather than assume the extreme is using defaults, if you launch airport utility click on the internet tab, and then DHCP, and note the DHCP beginning and ending addresses that will make sure we avoid any conflicts.

Unfortunately Airport Utility under Mavericks doesn't have those tabs. I've checked the IP addresses of various iPhones, iPads, iMacs and a MacBook and we currently have the following endings: 111, 162, 125, 136, 152, 114, 103 and 116. Subnet mask is 255.255.255.0

The Pi is now reconnected to the TV and the 255.255.255.255 that I reported earlier is definitely correct.

Does any of this help?

Edit: I've just found how to access stuff in the new Airport Utility, but I don't see where it tells me a begining and ending address.

 

[MoJoe]

I am finding this project is turning out to be more hassle than it is worth for me. I decided to just leave the Pi plugged in at all times. I have lost count of how many times I have had to re-flash it. This time i can't re-flash to the 64gb SD card because the SD card believes it has less than 1gb of space. I wanted/expceted this to work just like another bit of kit. Switch it on and enjoy. Perhaps that was a little naive. Or perhaps my inexperience with this form of technology is playing it's part. Anyway... meh, see ye volumio and see ye Pi.

 

[Dave_]

OK don't worry about it if you can't find the DHCP settings, we'll just assume its using defaults, which will avoid any conflicts anyway looking at the IPs your devices have been assigned.

One thing we do need is the default gateway (the extremes IP Addy), so if you could run ifconfig on your Mac unless it lists it in airport util somewhere and I'll post up the config changes you need to make

 

[ifor]

OK don't worry about it if you can't find the DHCP settings, we'll just assume its using defaults, which will avoid any conflicts anyway looking at the IPs your devices have been assigned.

One thing we do need is the default gateway (the extremes IP Addy), so if you could run ifconfig on your Mac unless it lists it in airport util somewhere and I'll post up the config changes you need to make

The Extreme is 10.0.0.100

 

[Dave_]

OK first things first, in the terminal enter,

'sudo cp /etc/network/interfaces /etc/network/interfaces.backup' (this will create a backup of the file your about to edit)

Then enter,

'sudo nano /etc/network/interfaces' (this will open the file in nano, the default text editor for RPis running rasbian based distros)

Now look for the line that reads, 'iface eth0 inet dhcp'.

You need to edit this line and add the static address, gateway and subnet so it looks like below,

iface eth0 inet static

address 10.0.0.201

netmask 255.255.255.0

gateway 10.0.0.100

Now hit ctrl + X this will exit nano, then Y to save any changes.

Enter 'sudo shutdown -r now' or 'sudo reboot'. Wait for the Pi to reboot.

Hopefully if its worked, if you enter volumio.local/ or the ip address 10.0.0.201 in a browser you should see the volumio web interface

 

[ifor]

Thank you. I will try it in the morning.

 

[ifor]

I haven't done the above yet, but I thought it might be worth mentioning what I just noticed on rebooting the Pi.

DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5

DHCPREQUEST on eth0 to 255.255.255.255 port 67

DHCPOFFER from 10.0.0.1

DHCPACK from 10.0.0.1

Reloading /etc/samba/smb.conf: smbd only.

bound to 10.0.0.101 -- renewal in 74259 seconds.

done.

Does this mean the gateway should be 10.0.0.1, which is the Sitecom router rather than 10.0.0.100, which is the AirPort Extreme, which I now know to be in Bridge Mode.

 

[ifor]

I have tried gateway as both 10.0.0.1 and 10.0.0.100 and mask as both 255.255.255.0 and 255.255.255.255. No luck!

 

[margetti]

Hi ifor, have been watching from the sidelines so to speak - no point in me adding anything whilst daveh was on the case

First things first - you're Pi has finally managed to get an IP address from DHCP :dance: , which is 10.0.0.101

So 10.0.0.101 should now work in your broweser to access the web GUI....

 

[ifor]

I am now looking at:

eth0 Link encap:Ethernet HWaddr b8:27:eb:14:a4:70

inet addr:10.0.0.201 Bcast:10.0.0.201 Mask:255.255.255.255

inet6 addr: fe80::ba27:ebff:fe14:a470/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:2 errors:0 dropped:2 overruns:0 frame:0

TX packets:78 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:240 (240.0 B) TX bytes:18025 (17.6 KiB)

lo Link encap:Local Loopback

inet addr: 127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:44 errors:0 dropped:0 overruns:0 frame:0

TX packets:44 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:3828 (3.7 KiB) TX bytes:3828 (3.7 KiB)

 

[ifor]

Good morning margetti. You probably missed my edit to the previous post, but no luck so far. I am now reverting to the original network setting to see whether I can get back to the state that your comment relates too. Unfortunately this time no offers were received.

 

[margetti]

Morning yes I've just seen we had crossed posts which doesn't help, lol!

So you're back to where you were this morning? When it very much appears you got an IP address from DHCP... I would switch off the Sitecom router, AE, and Pi and leave them off for a few minutes (all a bit OTT I have to say but bare with me) then restart them again in that order, with the Pi being switched back on last... watch for that DHCPOFFER again whilst the Pi boots...

 

[ifor]

Yes, after several reboots I am exactly where I was this morning with the apparent IP address of 10.0.0.101, but I still can't access it with http://Volumio.local. It is showing in the finder window on the iMac. I'll now do the reboot sequence as you suggested.