Re: [CentOS] RAID questions

[John R Pierce]

On 2/16/2017 9:18 PM, Keith Keller wrote:

On 2017-02-15, John R Pierce  wrote:

On 2/14/2017 4:48 PM,tdu...@palmettoshopper.com  wrote:


3 - Can additional drive(s) be added later with a changein RAID level
without current data loss?

Only some systems support that sort of restriping, and its a dangerous
activity (if the power fails or system crashes midway through the
restriping operation, its probably not restartable, you quite likely
will lose the whole volume)

Doesn't mdraid support changing RAID levels?  I think it will even do it
reasonably safely (though still better not to have a power failure!).  I
have a vague memory of adding a drive to a RAID5 and converting it to a
RAID6 but I could be misremembering.


any such operation requires the entire raid to be re-slivered, stripe by 
stripe, as ALL the data moves around. on a large raid made from 
multi-terabyte drives, this would take DAYS.



--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] RAID questions

[Keith Keller]

On 2017-02-15, John R Pierce  wrote:
> On 2/14/2017 4:48 PM, tdu...@palmettoshopper.com wrote:
>
>> 3 - Can additional drive(s) be added later with a changein RAID level
>> without current data loss?
>
> Only some systems support that sort of restriping, and its a dangerous 
> activity (if the power fails or system crashes midway through the 
> restriping operation, its probably not restartable, you quite likely 
> will lose the whole volume)

Doesn't mdraid support changing RAID levels?  I think it will even do it
reasonably safely (though still better not to have a power failure!).  I
have a vague memory of adding a drive to a RAID5 and converting it to a
RAID6 but I could be misremembering.

--keith

-- 
kkel...@wombat.san-francisco.ca.us


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] USB 2.0 device on a USB 3.0 plug

[Gordon Messmer]

On 02/16/2017 01:20 PM, John R Pierce wrote:
look very closely at a USB 3.0 port, with the 'blue' tongued A 
connector, and you'll see 5 additional pins in there behind the 
standard USB1/2 4 pins. 



I will be a monkey's uncle.  Thanks for the pointers.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] GCC 4.9 in CentOS 7 ??

[Gordon Messmer]

On 02/16/2017 04:45 PM, Dave Johansen wrote:

The source RPMs for devtoolset don't appear to be there, but I did find
them here:
http://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/RHSCL/SRPMS/



Possibly a result of an unspecified "accident"

https://lists.centos.org/pipermail/centos-devel/2017-February/015676.html

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] GCC 4.9 in CentOS 7 ??

[Dave Johansen]

On Sun, Feb 5, 2017 at 11:43 PM, Gordon Messmer 
wrote:

> On 02/05/2017 06:37 PM, Alice Wonder wrote:
>
>> Where are src.rpm's ?
>>
>
>
> Same place as everything else:
>
> http://vault.centos.org/7.3.1611/sclo/Source/


The source RPMs for devtoolset don't appear to be there, but I did find
them here:
http://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/RHSCL/SRPMS/
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] USB 2.0 device on a USB 3.0 plug

[John R Pierce]

On 2/16/2017 1:12 PM, Gordon Messmer wrote:

On 02/16/2017 12:28 PM, John R Pierce wrote:
USB 1 and 2 used 4 pins.USB 3 ports have an ADDITIONAL 5 pins, 
the original 4 are used for USB 1/2 operation, the new 5 only for USB 
3 operation.   they are effectively two completely independent 
controllers. 



Do you mean USB type C?  USB 3 is supported and most commonly uses 
type A plugs & ports, which should support older devices. 


look very closely at a USB 3.0 port, with the 'blue' tongued A 
connector, and you'll see 5 additional pins in there behind the standard 
USB1/2 4 pins.


https://files.cablewholesale.com/mailimages/usb-30-type-a-connector-det-small.jpg 
(male)


http://p.globalsources.com/IMAGES/PDT/BIG/663/B1079644663.jpg (female)


--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] USB 2.0 device on a USB 3.0 plug

[Gordon Messmer]

On 02/16/2017 12:28 PM, John R Pierce wrote:
USB 1 and 2 used 4 pins.USB 3 ports have an ADDITIONAL 5 pins, the 
original 4 are used for USB 1/2 operation, the new 5 only for USB 3 
operation.   they are effectively two completely independent controllers. 



Do you mean USB type C?  USB 3 is supported and most commonly uses type 
A plugs & ports, which should support older devices.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] USB 2.0 device on a USB 3.0 plug

[John R Pierce]

On 2/16/2017 9:58 AM, Jerry Geis wrote:

When I plug in my device which is USB 2.0 into a 3.0 slot (cause that is
all I have)
[495042.943074] usb 5-2: new low-speed USB device number 6 using xhci_hcd
[495043.100076] usb 5-2: device descriptor read/64, error -71

I receive the above error.

Is there a flag or setting that tells the USB to in a 2.0 mode ?


USB 1 and 2 used 4 pins.USB 3 ports have an ADDITIONAL 5 pins, the 
original 4 are used for USB 1/2 operation, the new 5 only for USB 3 
operation.   they are effectively two completely independent controllers.


the combined protocol stack is an unholy mess of poorly planned extensions.


--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] USB 2.0 device on a USB 3.0 plug

[Fred Smith]

On Thu, Feb 16, 2017 at 12:58:09PM -0500, Jerry Geis wrote:
> When I plug in my device which is USB 2.0 into a 3.0 slot (cause that is
> all I have)
> [495042.943074] usb 5-2: new low-speed USB device number 6 using xhci_hcd
> [495043.100076] usb 5-2: device descriptor read/64, error -71
> 
> I receive the above error.
> 
> Is there a flag or setting that tells the USB to in a 2.0 mode ?

I'm no expert, and I don't know the answer, here is an idea: are you
using a USB3 cable for this? If so, might it be worth trying a USB2
cable instead?

Also, are you sure that the device itself is working correctly? Try
it on a different system on usb2 and usb3? try it on this same system
in a usb2 port (temporarily, since you have no spare usb2 ports).

Fred
-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
"Not everyone who says to me, 'Lord, Lord,' will enter the kingdom of
 heaven, but only he who does the will of my Father who is in heaven."
-- Matthew 7:21 (niv) -
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] USB 2.0 device on a USB 3.0 plug

[Jerry Geis]

When I plug in my device which is USB 2.0 into a 3.0 slot (cause that is
all I have)
[495042.943074] usb 5-2: new low-speed USB device number 6 using xhci_hcd
[495043.100076] usb 5-2: device descriptor read/64, error -71

I receive the above error.

Is there a flag or setting that tells the USB to in a 2.0 mode ?

Thanks,

Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] About the flash-plugin

[m . roth]

Istimsak Abdulbasir wrote:
> On Wed, Feb 15, 2017 at 4:39 PM,  wrote:
>
>> Y'all may remember I posted here weeks ago, that flash-plugin was
>> crashing. There was an update this morning, which I did on my
>> workstation... and it hasn't crashed all day on either of the two radio
>> stations who I listen to via streaming media.
>>
>> That is good news. What station are you listening to?
>
Same as I was last month: kut.edu, UT at Austin, and wqxr.org, a radio
station out of NYC.

 mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] About the flash-plugin

[Istimsak Abdulbasir]

On Wed, Feb 15, 2017 at 4:39 PM,  wrote:

> Y'all may remember I posted here weeks ago, that flash-plugin was
> crashing. There was an update this morning, which I did on my
> workstation... and it hasn't crashed all day on either of the two radio
> stations who I listen to via streaming media.
>
>   mark
>
> That is good news. What station are you listening to?

> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>



-- 
"Collaboration is the new innovation" (Istimsak Abdulbasir, 2016)
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] IPv6 broken on Linode

[Alice Wonder]

On 02/16/2017 04:34 AM, Alice Wonder wrote:

On 02/16/2017 04:20 AM, James Hogarth wrote:

On 16 February 2017 at 12:02, James Hogarth 
wrote:

On 16 February 2017 at 11:46, James Hogarth 
wrote:

On 16 February 2017 at 11:35, Alice Wonder 
wrote:

On 02/16/2017 03:28 AM, James Hogarth wrote:


On 16 February 2017 at 10:42, Alice Wonder 
wrote:


On 02/16/2017 02:32 AM, James Hogarth wrote:



On 16 February 2017 at 10:17, Alice Wonder
 wrote:



On 02/16/2017 02:03 AM, James Hogarth wrote:




On 16 February 2017 at 09:09, Alice Wonder 
wrote:




On 02/16/2017 12:54 AM, Tony Mountifield wrote:





In article
<4cbb9dc4-f063-3434-b7a1-d4d0e6581...@domblogger.net>,
Alice Wonder  wrote:





https://forum.linode.com/viewtopic.php?f=19=14570=72785

I can not figure out what I need to do.

Apparently according to linode support, the VM is trying to
grab an
IPv6
address with some privacy stuff enabled by default causing
it to
not
grab the IPv6 address that is assigned to me.






Does the accepted answer at the following link give you any
useful
hints?





http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-when-using-ipv6


Cheers
Tony



Not really - I tried

net.ipv6.conf.all.use_tempaddr = 0

and it still fails to grab the proper IPv6

-=-

Just in case, I did ask Linode support to verify that my
hardware
address
is
what it is suppose to be. Still waiting to hear on that.

___






it still is key=value  ... it uses the ifcfg- files (via the rh
plugin) and they are all key=value

It would be helpful if you could paste the journal output
(journalctl
-u NetworkManager) from the time period of attempting to get an
address ...

also the nmcli conn sh  information for the
interface
along with your ifcfg- files





ifcfg-lo is the only one that exists on any of the servers -
including
the
VMs that grab the correct IPv6 address.

from /sbin/ifconfig -a :



For a start stop using ifconfig ... it's broken at this point on
linux, especially on multi ip and ipv6 scenarios

Use `ip -6 addr sh` for ipv6 specfic stuff, or just ip addr sh
to see
all IP address stuff regardless of family


eth0: flags=4163  mtu 1500
inet 178.79.185.217  netmask 255.255.255.0  broadcast
178.79.185.255
inet6 fe80::a8ad:d312:4ef4:7272  prefixlen 64  scopeid
0x20
inet6 2a01:7e00::825f:e564:ad53:72fc  prefixlen 64
scopeid
0x0
ether f2:3c:91:18:8a:7e  txqueuelen 1000  (Ethernet)
RX packets 9903  bytes 1088621 (1.0 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 7786  bytes 1087223 (1.0 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

That hardware address - the 18:8a:7e corresponds with what the
IPv6
address
is suppose to be. But that's not the address it is grabbing,
despite
the
fact that net.ipv6.conf.all.use_tempaddr = 0 is set.

I'm seriously wondering if the real issue is a mis-configured dhcp
server
in
their London facility because nothing makes sense.

journalctl -u NetworkManager

reports no journal entries found.



So are you not using NetworkManager then? there should be some
logs ...



I think the problem must be on their end.

It all was working fine until they migrated the VM because of a
hardware
issue, and I suspect now all the hardware address privacy stuff
being
the
issue is barking up the wrong tree because all the reading I
have done
seems
to indicate that with

net.ipv6.conf.all.use_tempaddr = 0

that a fake temporary hardware address would not be sent to
their dhcp
server when obtaining the address, but the real one, that
should be
fetching
my assigned address.




Only if the kernel is doing SLAAC ... if other things (eg NM) are
handling it directly they may act differently ... but then from the
lack of logs is NM actually handling this?

Does systemctl status NetworkManager show it running and does nmcli
show anything?



systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service;
enabled;
vendor preset: enabled)
   Active: active (running) since Thu 2017-02-16 08:19:34 UTC; 2h
19min
ago

* more stuff *

nmcli
eth0: connected to Wired connection 1
"Red Hat Virtio network device"
ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500
ip4 default, ip6 default
inet4 178.79.185.217/24
route4 178.79.187.246/32
inet6 2a01:7e00::825f:e564:ad53:72fc/64
inet6 fe80::a8ad:d312:4ef4:7272/64
route6 2a01:7e00::/64

* more stuff for other interfaces *

-=-

The output of

sysctl -a | grep net.ipv6 :

https://librelamp.com/sysctl.txt

It looks from that like it should not be hiding the real MAC
address.




do nmcli conn show "Wired 

Re: [CentOS] IPv6 broken on Linode

[Alice Wonder]

On 02/16/2017 04:20 AM, James Hogarth wrote:

On 16 February 2017 at 12:02, James Hogarth  wrote:

On 16 February 2017 at 11:46, James Hogarth  wrote:

On 16 February 2017 at 11:35, Alice Wonder  wrote:

On 02/16/2017 03:28 AM, James Hogarth wrote:


On 16 February 2017 at 10:42, Alice Wonder  wrote:


On 02/16/2017 02:32 AM, James Hogarth wrote:



On 16 February 2017 at 10:17, Alice Wonder  wrote:



On 02/16/2017 02:03 AM, James Hogarth wrote:




On 16 February 2017 at 09:09, Alice Wonder 
wrote:




On 02/16/2017 12:54 AM, Tony Mountifield wrote:





In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581...@domblogger.net>,
Alice Wonder  wrote:





https://forum.linode.com/viewtopic.php?f=19=14570=72785

I can not figure out what I need to do.

Apparently according to linode support, the VM is trying to grab an
IPv6
address with some privacy stuff enabled by default causing it to
not
grab the IPv6 address that is assigned to me.






Does the accepted answer at the following link give you any useful
hints?





http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-when-using-ipv6

Cheers
Tony



Not really - I tried

net.ipv6.conf.all.use_tempaddr = 0

and it still fails to grab the proper IPv6

-=-

Just in case, I did ask Linode support to verify that my hardware
address
is
what it is suppose to be. Still waiting to hear on that.

___






it still is key=value  ... it uses the ifcfg- files (via the rh
plugin) and they are all key=value

It would be helpful if you could paste the journal output (journalctl
-u NetworkManager) from the time period of attempting to get an
address ...

also the nmcli conn sh  information for the interface
along with your ifcfg- files





ifcfg-lo is the only one that exists on any of the servers - including
the
VMs that grab the correct IPv6 address.

from /sbin/ifconfig -a :



For a start stop using ifconfig ... it's broken at this point on
linux, especially on multi ip and ipv6 scenarios

Use `ip -6 addr sh` for ipv6 specfic stuff, or just ip addr sh to see
all IP address stuff regardless of family


eth0: flags=4163  mtu 1500
inet 178.79.185.217  netmask 255.255.255.0  broadcast
178.79.185.255
inet6 fe80::a8ad:d312:4ef4:7272  prefixlen 64  scopeid
0x20
inet6 2a01:7e00::825f:e564:ad53:72fc  prefixlen 64  scopeid
0x0
ether f2:3c:91:18:8a:7e  txqueuelen 1000  (Ethernet)
RX packets 9903  bytes 1088621 (1.0 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 7786  bytes 1087223 (1.0 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

That hardware address - the 18:8a:7e corresponds with what the IPv6
address
is suppose to be. But that's not the address it is grabbing, despite
the
fact that net.ipv6.conf.all.use_tempaddr = 0 is set.

I'm seriously wondering if the real issue is a mis-configured dhcp
server
in
their London facility because nothing makes sense.

journalctl -u NetworkManager

reports no journal entries found.



So are you not using NetworkManager then? there should be some logs ...



I think the problem must be on their end.

It all was working fine until they migrated the VM because of a
hardware
issue, and I suspect now all the hardware address privacy stuff being
the
issue is barking up the wrong tree because all the reading I have done
seems
to indicate that with

net.ipv6.conf.all.use_tempaddr = 0

that a fake temporary hardware address would not be sent to their dhcp
server when obtaining the address, but the real one, that should be
fetching
my assigned address.




Only if the kernel is doing SLAAC ... if other things (eg NM) are
handling it directly they may act differently ... but then from the
lack of logs is NM actually handling this?

Does systemctl status NetworkManager show it running and does nmcli
show anything?



systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service;
enabled;
vendor preset: enabled)
   Active: active (running) since Thu 2017-02-16 08:19:34 UTC; 2h 19min
ago

* more stuff *

nmcli
eth0: connected to Wired connection 1
"Red Hat Virtio network device"
ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500
ip4 default, ip6 default
inet4 178.79.185.217/24
route4 178.79.187.246/32
inet6 2a01:7e00::825f:e564:ad53:72fc/64
inet6 fe80::a8ad:d312:4ef4:7272/64
route6 2a01:7e00::/64

* more stuff for other interfaces *

-=-

The output of

sysctl -a | grep net.ipv6 :

https://librelamp.com/sysctl.txt

It looks from that like it should not be hiding the real MAC address.




do nmcli conn show "Wired connection 1"

the entries of interest are:

Re: [CentOS] IPv6 broken on Linode

[James Hogarth]

On 16 February 2017 at 12:02, James Hogarth  wrote:
> On 16 February 2017 at 11:46, James Hogarth  wrote:
>> On 16 February 2017 at 11:35, Alice Wonder  wrote:
>>> On 02/16/2017 03:28 AM, James Hogarth wrote:

 On 16 February 2017 at 10:42, Alice Wonder  wrote:
>
> On 02/16/2017 02:32 AM, James Hogarth wrote:
>>
>>
>> On 16 February 2017 at 10:17, Alice Wonder  wrote:
>>>
>>>
>>> On 02/16/2017 02:03 AM, James Hogarth wrote:



 On 16 February 2017 at 09:09, Alice Wonder 
 wrote:
>
>
>
> On 02/16/2017 12:54 AM, Tony Mountifield wrote:
>>
>>
>>
>>
>> In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581...@domblogger.net>,
>> Alice Wonder  wrote:
>>>
>>>
>>>
>>>
>>> https://forum.linode.com/viewtopic.php?f=19=14570=72785
>>>
>>> I can not figure out what I need to do.
>>>
>>> Apparently according to linode support, the VM is trying to grab an
>>> IPv6
>>> address with some privacy stuff enabled by default causing it to
>>> not
>>> grab the IPv6 address that is assigned to me.
>>
>>
>>
>>
>>
>> Does the accepted answer at the following link give you any useful
>> hints?
>>
>>
>>
>>
>>
>> http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-when-using-ipv6
>>
>> Cheers
>> Tony
>>
>
> Not really - I tried
>
> net.ipv6.conf.all.use_tempaddr = 0
>
> and it still fails to grab the proper IPv6
>
> -=-
>
> Just in case, I did ask Linode support to verify that my hardware
> address
> is
> what it is suppose to be. Still waiting to hear on that.
>
> ___





 it still is key=value  ... it uses the ifcfg- files (via the rh
 plugin) and they are all key=value

 It would be helpful if you could paste the journal output (journalctl
 -u NetworkManager) from the time period of attempting to get an
 address ...

 also the nmcli conn sh  information for the interface
 along with your ifcfg- files
>>>
>>>
>>>
>>>
>>> ifcfg-lo is the only one that exists on any of the servers - including
>>> the
>>> VMs that grab the correct IPv6 address.
>>>
>>> from /sbin/ifconfig -a :
>>>
>>
>> For a start stop using ifconfig ... it's broken at this point on
>> linux, especially on multi ip and ipv6 scenarios
>>
>> Use `ip -6 addr sh` for ipv6 specfic stuff, or just ip addr sh to see
>> all IP address stuff regardless of family
>>
>>> eth0: flags=4163  mtu 1500
>>> inet 178.79.185.217  netmask 255.255.255.0  broadcast
>>> 178.79.185.255
>>> inet6 fe80::a8ad:d312:4ef4:7272  prefixlen 64  scopeid
>>> 0x20
>>> inet6 2a01:7e00::825f:e564:ad53:72fc  prefixlen 64  scopeid
>>> 0x0
>>> ether f2:3c:91:18:8a:7e  txqueuelen 1000  (Ethernet)
>>> RX packets 9903  bytes 1088621 (1.0 MiB)
>>> RX errors 0  dropped 0  overruns 0  frame 0
>>> TX packets 7786  bytes 1087223 (1.0 MiB)
>>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>>
>>> That hardware address - the 18:8a:7e corresponds with what the IPv6
>>> address
>>> is suppose to be. But that's not the address it is grabbing, despite
>>> the
>>> fact that net.ipv6.conf.all.use_tempaddr = 0 is set.
>>>
>>> I'm seriously wondering if the real issue is a mis-configured dhcp
>>> server
>>> in
>>> their London facility because nothing makes sense.
>>>
>>> journalctl -u NetworkManager
>>>
>>> reports no journal entries found.
>>>
>>
>> So are you not using NetworkManager then? there should be some logs ...
>>
>>
>>> I think the problem must be on their end.
>>>
>>> It all was working fine until they migrated the VM because of a
>>> hardware
>>> issue, and I suspect now all the hardware address privacy stuff being
>>> the
>>> issue is barking up the wrong tree because all the reading I have done
>>> seems
>>> to indicate that with
>>>
>>> net.ipv6.conf.all.use_tempaddr = 0
>>>
>>> that a fake temporary hardware address would not be sent to their dhcp
>>> server when obtaining the address, but the real one, that should be

Re: [CentOS] IPv6 broken on Linode

[James Hogarth]

On 16 February 2017 at 11:46, James Hogarth  wrote:
> On 16 February 2017 at 11:35, Alice Wonder  wrote:
>> On 02/16/2017 03:28 AM, James Hogarth wrote:
>>>
>>> On 16 February 2017 at 10:42, Alice Wonder  wrote:

 On 02/16/2017 02:32 AM, James Hogarth wrote:
>
>
> On 16 February 2017 at 10:17, Alice Wonder  wrote:
>>
>>
>> On 02/16/2017 02:03 AM, James Hogarth wrote:
>>>
>>>
>>>
>>> On 16 February 2017 at 09:09, Alice Wonder 
>>> wrote:



 On 02/16/2017 12:54 AM, Tony Mountifield wrote:
>
>
>
>
> In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581...@domblogger.net>,
> Alice Wonder  wrote:
>>
>>
>>
>>
>> https://forum.linode.com/viewtopic.php?f=19=14570=72785
>>
>> I can not figure out what I need to do.
>>
>> Apparently according to linode support, the VM is trying to grab an
>> IPv6
>> address with some privacy stuff enabled by default causing it to
>> not
>> grab the IPv6 address that is assigned to me.
>
>
>
>
>
> Does the accepted answer at the following link give you any useful
> hints?
>
>
>
>
>
> http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-when-using-ipv6
>
> Cheers
> Tony
>

 Not really - I tried

 net.ipv6.conf.all.use_tempaddr = 0

 and it still fails to grab the proper IPv6

 -=-

 Just in case, I did ask Linode support to verify that my hardware
 address
 is
 what it is suppose to be. Still waiting to hear on that.

 ___
>>>
>>>
>>>
>>>
>>>
>>> it still is key=value  ... it uses the ifcfg- files (via the rh
>>> plugin) and they are all key=value
>>>
>>> It would be helpful if you could paste the journal output (journalctl
>>> -u NetworkManager) from the time period of attempting to get an
>>> address ...
>>>
>>> also the nmcli conn sh  information for the interface
>>> along with your ifcfg- files
>>
>>
>>
>>
>> ifcfg-lo is the only one that exists on any of the servers - including
>> the
>> VMs that grab the correct IPv6 address.
>>
>> from /sbin/ifconfig -a :
>>
>
> For a start stop using ifconfig ... it's broken at this point on
> linux, especially on multi ip and ipv6 scenarios
>
> Use `ip -6 addr sh` for ipv6 specfic stuff, or just ip addr sh to see
> all IP address stuff regardless of family
>
>> eth0: flags=4163  mtu 1500
>> inet 178.79.185.217  netmask 255.255.255.0  broadcast
>> 178.79.185.255
>> inet6 fe80::a8ad:d312:4ef4:7272  prefixlen 64  scopeid
>> 0x20
>> inet6 2a01:7e00::825f:e564:ad53:72fc  prefixlen 64  scopeid
>> 0x0
>> ether f2:3c:91:18:8a:7e  txqueuelen 1000  (Ethernet)
>> RX packets 9903  bytes 1088621 (1.0 MiB)
>> RX errors 0  dropped 0  overruns 0  frame 0
>> TX packets 7786  bytes 1087223 (1.0 MiB)
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>
>> That hardware address - the 18:8a:7e corresponds with what the IPv6
>> address
>> is suppose to be. But that's not the address it is grabbing, despite
>> the
>> fact that net.ipv6.conf.all.use_tempaddr = 0 is set.
>>
>> I'm seriously wondering if the real issue is a mis-configured dhcp
>> server
>> in
>> their London facility because nothing makes sense.
>>
>> journalctl -u NetworkManager
>>
>> reports no journal entries found.
>>
>
> So are you not using NetworkManager then? there should be some logs ...
>
>
>> I think the problem must be on their end.
>>
>> It all was working fine until they migrated the VM because of a
>> hardware
>> issue, and I suspect now all the hardware address privacy stuff being
>> the
>> issue is barking up the wrong tree because all the reading I have done
>> seems
>> to indicate that with
>>
>> net.ipv6.conf.all.use_tempaddr = 0
>>
>> that a fake temporary hardware address would not be sent to their dhcp
>> server when obtaining the address, but the real one, that should be
>> fetching
>> my assigned address.
>
>
>
> Only if the kernel is doing SLAAC ... if other things (eg NM) are
> handling it directly they may act differently ... but then from the
> lack of logs 

[CentOS] CentOS-announce Digest, Vol 144, Issue 5

[centos-announce-request]

Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. CEBA-2017:0274  CentOS 5 kernel BugFix Update (Johnny Hughes)
   2. CESA-2017:0276 Moderate CentOS 7 bind SecurityUpdate
  (Johnny Hughes)


--

Message: 1
Date: Wed, 15 Feb 2017 13:14:42 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CEBA-2017:0274  CentOS 5 kernel BugFix
Update
Message-ID: <20170215131442.ga8...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Bugfix Advisory 2017:0274 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-0274.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
5eeff3ee579f570ec49233bf04caa335af2375ffacbc46dae45826e5f9b70748  
kernel-2.6.18-418.el5.i686.rpm
9f674e2c212f4ed8b85452682f0d08814580eebb188cbc492e66932dde518338  
kernel-debug-2.6.18-418.el5.i686.rpm
bfa94e23b90d87f1241391d4354425000cb28fb71c516c6db43ad948d0f23400  
kernel-debug-devel-2.6.18-418.el5.i686.rpm
181c671e7fb6fa4576b52c3a23c69222e8915fec78279ca7b0ca9b17e7fbf593  
kernel-devel-2.6.18-418.el5.i686.rpm
03a9c5df55efc1a9fb0268e77b929fda5974661529bd12b3a76908ef9cbe1ca1  
kernel-doc-2.6.18-418.el5.noarch.rpm
b37bf6415c42abf09ecbb75c145090e175bc3494c41c0c32e91e637cbcd55e46  
kernel-headers-2.6.18-418.el5.i386.rpm
bd2c2051d500bf3a77d37eaf5bc3fd50945ea4729c0ce146052a8390bac2ba46  
kernel-PAE-2.6.18-418.el5.i686.rpm
f7d8ec73731cdbc7a45a408fcdec5a58ddb5ecacbc88c145ddd07a9bd7565eb2  
kernel-PAE-devel-2.6.18-418.el5.i686.rpm
70969578c772dd985fd97721c208a2a4dc4ff7fa480fd95c7a233890730df58c  
kernel-xen-2.6.18-418.el5.i686.rpm
1479b4c750af9b2061997c76366ed7a45bfe6055174d4c880012f79d67e437a8  
kernel-xen-devel-2.6.18-418.el5.i686.rpm

x86_64:
583c518288691608947e8a769a31331bb1574065ccbe46ece4903ecdabf60aa6  
kernel-2.6.18-418.el5.x86_64.rpm
466872dd2c61bb6dcffcbeb5839eb772c9f7272b552f7d8a8903cc95a6024f8a  
kernel-debug-2.6.18-418.el5.x86_64.rpm
353e4c5e338979dbb63fb415323e7d613c4b1be04626c6d39d27b03ac1a86a08  
kernel-debug-devel-2.6.18-418.el5.x86_64.rpm
cf2f965ca2219ad25a836261e28328d7c881204788f91ee2ff66389ac4ee9b2f  
kernel-devel-2.6.18-418.el5.x86_64.rpm
03a9c5df55efc1a9fb0268e77b929fda5974661529bd12b3a76908ef9cbe1ca1  
kernel-doc-2.6.18-418.el5.noarch.rpm
358bbaf90801ad08686df5c6de9f4ce17338abea531a23a87a9c913319abc884  
kernel-headers-2.6.18-418.el5.x86_64.rpm
cc2836181bfd15f0d65406204d2323a3fd17a7ea6a43a8af889ef210256a7410  
kernel-xen-2.6.18-418.el5.x86_64.rpm
e35eeb4cd3d0ef2bfeec3e47735e2e7f1475f7597db9f8433531d1b8ea4e8478  
kernel-xen-devel-2.6.18-418.el5.x86_64.rpm

Source:
9785160c0ab76993df6bdc5ec04362df88ad98e8492d6bdd1107872c6e490a64  
kernel-2.6.18-418.el5.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: JohnnyCentOS



--

Message: 2
Date: Wed, 15 Feb 2017 14:49:31 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2017:0276 Moderate CentOS 7 bind
SecurityUpdate
Message-ID: <20170215144931.ga63...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2017:0276 Moderate

Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0276.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
78da78be03829d07f7ddd5bf6fde8fb873ae21fda0ca931eb01e251351d0e0d4  
bind-9.9.4-38.el7_3.2.x86_64.rpm
0a4048a4c3afc0656da2ea3d9f67467c3bb13aef795169a831e20be62973cb3b  
bind-chroot-9.9.4-38.el7_3.2.x86_64.rpm
3edf4863b3265a5ffb6f96e33e0b70cf00f63f632060de6946a98e1f5d6abd4f  
bind-devel-9.9.4-38.el7_3.2.i686.rpm
db587a93bb81fc8471f85f852d6a5e1b68ccae8b1518dcd6aee0bb789ee39609  
bind-devel-9.9.4-38.el7_3.2.x86_64.rpm
2f80f485510682611829cf0b00dbba5ed8858ea6862dc37278cc0df4dc965964  
bind-libs-9.9.4-38.el7_3.2.i686.rpm
102cdd935e72edc2c3eb7f3997eb86b66bd88d0db7c3c67481d46be5e33d1032  
bind-libs-9.9.4-38.el7_3.2.x86_64.rpm
93e1824c575495e0d95abbc23155f3039a0fd7af939583eefe8b027101d3c1ae  
bind-libs-lite-9.9.4-38.el7_3.2.i686.rpm
fc482a8e502415088cec63af435d2b00d65176e0f02e78112ac0e110da5bbe7d  
bind-libs-lite-9.9.4-38.el7_3.2.x86_64.rpm
7dd2e52354a0b7bdeb26bcd4bebf4624838854e45a881b8cf9580a6d900aac62  
bind-license-9.9.4-38.el7_3.2.noarch.rpm

Re: [CentOS] IPv6 broken on Linode

[James Hogarth]

On 16 February 2017 at 11:35, Alice Wonder  wrote:
> On 02/16/2017 03:28 AM, James Hogarth wrote:
>>
>> On 16 February 2017 at 10:42, Alice Wonder  wrote:
>>>
>>> On 02/16/2017 02:32 AM, James Hogarth wrote:


 On 16 February 2017 at 10:17, Alice Wonder  wrote:
>
>
> On 02/16/2017 02:03 AM, James Hogarth wrote:
>>
>>
>>
>> On 16 February 2017 at 09:09, Alice Wonder 
>> wrote:
>>>
>>>
>>>
>>> On 02/16/2017 12:54 AM, Tony Mountifield wrote:




 In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581...@domblogger.net>,
 Alice Wonder  wrote:
>
>
>
>
> https://forum.linode.com/viewtopic.php?f=19=14570=72785
>
> I can not figure out what I need to do.
>
> Apparently according to linode support, the VM is trying to grab an
> IPv6
> address with some privacy stuff enabled by default causing it to
> not
> grab the IPv6 address that is assigned to me.





 Does the accepted answer at the following link give you any useful
 hints?





 http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-when-using-ipv6

 Cheers
 Tony

>>>
>>> Not really - I tried
>>>
>>> net.ipv6.conf.all.use_tempaddr = 0
>>>
>>> and it still fails to grab the proper IPv6
>>>
>>> -=-
>>>
>>> Just in case, I did ask Linode support to verify that my hardware
>>> address
>>> is
>>> what it is suppose to be. Still waiting to hear on that.
>>>
>>> ___
>>
>>
>>
>>
>>
>> it still is key=value  ... it uses the ifcfg- files (via the rh
>> plugin) and they are all key=value
>>
>> It would be helpful if you could paste the journal output (journalctl
>> -u NetworkManager) from the time period of attempting to get an
>> address ...
>>
>> also the nmcli conn sh  information for the interface
>> along with your ifcfg- files
>
>
>
>
> ifcfg-lo is the only one that exists on any of the servers - including
> the
> VMs that grab the correct IPv6 address.
>
> from /sbin/ifconfig -a :
>

 For a start stop using ifconfig ... it's broken at this point on
 linux, especially on multi ip and ipv6 scenarios

 Use `ip -6 addr sh` for ipv6 specfic stuff, or just ip addr sh to see
 all IP address stuff regardless of family

> eth0: flags=4163  mtu 1500
> inet 178.79.185.217  netmask 255.255.255.0  broadcast
> 178.79.185.255
> inet6 fe80::a8ad:d312:4ef4:7272  prefixlen 64  scopeid
> 0x20
> inet6 2a01:7e00::825f:e564:ad53:72fc  prefixlen 64  scopeid
> 0x0
> ether f2:3c:91:18:8a:7e  txqueuelen 1000  (Ethernet)
> RX packets 9903  bytes 1088621 (1.0 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 7786  bytes 1087223 (1.0 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> That hardware address - the 18:8a:7e corresponds with what the IPv6
> address
> is suppose to be. But that's not the address it is grabbing, despite
> the
> fact that net.ipv6.conf.all.use_tempaddr = 0 is set.
>
> I'm seriously wondering if the real issue is a mis-configured dhcp
> server
> in
> their London facility because nothing makes sense.
>
> journalctl -u NetworkManager
>
> reports no journal entries found.
>

 So are you not using NetworkManager then? there should be some logs ...


> I think the problem must be on their end.
>
> It all was working fine until they migrated the VM because of a
> hardware
> issue, and I suspect now all the hardware address privacy stuff being
> the
> issue is barking up the wrong tree because all the reading I have done
> seems
> to indicate that with
>
> net.ipv6.conf.all.use_tempaddr = 0
>
> that a fake temporary hardware address would not be sent to their dhcp
> server when obtaining the address, but the real one, that should be
> fetching
> my assigned address.



 Only if the kernel is doing SLAAC ... if other things (eg NM) are
 handling it directly they may act differently ... but then from the
 lack of logs is NM actually handling this?

 Does systemctl status NetworkManager show it running and does nmcli
 show anything?

>>>
>>> systemctl status NetworkManager
>>> ● NetworkManager.service - Network Manager
>>>Loaded: 

Re: [CentOS] IPv6 broken on Linode

[Alice Wonder]

On 02/16/2017 03:28 AM, James Hogarth wrote:

On 16 February 2017 at 10:42, Alice Wonder  wrote:

On 02/16/2017 02:32 AM, James Hogarth wrote:


On 16 February 2017 at 10:17, Alice Wonder  wrote:


On 02/16/2017 02:03 AM, James Hogarth wrote:



On 16 February 2017 at 09:09, Alice Wonder  wrote:



On 02/16/2017 12:54 AM, Tony Mountifield wrote:




In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581...@domblogger.net>,
Alice Wonder  wrote:




https://forum.linode.com/viewtopic.php?f=19=14570=72785

I can not figure out what I need to do.

Apparently according to linode support, the VM is trying to grab an
IPv6
address with some privacy stuff enabled by default causing it to not
grab the IPv6 address that is assigned to me.





Does the accepted answer at the following link give you any useful
hints?




http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-when-using-ipv6

Cheers
Tony



Not really - I tried

net.ipv6.conf.all.use_tempaddr = 0

and it still fails to grab the proper IPv6

-=-

Just in case, I did ask Linode support to verify that my hardware
address
is
what it is suppose to be. Still waiting to hear on that.

___





it still is key=value  ... it uses the ifcfg- files (via the rh
plugin) and they are all key=value

It would be helpful if you could paste the journal output (journalctl
-u NetworkManager) from the time period of attempting to get an
address ...

also the nmcli conn sh  information for the interface
along with your ifcfg- files




ifcfg-lo is the only one that exists on any of the servers - including
the
VMs that grab the correct IPv6 address.

from /sbin/ifconfig -a :



For a start stop using ifconfig ... it's broken at this point on
linux, especially on multi ip and ipv6 scenarios

Use `ip -6 addr sh` for ipv6 specfic stuff, or just ip addr sh to see
all IP address stuff regardless of family


eth0: flags=4163  mtu 1500
inet 178.79.185.217  netmask 255.255.255.0  broadcast
178.79.185.255
inet6 fe80::a8ad:d312:4ef4:7272  prefixlen 64  scopeid 0x20
inet6 2a01:7e00::825f:e564:ad53:72fc  prefixlen 64  scopeid
0x0
ether f2:3c:91:18:8a:7e  txqueuelen 1000  (Ethernet)
RX packets 9903  bytes 1088621 (1.0 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 7786  bytes 1087223 (1.0 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

That hardware address - the 18:8a:7e corresponds with what the IPv6
address
is suppose to be. But that's not the address it is grabbing, despite the
fact that net.ipv6.conf.all.use_tempaddr = 0 is set.

I'm seriously wondering if the real issue is a mis-configured dhcp server
in
their London facility because nothing makes sense.

journalctl -u NetworkManager

reports no journal entries found.



So are you not using NetworkManager then? there should be some logs ...



I think the problem must be on their end.

It all was working fine until they migrated the VM because of a hardware
issue, and I suspect now all the hardware address privacy stuff being the
issue is barking up the wrong tree because all the reading I have done
seems
to indicate that with

net.ipv6.conf.all.use_tempaddr = 0

that a fake temporary hardware address would not be sent to their dhcp
server when obtaining the address, but the real one, that should be
fetching
my assigned address.



Only if the kernel is doing SLAAC ... if other things (eg NM) are
handling it directly they may act differently ... but then from the
lack of logs is NM actually handling this?

Does systemctl status NetworkManager show it running and does nmcli
show anything?



systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: enabled)
   Active: active (running) since Thu 2017-02-16 08:19:34 UTC; 2h 19min ago

* more stuff *

nmcli
eth0: connected to Wired connection 1
"Red Hat Virtio network device"
ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500
ip4 default, ip6 default
inet4 178.79.185.217/24
route4 178.79.187.246/32
inet6 2a01:7e00::825f:e564:ad53:72fc/64
inet6 fe80::a8ad:d312:4ef4:7272/64
route6 2a01:7e00::/64

* more stuff for other interfaces *

-=-

The output of

sysctl -a | grep net.ipv6 :

https://librelamp.com/sysctl.txt

It looks from that like it should not be hiding the real MAC address.




do nmcli conn show "Wired connection 1"

the entries of interest are:

ipv6.ip6-privacy
ipv6.addr-gen-mode

man nm-settings to get what they mean
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



ipv6.ip6-privacy:   -1 (unknown)
ipv6.addr-gen-mode: 

Re: [CentOS] IPv6 broken on Linode

[James Hogarth]

On 16 February 2017 at 10:42, Alice Wonder  wrote:
> On 02/16/2017 02:32 AM, James Hogarth wrote:
>>
>> On 16 February 2017 at 10:17, Alice Wonder  wrote:
>>>
>>> On 02/16/2017 02:03 AM, James Hogarth wrote:


 On 16 February 2017 at 09:09, Alice Wonder  wrote:
>
>
> On 02/16/2017 12:54 AM, Tony Mountifield wrote:
>>
>>
>>
>> In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581...@domblogger.net>,
>> Alice Wonder  wrote:
>>>
>>>
>>>
>>> https://forum.linode.com/viewtopic.php?f=19=14570=72785
>>>
>>> I can not figure out what I need to do.
>>>
>>> Apparently according to linode support, the VM is trying to grab an
>>> IPv6
>>> address with some privacy stuff enabled by default causing it to not
>>> grab the IPv6 address that is assigned to me.
>>
>>
>>
>>
>> Does the accepted answer at the following link give you any useful
>> hints?
>>
>>
>>
>>
>> http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-when-using-ipv6
>>
>> Cheers
>> Tony
>>
>
> Not really - I tried
>
> net.ipv6.conf.all.use_tempaddr = 0
>
> and it still fails to grab the proper IPv6
>
> -=-
>
> Just in case, I did ask Linode support to verify that my hardware
> address
> is
> what it is suppose to be. Still waiting to hear on that.
>
> ___




 it still is key=value  ... it uses the ifcfg- files (via the rh
 plugin) and they are all key=value

 It would be helpful if you could paste the journal output (journalctl
 -u NetworkManager) from the time period of attempting to get an
 address ...

 also the nmcli conn sh  information for the interface
 along with your ifcfg- files
>>>
>>>
>>>
>>> ifcfg-lo is the only one that exists on any of the servers - including
>>> the
>>> VMs that grab the correct IPv6 address.
>>>
>>> from /sbin/ifconfig -a :
>>>
>>
>> For a start stop using ifconfig ... it's broken at this point on
>> linux, especially on multi ip and ipv6 scenarios
>>
>> Use `ip -6 addr sh` for ipv6 specfic stuff, or just ip addr sh to see
>> all IP address stuff regardless of family
>>
>>> eth0: flags=4163  mtu 1500
>>> inet 178.79.185.217  netmask 255.255.255.0  broadcast
>>> 178.79.185.255
>>> inet6 fe80::a8ad:d312:4ef4:7272  prefixlen 64  scopeid 0x20
>>> inet6 2a01:7e00::825f:e564:ad53:72fc  prefixlen 64  scopeid
>>> 0x0
>>> ether f2:3c:91:18:8a:7e  txqueuelen 1000  (Ethernet)
>>> RX packets 9903  bytes 1088621 (1.0 MiB)
>>> RX errors 0  dropped 0  overruns 0  frame 0
>>> TX packets 7786  bytes 1087223 (1.0 MiB)
>>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>>
>>> That hardware address - the 18:8a:7e corresponds with what the IPv6
>>> address
>>> is suppose to be. But that's not the address it is grabbing, despite the
>>> fact that net.ipv6.conf.all.use_tempaddr = 0 is set.
>>>
>>> I'm seriously wondering if the real issue is a mis-configured dhcp server
>>> in
>>> their London facility because nothing makes sense.
>>>
>>> journalctl -u NetworkManager
>>>
>>> reports no journal entries found.
>>>
>>
>> So are you not using NetworkManager then? there should be some logs ...
>>
>>
>>> I think the problem must be on their end.
>>>
>>> It all was working fine until they migrated the VM because of a hardware
>>> issue, and I suspect now all the hardware address privacy stuff being the
>>> issue is barking up the wrong tree because all the reading I have done
>>> seems
>>> to indicate that with
>>>
>>> net.ipv6.conf.all.use_tempaddr = 0
>>>
>>> that a fake temporary hardware address would not be sent to their dhcp
>>> server when obtaining the address, but the real one, that should be
>>> fetching
>>> my assigned address.
>>
>>
>> Only if the kernel is doing SLAAC ... if other things (eg NM) are
>> handling it directly they may act differently ... but then from the
>> lack of logs is NM actually handling this?
>>
>> Does systemctl status NetworkManager show it running and does nmcli
>> show anything?
>>
>
> systemctl status NetworkManager
> ● NetworkManager.service - Network Manager
>Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled;
> vendor preset: enabled)
>Active: active (running) since Thu 2017-02-16 08:19:34 UTC; 2h 19min ago
>
> * more stuff *
>
> nmcli
> eth0: connected to Wired connection 1
> "Red Hat Virtio network device"
> ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500
> ip4 default, ip6 default
> inet4 178.79.185.217/24
> route4 178.79.187.246/32
> inet6 2a01:7e00::825f:e564:ad53:72fc/64
> inet6 fe80::a8ad:d312:4ef4:7272/64

Re: [CentOS] IPv6 broken on Linode

[Alice Wonder]

On 02/16/2017 02:32 AM, James Hogarth wrote:

On 16 February 2017 at 10:17, Alice Wonder  wrote:

On 02/16/2017 02:03 AM, James Hogarth wrote:


On 16 February 2017 at 09:09, Alice Wonder  wrote:


On 02/16/2017 12:54 AM, Tony Mountifield wrote:



In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581...@domblogger.net>,
Alice Wonder  wrote:



https://forum.linode.com/viewtopic.php?f=19=14570=72785

I can not figure out what I need to do.

Apparently according to linode support, the VM is trying to grab an
IPv6
address with some privacy stuff enabled by default causing it to not
grab the IPv6 address that is assigned to me.




Does the accepted answer at the following link give you any useful
hints?



http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-when-using-ipv6

Cheers
Tony



Not really - I tried

net.ipv6.conf.all.use_tempaddr = 0

and it still fails to grab the proper IPv6

-=-

Just in case, I did ask Linode support to verify that my hardware address
is
what it is suppose to be. Still waiting to hear on that.

___




it still is key=value  ... it uses the ifcfg- files (via the rh
plugin) and they are all key=value

It would be helpful if you could paste the journal output (journalctl
-u NetworkManager) from the time period of attempting to get an
address ...

also the nmcli conn sh  information for the interface
along with your ifcfg- files



ifcfg-lo is the only one that exists on any of the servers - including the
VMs that grab the correct IPv6 address.

from /sbin/ifconfig -a :



For a start stop using ifconfig ... it's broken at this point on
linux, especially on multi ip and ipv6 scenarios

Use `ip -6 addr sh` for ipv6 specfic stuff, or just ip addr sh to see
all IP address stuff regardless of family


eth0: flags=4163  mtu 1500
inet 178.79.185.217  netmask 255.255.255.0  broadcast 178.79.185.255
inet6 fe80::a8ad:d312:4ef4:7272  prefixlen 64  scopeid 0x20
inet6 2a01:7e00::825f:e564:ad53:72fc  prefixlen 64  scopeid
0x0
ether f2:3c:91:18:8a:7e  txqueuelen 1000  (Ethernet)
RX packets 9903  bytes 1088621 (1.0 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 7786  bytes 1087223 (1.0 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

That hardware address - the 18:8a:7e corresponds with what the IPv6 address
is suppose to be. But that's not the address it is grabbing, despite the
fact that net.ipv6.conf.all.use_tempaddr = 0 is set.

I'm seriously wondering if the real issue is a mis-configured dhcp server in
their London facility because nothing makes sense.

journalctl -u NetworkManager

reports no journal entries found.



So are you not using NetworkManager then? there should be some logs ...



I think the problem must be on their end.

It all was working fine until they migrated the VM because of a hardware
issue, and I suspect now all the hardware address privacy stuff being the
issue is barking up the wrong tree because all the reading I have done seems
to indicate that with

net.ipv6.conf.all.use_tempaddr = 0

that a fake temporary hardware address would not be sent to their dhcp
server when obtaining the address, but the real one, that should be fetching
my assigned address.


Only if the kernel is doing SLAAC ... if other things (eg NM) are
handling it directly they may act differently ... but then from the
lack of logs is NM actually handling this?

Does systemctl status NetworkManager show it running and does nmcli
show anything?



systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; 
enabled; vendor preset: enabled)

   Active: active (running) since Thu 2017-02-16 08:19:34 UTC; 2h 19min ago

* more stuff *

nmcli
eth0: connected to Wired connection 1
"Red Hat Virtio network device"
ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500
ip4 default, ip6 default
inet4 178.79.185.217/24
route4 178.79.187.246/32
inet6 2a01:7e00::825f:e564:ad53:72fc/64
inet6 fe80::a8ad:d312:4ef4:7272/64
route6 2a01:7e00::/64

* more stuff for other interfaces *

-=-

The output of

sysctl -a | grep net.ipv6 :

https://librelamp.com/sysctl.txt

It looks from that like it should not be hiding the real MAC address.





It's all very frustrating but I suspect now the problem isn't the CentOS
network configuration.



Sounds likely ... depending on what there RA's say and how dhcpv6 is
being handled there (if at all) it could drastically affect things -
particularly if MAC changed on migration.


Five other servers all configured the same (started from same CentOS 7 image
and network stuff left alone) work properly - so I don't know.


___
CentOS mailing list

Re: [CentOS] IPv6 broken on Linode

[Mike McCarthy, W1NR]

Having used Linode and CentOS for years I have never had a problem quite
like this. Sure sounds like the IPv6 is misconfigured in the DHCP server
or is in use somewhere. Some things I would try are:

1. Set "Auto configure networking" in your config profile and reboot.
2. Try to assign the adddress static.
3. Ask Linode to assign you a new IPv6
4. Wait for Linode to fix the problem.

Mike

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] IPv6 broken on Linode

[James Hogarth]

On 16 February 2017 at 10:17, Alice Wonder  wrote:
> On 02/16/2017 02:03 AM, James Hogarth wrote:
>>
>> On 16 February 2017 at 09:09, Alice Wonder  wrote:
>>>
>>> On 02/16/2017 12:54 AM, Tony Mountifield wrote:


 In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581...@domblogger.net>,
 Alice Wonder  wrote:
>
>
> https://forum.linode.com/viewtopic.php?f=19=14570=72785
>
> I can not figure out what I need to do.
>
> Apparently according to linode support, the VM is trying to grab an
> IPv6
> address with some privacy stuff enabled by default causing it to not
> grab the IPv6 address that is assigned to me.



 Does the accepted answer at the following link give you any useful
 hints?



 http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-when-using-ipv6

 Cheers
 Tony

>>>
>>> Not really - I tried
>>>
>>> net.ipv6.conf.all.use_tempaddr = 0
>>>
>>> and it still fails to grab the proper IPv6
>>>
>>> -=-
>>>
>>> Just in case, I did ask Linode support to verify that my hardware address
>>> is
>>> what it is suppose to be. Still waiting to hear on that.
>>>
>>> ___
>>
>>
>>
>> it still is key=value  ... it uses the ifcfg- files (via the rh
>> plugin) and they are all key=value
>>
>> It would be helpful if you could paste the journal output (journalctl
>> -u NetworkManager) from the time period of attempting to get an
>> address ...
>>
>> also the nmcli conn sh  information for the interface
>> along with your ifcfg- files
>
>
> ifcfg-lo is the only one that exists on any of the servers - including the
> VMs that grab the correct IPv6 address.
>
> from /sbin/ifconfig -a :
>

For a start stop using ifconfig ... it's broken at this point on
linux, especially on multi ip and ipv6 scenarios

Use `ip -6 addr sh` for ipv6 specfic stuff, or just ip addr sh to see
all IP address stuff regardless of family

> eth0: flags=4163  mtu 1500
> inet 178.79.185.217  netmask 255.255.255.0  broadcast 178.79.185.255
> inet6 fe80::a8ad:d312:4ef4:7272  prefixlen 64  scopeid 0x20
> inet6 2a01:7e00::825f:e564:ad53:72fc  prefixlen 64  scopeid
> 0x0
> ether f2:3c:91:18:8a:7e  txqueuelen 1000  (Ethernet)
> RX packets 9903  bytes 1088621 (1.0 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 7786  bytes 1087223 (1.0 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> That hardware address - the 18:8a:7e corresponds with what the IPv6 address
> is suppose to be. But that's not the address it is grabbing, despite the
> fact that net.ipv6.conf.all.use_tempaddr = 0 is set.
>
> I'm seriously wondering if the real issue is a mis-configured dhcp server in
> their London facility because nothing makes sense.
>
> journalctl -u NetworkManager
>
> reports no journal entries found.
>

So are you not using NetworkManager then? there should be some logs ...


> I think the problem must be on their end.
>
> It all was working fine until they migrated the VM because of a hardware
> issue, and I suspect now all the hardware address privacy stuff being the
> issue is barking up the wrong tree because all the reading I have done seems
> to indicate that with
>
> net.ipv6.conf.all.use_tempaddr = 0
>
> that a fake temporary hardware address would not be sent to their dhcp
> server when obtaining the address, but the real one, that should be fetching
> my assigned address.

Only if the kernel is doing SLAAC ... if other things (eg NM) are
handling it directly they may act differently ... but then from the
lack of logs is NM actually handling this?

Does systemctl status NetworkManager show it running and does nmcli
show anything?


>
> It's all very frustrating but I suspect now the problem isn't the CentOS
> network configuration.
>

Sounds likely ... depending on what there RA's say and how dhcpv6 is
being handled there (if at all) it could drastically affect things -
particularly if MAC changed on migration.

> Five other servers all configured the same (started from same CentOS 7 image
> and network stuff left alone) work properly - so I don't know.
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] IPv6 broken on Linode

[Alice Wonder]

On 02/16/2017 02:03 AM, James Hogarth wrote:

On 16 February 2017 at 09:09, Alice Wonder  wrote:

On 02/16/2017 12:54 AM, Tony Mountifield wrote:


In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581...@domblogger.net>,
Alice Wonder  wrote:


https://forum.linode.com/viewtopic.php?f=19=14570=72785

I can not figure out what I need to do.

Apparently according to linode support, the VM is trying to grab an IPv6
address with some privacy stuff enabled by default causing it to not
grab the IPv6 address that is assigned to me.



Does the accepted answer at the following link give you any useful hints?


http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-when-using-ipv6

Cheers
Tony



Not really - I tried

net.ipv6.conf.all.use_tempaddr = 0

and it still fails to grab the proper IPv6

-=-

Just in case, I did ask Linode support to verify that my hardware address is
what it is suppose to be. Still waiting to hear on that.

___



it still is key=value  ... it uses the ifcfg- files (via the rh
plugin) and they are all key=value

It would be helpful if you could paste the journal output (journalctl
-u NetworkManager) from the time period of attempting to get an
address ...

also the nmcli conn sh  information for the interface
along with your ifcfg- files


ifcfg-lo is the only one that exists on any of the servers - including 
the VMs that grab the correct IPv6 address.


from /sbin/ifconfig -a :

eth0: flags=4163  mtu 1500
inet 178.79.185.217  netmask 255.255.255.0  broadcast 
178.79.185.255

inet6 fe80::a8ad:d312:4ef4:7272  prefixlen 64  scopeid 0x20
inet6 2a01:7e00::825f:e564:ad53:72fc  prefixlen 64  scopeid 
0x0

ether f2:3c:91:18:8a:7e  txqueuelen 1000  (Ethernet)
RX packets 9903  bytes 1088621 (1.0 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 7786  bytes 1087223 (1.0 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

That hardware address - the 18:8a:7e corresponds with what the IPv6 
address is suppose to be. But that's not the address it is grabbing, 
despite the fact that net.ipv6.conf.all.use_tempaddr = 0 is set.


I'm seriously wondering if the real issue is a mis-configured dhcp 
server in their London facility because nothing makes sense.


journalctl -u NetworkManager

reports no journal entries found.

I think the problem must be on their end.

It all was working fine until they migrated the VM because of a hardware 
issue, and I suspect now all the hardware address privacy stuff being 
the issue is barking up the wrong tree because all the reading I have 
done seems to indicate that with


net.ipv6.conf.all.use_tempaddr = 0

that a fake temporary hardware address would not be sent to their dhcp 
server when obtaining the address, but the real one, that should be 
fetching my assigned address.


It's all very frustrating but I suspect now the problem isn't the CentOS 
network configuration.


Five other servers all configured the same (started from same CentOS 7 
image and network stuff left alone) work properly - so I don't know.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] IPv6 broken on Linode

[Pete Biggs]

On Thu, 2017-02-16 at 00:37 -0800, Alice Wonder wrote:
> https://forum.linode.com/viewtopic.php?f=19=14570=72785
> 
> I can not figure out what I need to do.
> 
> Apparently according to linode support, the VM is trying to grab an IPv6 
> address with some privacy stuff enabled by default causing it to not 
> grab the IPv6 address that is assigned to me.

I'm no IPv6 expert (as in I know nothing), but look at the options that
dhclient is using when it's running - there are various v6 specific
options that would affect what's happening. 'man dhclient' is useful
here.

> 
> 
> I know CentOS follows Red Hat so I'm not suggesting this is CentOS's 
> fault, but stuff like this really is why I am a much bigger fan of KISS 
> with simple key=value configuration files that don't seem to exist 
> anymore with Linux networking in the Red Hat world.

Yes they do. Everything concerned with networking is held in flat files
- they may be XML like files or some other structured approach, but
they are there. What you are probably confusing it with is the fact
that most of the config files are written by GUI applications or
maintained by CLI commands rather than editing them by hand. That's all
down to NetworkManager - love it or hate it, but the clue to what it
does is in the name, it manages your network.  If you don't want
something to manage your network, don't use it.

> 
> Anyone know what might be going on? And how to get dhclient to grab the 
> "right" IPv6 address, the same one this VM grabbed no problem for well 
> over a year?
> 

As I said, you need to look at dhclient configuration and command line
options.  If you have NetworkManager running then it will be
controlling what dhclient does so manual editing the files will not
work. Use nmcli to see what's happening and modify the configuration.

P.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] IPv6 broken on Linode

[James Hogarth]

On 16 February 2017 at 09:09, Alice Wonder  wrote:
> On 02/16/2017 12:54 AM, Tony Mountifield wrote:
>>
>> In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581...@domblogger.net>,
>> Alice Wonder  wrote:
>>>
>>> https://forum.linode.com/viewtopic.php?f=19=14570=72785
>>>
>>> I can not figure out what I need to do.
>>>
>>> Apparently according to linode support, the VM is trying to grab an IPv6
>>> address with some privacy stuff enabled by default causing it to not
>>> grab the IPv6 address that is assigned to me.
>>
>>
>> Does the accepted answer at the following link give you any useful hints?
>>
>>
>> http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-when-using-ipv6
>>
>> Cheers
>> Tony
>>
>
> Not really - I tried
>
> net.ipv6.conf.all.use_tempaddr = 0
>
> and it still fails to grab the proper IPv6
>
> -=-
>
> Just in case, I did ask Linode support to verify that my hardware address is
> what it is suppose to be. Still waiting to hear on that.
>
> ___


it still is key=value  ... it uses the ifcfg- files (via the rh
plugin) and they are all key=value

It would be helpful if you could paste the journal output (journalctl
-u NetworkManager) from the time period of attempting to get an
address ...

also the nmcli conn sh  information for the interface
along with your ifcfg- files
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] IPv6 broken on Linode

[Alice Wonder]

On 02/16/2017 12:54 AM, Tony Mountifield wrote:

In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581...@domblogger.net>,
Alice Wonder  wrote:

https://forum.linode.com/viewtopic.php?f=19=14570=72785

I can not figure out what I need to do.

Apparently according to linode support, the VM is trying to grab an IPv6
address with some privacy stuff enabled by default causing it to not
grab the IPv6 address that is assigned to me.


Does the accepted answer at the following link give you any useful hints?

http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-when-using-ipv6

Cheers
Tony



Not really - I tried

net.ipv6.conf.all.use_tempaddr = 0

and it still fails to grab the proper IPv6

-=-

Just in case, I did ask Linode support to verify that my hardware 
address is what it is suppose to be. Still waiting to hear on that.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] IPv6 broken on Linode

[Tony Mountifield]

In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581...@domblogger.net>,
Alice Wonder  wrote:
> https://forum.linode.com/viewtopic.php?f=19=14570=72785
> 
> I can not figure out what I need to do.
> 
> Apparently according to linode support, the VM is trying to grab an IPv6 
> address with some privacy stuff enabled by default causing it to not 
> grab the IPv6 address that is assigned to me.

Does the accepted answer at the following link give you any useful hints?

http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-when-using-ipv6

Cheers
Tony
-- 
Tony Mountifield
Work: t...@softins.co.uk - http://www.softins.co.uk
Play: t...@mountifield.org - http://tony.mountifield.org
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] IPv6 broken on Linode

[Alice Wonder]

https://forum.linode.com/viewtopic.php?f=19=14570=72785

I can not figure out what I need to do.

Apparently according to linode support, the VM is trying to grab an IPv6 
address with some privacy stuff enabled by default causing it to not 
grab the IPv6 address that is assigned to me.


Nothing I have tried seems to work, and it seems that Linode support are 
far more familiar with Ubuntu than CentOS.


I know CentOS follows Red Hat so I'm not suggesting this is CentOS's 
fault, but stuff like this really is why I am a much bigger fan of KISS 
with simple key=value configuration files that don't seem to exist 
anymore with Linux networking in the Red Hat world.


Making things more complex to benefit "Cloud" servers it the worst thing 
Red Hat ever did.


Sorry for the tone, I'm quite frustrated and as an epileptic who doesn't 
drive, driving down to the SF Bay Area for RHCE classes that won't even 
be applicable in a few years when they change stuff again isn't really 
an option.


Been using Red Hat since MKLinux DR3 (based on Red Hat 5.1) and been 
through the training courses before and everything changes.


Anyone know what might be going on? And how to get dhclient to grab the 
"right" IPv6 address, the same one this VM grabbed no problem for well 
over a year?

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos