Ryan
July 1, 2014, 12:57pm
1
I just recently changed to a static IP on my Beaglebone black. I am trying to follow a guide on creating a web server with my Beaglebone black. Currently running Debian Wheezy instead of Angstrom like I was doing previously.
The link to the guide: http://www.element14.com/community/community/designcenter/single-board-computers/next-gen_beaglebone/blog/2013/11/20/beaglebone-web-server–setup
If there is a better guide for creating a web server with Debian Wheezy… I’d also love to see it.
I am very new to Linux, and now with Debian running, I am a little stuck… The static IP I set is working fine, since I’ve been able to connect to it… so I don’t really think it could be the static IP, I think I may just be using an incorrect method for getting the “opkg update.”
Response For getting the “opkg update”:
root@beaglebone:~# sudo apt-get update
Err http://ftp.us.debian.org wheezy Release.gpg
Could not resolve ‘ftp.us.debian.org ’
Err http://ftp.us.debian.org wheezy-updates Release.gpg
Could not resolve ‘ftp.us.debian.org ’
Err http://beagle.s3.amazonaws.com wheezy-bbb Release.gpg
Could not resolve ‘beagle.s3.amazonaws.com ’
Err http://security.debian.org wheezy/updates Release.gpg
Could not resolve ‘security.debian.org ’
Reading package lists… Done
W: Failed to fetch http://ftp.us.debian.org/debian/dists/wheezy/Release.gpg Could not resolve ‘ftp.us.debian.org ’
W: Failed to fetch http://ftp.us.debian.org/debian/dists/wheezy-updates/Release.gpg Could not resolve ‘ftp.us.debian.org ’
W: Failed to fetch http://security.debian.org/dists/wheezy/updates/Release.gpg Could not resolve ‘security.debian.org ’
W: Failed to fetch http://beagle.s3.amazonaws.com/debian/dists/wheezy-bbb/Release.gpg Could not resolve ‘beagle.s3.amazonaws.com ’
W: Some index files failed to download. They have been ignored, or old ones used instead.
I’m a big noob, and I really appreciate any help you have to offer.
Thanks,
Ryan
What are you using for /etc/resolv.conf?
I'm wondering if i should just add google's dns settings by default..
# Use Google public DNS server:
nameserver 8.8.8.8
nameserver 8.8.4.4
Regards,
Ryan
July 1, 2014, 1:08pm
3
I added those nameserver, but I still have the same result…
I have two nameservers currently in the /etc/resolve.conf that aren’t the Google public DNS servers that you listed.
Of course, i forgot the second question as i was running out of the door..
What interface? eth0 or usb0?
Regards,
Ryan
July 1, 2014, 1:29pm
5
No problem, thank you for helping me in a bad time…
eth0… I never did re-comment out the usb0, I was a little bit confused after reading a few guides on setting a static IP for if I was suppose to comment out the usb0 after un-commenting and using the eth0
I tried doing a shutdown to see if that could have been the problem, so I went back in to check the /etc/resolve.conf and saw that it became empty for some reason?
It get's overwritten on bootup..
Add this to your iface: for eth0:
dns-nameservers 8.8.8.8 127.0.0.1
Regards,
Ryan
July 1, 2014, 1:44pm
7
Added it, then tried the update again, no changes in the response:
auto eth0
iface eth0 inet static
address 192.168.1.61
netmask 255.255.255.0
gateway 192.168.1.83
dns-nameservers 8.8.8.8 127.0.0.1
Added it, then tried the update again, no changes in the response:
auto eth0
iface eth0 inet static
address 192.168.1.61
netmask 255.255.255.0
gateway 192.168.1.83
dns-nameservers 8.8.8.8 127.0.0.1
Did you then do "ifdown eth0" followed by "ifup eth0"? Alternatively
reboot.
You can check it worked by looking in /etc/resolv.conf.
David
Ryan
July 1, 2014, 1:53pm
9
Just tried the ifdown and ifup, that went fine, but the /etc/resolve.conf is still completely empty.
Just tried the ifdown and ifup, that went fine, but the /etc/resolve.conf
is still completely empty.
The answer is that it should be dns-nameserver not dns-nameservers. To add
multiple servers add multiple lines.
David
Ryan
July 1, 2014, 2:08pm
11
Okay, I made that change.
Ryan
July 1, 2014, 2:12pm
12
Still no changes with the get update.
can you ping the gateway from the bbb?
Regards,
Ryan
July 1, 2014, 2:31pm
15
Changed the gateway address, and now it works…