Re: Puppy on a RPI 2+


Marty Hartwell
 

Hi David

Ok answer to the first question then I will go to the shack where all is located and try to get the other
information for you. So there will be two or more responses to this email.


On 05/01/2016 12:06 PM, David Ranch dranch@trinnet.net [Raspberry_Pi_4-Ham_RADIO] wrote:


Hey Marty,

Ok... let's see if I can piece all of this together:

- Your Rpi (non-working network) and other working Xubuntu machines are using *wired ethernet* CAT5 or CAT6 cables to the Cisco Xfinity XB3 cablemodem. Is that accurate?
Not quite, two Xubuntu are, the desktop and the ham laptop. The RPi is in there also and wired to the router.

- You also said "It does have modem for 2.4 and also 5.0 networks" I assume your referring to 2.4Ghz and 5.8Ghz Wifi? Is this Wifi support coming from the Comcast box? Other than the Samsung tablet using Wifi? If true, that means that you're not using wireless
Ok not sure what you mean by not using wireless. Two are connected to internet by way of wi-fi through the router.
The SSID we see is "HOME - AB0A-2.4. The newer phones and tablets that can connect see both that one and the
HOME - AB0A-5.0 and connect with the same passcode. And there is only one box that Comcast (Xfinity) installed.
Total of 4 usable PC's and the unusable at present RPi, plus some tablets.

We have a birthday party to attend this afternoon starting about 2:00 PM so I will get to the commands and responses
you requested then.

Marty

- Per an email from you on 4/29/16 @ 3:54pm, you had the following IPs on the Rpi:

inet addr:10.0.0.91 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr:2601:483:200:6dfc:3ff8:b1e9:7e03:f29a/64 Scope:Global
inet6 addr:2601:483:200:6dfc::9179/128 Scope:Global
inet6 addr:fe80::5877:240a:77ac:4ef0/64 Scope:Link



Ok, some additional / corrected commands to get some more data (send back your results):

- Let's see what kind of DHCP lease information you're getting with the command: dhcpcd -T eth0

- Can you ping your IPv4 default gateway: ping -c 5 10.0.0.1

- Let's try the IPv6 ping command again but with the right syntax: sudo ping6 -c 5 2001:558:feed::1



So it looks like your Rpi is preferring to use IPv6 but in your route table, it's using the "LinkLocal" address as the next hop which is unfamiliar to me:

pi@raspberrypi:/etc $ /sbin/ip -6 route show dev eth0
2601:483:200:6dfc::/64 proto kernel metric 202
fe80::/64 proto kernel metric 256
default via fe80::7454:7dff:fe9f:ab0d metric 202 <--------------------

Your traceroute seemed to automatically route from your LinkLocal to your SiteLocal address:

2601:483:200:6dfc:7454:7dff:fe9f:ab0d <--------------------- Notice the suffix is identical to your linklocal address

Per https://wiki.archlinux.org/index.php/IPv6#IPv6_on_Comcast , once we get the output of the DHCP lease data, I think we can try doing some tests to see if we can get IPv6 working.


As a IPv4 test, edit the /etc/gai.conf file with sudo rights, and remove the "#" from the beginning of the line that looks like:

#precedence ::ffff:0:0/96 100

Once saved, reboot the Rpi and then try:

ping -c 5 8.8.8.8

If that works, try other things like a web browser or what not on your Raspberry Pi. Does that work now?

--David
KI6ZHD




On 04/30/2016 04:05 PM, Marty Hartwell mhartwe@gmail.com [Raspberry_Pi_4-Ham_RADIO] wrote:

Hi David

Here are the results of your request. I will put the contents of the
file named net2 and see if I can attach
a copy too.

--------Beginning of results------------

command cat /etc/gai.conf >> $HOME/net2

# Configuration for getaddrinfo(3).
#
# So far only configuration for the destination address sorting is needed.
# RFC 3484 governs the sorting. But the RFC also says that system
# administrators should be able to overwrite the defaults. This can be
# achieved here.
#
# All lines have an initial identifier specifying the option followed by
# up to two values. Information specified in this file replaces the
# default information. Complete absence of data of one kind causes the
# appropriate default information to be used. The supported commands
include:
#
# reload <yes|no>
# If set to yes, each getaddrinfo(3) call will check whether this file
# changed and if necessary reload. This option should not really be
# used. There are possible runtime problems. The default is no.
#
# label <mask> <value>
# Add another rule to the RFC 3484 label table. See section 2.1 in
# RFC 3484. The default is:
#
#label ::1/128 0
#label ::/0 1
#label 2002::/16 2
#label ::/96 3
#label ::ffff:0:0/96 4
#label fec0::/10 5
#label fc00::/7 6
#label 2001:0::/32 7
#
# This default differs from the tables given in RFC 3484 by handling
# (now obsolete) site-local IPv6 addresses and Unique Local Addresses.
# The reason for this difference is that these addresses are never
# NATed while IPv4 site-local addresses most probably are. Given
# the precedence of IPv6 over IPv4 (see below) on machines having only
# site-local IPv4 and IPv6 addresses a lookup for a global address would
# see the IPv6 be preferred. The result is a long delay because the
# site-local IPv6 addresses cannot be used while the IPv4 address is
# (at least for the foreseeable future) NATed. We also treat Teredo
# tunnels special.
#
# precedence <mask> <value>
# Add another rule to the RFC 3484 precedence table. See section 2.1
# and 10.3 in RFC 3484. The default is:
#
#precedence ::1/128 50
#precedence ::/0 40
#precedence 2002::/16 30
#precedence ::/96 20
#precedence ::ffff:0:0/96 10
#
# For sites which prefer IPv4 connections change the last line to
#
#precedence ::ffff:0:0/96 100
#
# scopev4 <mask> <value>
# Add another rule to the RFC 6724 scope table for IPv4 addresses.
# By default the scope IDs described in section 3.2 in RFC 6724 are
# used. Changing these defaults should hardly ever be necessary.
# The defaults are equivalent to:
##scopev4 ::ffff:169.254.0.0/112 2
#scopev4 ::ffff:127.0.0.0/104 2
#scopev4 ::ffff:0.0.0.0/96 14

command cat /etc/host.conf >> $HOME/net2

multi on

command traceroute 2001:4860::8888 >> $HOME/net2

traceroute 2001:4860::8888
traceroute to 2001:4860::8888 (2001:4860::8888), 30 hops max, 80 byte
packets
1 2601:483:200:6dfc:7454:7dff:fe9f:ab0d
(2601:483:200:6dfc:7454:7dff:fe9f:ab0d) 26.063 ms 32.273 ms 32.795 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

command
ping -c 5 75.75.75.75
ping: icmp open socket: Operation not permitted
pi@raspberrypi:/etc $ sudo ping -c 5 75.75.75.75
PING 75.75.75.75 (75.75.75.75) 56(84) bytes of data.

--- 75.75.75.75 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

command
sudo ping -c 5 75.75.76.76
PING 75.75.76.76 (75.75.76.76) 56(84) bytes of data.

--- 75.75.76.76 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4002ms

command
pi@raspberrypi:/etc $ sudo ping -c 5 2001:558:feed::1
ping: unknown host 2001:558:feed::1
pi@raspberrypi:/etc $ sudo ping -c 5 2001:558:feed::2
ping: unknown host 2001:558:feed::2
command
pi@raspberrypi:/etc $ /sbin/ip route show dev eth0
default via 10.0.0.1 metric 202
10.0.0.0/24 proto kernel scope link src 10.0.0.91 metric 202

pi@raspberrypi:/etc $ /sbin/ip -6 route show dev eth0
2601:483:200:6dfc::/64 proto kernel metric 202
fe80::/64 proto kernel metric 256
default via fe80::7454:7dff:fe9f:ab0d metric 202

Comcast modem is:
Made by Cisco
I don't see a model number anywhere
on front is says XB3 and Xfinity.
It does have modem for 2.4 and also 5.0 networks.
I only one unit that will connect to the 5.0, a new
type Samsung Tablet, all the rest of my network units
only see the 2.4 wi-fi network.

I hope this helps us get past this, and I will be keeping these
emails for reference. Also I hope I can use what ever we find
for Raspian Jessie on the Ubuntu Mate which seem to be operating
the same way. I much prefer the look and feel of that OS on the
Rpi.

Marty

PS: I am going to trim some of the parts of the below copy.

On 04/30/2016 10:46 AM, David Ranch dranch@trinnet.net
[Raspberry_Pi_4-Ham_RADIO] wrote:


Hello Marty, G4SRA, etc,

cat /etc/gai.conf
cat /etc/host.conf


command traceroute -I 8.8.8.8 >> net1
Your previous email indicated that this didn't go anywhere. Let's
see if you can traceroute to an IPv6 address. Please run the
following command and send us the results:

#traceroutes to one of your comcast DNS servers
traceroute 2001:558:feed::2

#traceroute a google public DNS server
traceroute 2001:4860:4860::8888


command cat /etc/resolv.conf >> net1

# Generated by resolvconf

domain hsd1.tn.comcast.net

nameserver 75.75.75.75

nameserver 75.75.76.76

nameserver 2001:558:feed::1

nameserver 2001:558:feed::2
Let's see if you can ping these remote DNS servers. Run the following
commands and post the responses:

ping -c 5 75.75.75.75
ping -c 5 75.75.76.76
ping -c 5 2001:558:feed::1
ping -c 5 2001:558:feed::2



command route -n >> net1
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.0.0.1 0.0.0.0 UG 202 0 0 eth0
10.0.0.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0
This is only showing us the IPv4 default gateway. Please run the
following commands to show the IPv4 and IPv6 gateways:

/sbin/ip route show dev eth0
/sbin/ip -6 route show dev eth0

Join RaspberryPi-4-HamRadio@groups.io to automatically receive all group messages.