[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] Is master supposed to be clean?
From: |
Eric S. Raymond |
Subject: |
Re: [gpsd-dev] Is master supposed to be clean? |
Date: |
Wed, 20 Apr 2016 18:42:44 -0400 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
Gary E. Miller <address@hidden>:
> Yo Eric!
>
> On Wed, 20 Apr 2016 18:11:03 -0400
> "Eric S. Raymond" <address@hidden> wrote:
>
> > Gary E. Miller <address@hidden>:
> > > Does you Pi show IPv6 in: ip addr?
> >
> > No.
>
> Ooops. When IPv6 enabled you should have at a minimum a link local
> IPv6 address auto assigned.
>
> Hree is how my pi looks:
>
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
> qlen 1000
> link/ether b8:27:eb:18:89:b5 brd ff:ff:ff:ff:ff:ff
> inet 204.17.205.17/24 brd 204.17.205.255 scope global eth0
> valid_lft forever preferred_lft forever
> inet6 2001:470:e815:0:ba27:ebff:fe18:89b5/64 scope global dynamic
> valid_lft 86390sec preferred_lft 14390sec
> inet6 fe80::ba27:ebff:fe18:89b5/64 scope link
> valid_lft forever preferred_lft forever
>
>
> The fe80:... should ALWAYS be there automagically.
Here's what mine looks like:
eth0 Link encap:Ethernet HWaddr b8:27:eb:05:b3:29
inet addr:192.168.1.23 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:80119 errors:0 dropped:0 overruns:0 frame:0
TX packets:40992 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:118201905 (112.7 MiB) TX bytes:3329761 (3.1 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:69 errors:0 dropped:0 overruns:0 frame:0
TX packets:69 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5728 (5.5 KiB) TX bytes:5728 (5.5 KiB)
wlan0 Link encap:Ethernet HWaddr b8:27:eb:50:e6:7c
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:34 errors:0 dropped:24 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7747 (7.5 KiB) TX bytes:570 (570.0 B)
> The other one, the 2001:470:815:... is my IPv6 net block. It should
> also be there automagically if you have a local IPv6 router and you do
> not disable it. You should never diable it.
>
> > OK, I think I just figured out what my mistake was. I changed
> > interfaces to declare a fixed static IPv4 address as part of
> > telling the Pi to run headless, then didn't declare an IPv6 address.
> > I'll try fixing that.
I found a document that made me think adding "iface eth0 inet6 auto"
would fix this. It didn't.
> As I said, this should be automatic, at least the FE80: one. If you
> did something to prevent that, then don't do that.
The only way I've messed with the networking (that I know of) is
by removing network-manager and declaring static addresses in
/etc/network/interfaces:
# interfaces(5) file used by ifup(8) and ifdown(8)
# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 192.168.1.23
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
dns-nameservers 192.168.1.1
allow-hotplug wlan0
iface wlan0 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
allow-hotplug wlan1
iface wlan1 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
If there's some magic I need to add, educate me.
I also removed these packages:
# apt-get -y remove --purge xserver-common
# apt-get -y remove --purge x11-common
# apt-get -y remove --purge gnome-icon-theme
# apt-get -y remove --purge gnome-themes-standard
# apt-get -y remove --purge penguinspuzzle
# apt-get -y remove --purge desktop-base
# apt-get -y remove --purge desktop-file-utils
# apt-get -y remove --purge hicolor-icon-theme
# apt-get -y remove --purge raspberrypi-artwork
# apt-get -y remove --purge omxplayer
# apt-get -y remove --purge bluez
# apt-get -y remove --purge avahi-daemon
# apt-get -y remove --purge triggerhappy
# apt-get -y autoremove
# apt-get -y update
Could removing avahi-daemon have done it?
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
signature.asc
Description: Digital signature
- [gpsd-dev] Is master supposed to be clean?, Hal Murray, 2016/04/20
- Re: [gpsd-dev] Is master supposed to be clean?, Eric S. Raymond, 2016/04/20
- Re: [gpsd-dev] Is master supposed to be clean?, Gary E. Miller, 2016/04/20
- Re: [gpsd-dev] Is master supposed to be clean?, Eric S. Raymond, 2016/04/20
- Re: [gpsd-dev] Is master supposed to be clean?, Gary E. Miller, 2016/04/20
- Re: [gpsd-dev] Is master supposed to be clean?, Eric S. Raymond, 2016/04/20
- Re: [gpsd-dev] Is master supposed to be clean?, Gary E. Miller, 2016/04/20
- Re: [gpsd-dev] Is master supposed to be clean?,
Eric S. Raymond <=
- Re: [gpsd-dev] Is master supposed to be clean?, Frank Nicholas, 2016/04/20
- Re: [gpsd-dev] Is master supposed to be clean?, Gary E. Miller, 2016/04/20
Re: [gpsd-dev] Is master supposed to be clean?, Gary E. Miller, 2016/04/20