public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lucas Ramage <ramage.lucas94@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] dhcpcd: disable zerconf
Date: Mon, 22 Jan 2018 15:26:17 -0500	[thread overview]
Message-ID: <CAKkjsY8sH839mWaWjjGuLvVEREsOM6ZEpu24-CTsP=dkm03gZg@mail.gmail.com> (raw)
In-Reply-To: <L3UUccz--3-0@tutanota.com>

[-- Attachment #1: Type: text/plain, Size: 2082 bytes --]

Is your scenario related to running Gentoo on a workstation?

I am using gentoo as a hypervisor for lxc and my veth interface for my
guest is getting assigned a 169.254.x.x address (host side). I can't see it
from inside the guest, but it's screwing with my routing tables.

On Mon, Jan 22, 2018 at 3:10 PM, <mad.scientist.at.large@tutanota.com>
wrote:

> that works.  myself, i like to totally misconfigure it and then change
> access to read only even for root, usually takes care of updates starting
> it.  i've also sabotaged one of there scripts so it just always returns a
> 1, i.e. error, also locked down afterwards.  the zero config stuff is
> tricky sometimes with updates and installs.  I also block router solicit
> and router advertising in the firewall.  I've been owned before, can't be
> too careful (pretty obvious when the system monitor won't launch, kinda
> pathetic when they knock out the sysmon for gnome but leave the one for kde
> working, glad i had both).
>
> mad.scientist.at.large (a good madscientist)
> --
> God bless the rich, the greedy and the corrupt politicians they have put
> into office.   God bless them for helping me do the right thing by giving
> the rich my little pile of cash.  After all, the rich know what to do with
> money.
>
>
> 22. Jan 2018 11:14 by gentoo-user@c-14.de:
>
>
> Holle,
> On 18-01-22 at 12:49, Lucas Ramage wrote:
>
> Hello,
>
> How does one disable zerconf for dhcpcd or at all in Gentoo for that
> matter?
>
> Do you mean ipv4ll? Add noipv4ll to /etc/dhcpcd.conf .
>
> --
> Simon Thelen
>
>


-- 

[image: Visit online journal] <https://lramage94.github.io>

*Lucas Ramage* / Software Engineer
ramage.lucas@openmailbox.org / (941) 404-6794

*PGP Fingerprint* / Learn More <https://emailselfdefense.fsf.org/en/>
EAE7 45DF 818D 4948 DDA7 0F44 F52A 5A96 7B9B 6FB7
<https://pgp.mit.edu/pks/lookup?op=get&search=0xF52A5A967B9B6FB7>

*Visit online journal*
http://lramage94.github.io <https://lramage94.github.io>

[image: Github]  <https://github.com/lramage94>[image: Linkedin]
<https://www.linkedin.com/in/lramage94>

[-- Attachment #2: Type: text/html, Size: 4742 bytes --]

  reply	other threads:[~2018-01-22 20:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22 17:49 [gentoo-user] dhcpcd: disable zerconf Lucas Ramage
2018-01-22 18:14 ` Simon Thelen
2018-01-22 18:27   ` Lucas Ramage
2018-01-22 20:10   ` mad.scientist.at.large
2018-01-22 20:26     ` Lucas Ramage [this message]
2018-01-22 20:29       ` mad.scientist.at.large
2018-01-23  3:25         ` Walter Dnes
2018-01-23  5:17           ` mad.scientist.at.large
     [not found]           ` <<20180123032549.GB14871@waltdnes.org>
     [not found]             ` <L3WRsHs--3-0@tutanota.com-L3WS-zS----0>
2018-01-23  5:22               ` mad.scientist.at.large

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKkjsY8sH839mWaWjjGuLvVEREsOM6ZEpu24-CTsP=dkm03gZg@mail.gmail.com' \
    --to=ramage.lucas94@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox