> Is there any way to silence these logs? I only want to hand out a
> small number of IPv4 addresses on my IPv6 network to those machines
> that won't function properly without them. That leaves many machines
> on my network constantly requesting IPv4 addresses, and dhcpd is
> clogging my
Ok, think I figured it out.
My core problem was that I was assigning prefixes manually in rad.conf,
then assigning each interface an address *in the same prefix*. This
created some kind of conflictâthe nature of which I still don't fully
understand.
This was the key line I missed in
Is there any way to silence these logs? I only want to hand out a small
number of IPv4 addresses on my IPv6 network to those machines that won't
function properly without them. That leaves many machines on my network
constantly requesting IPv4 addresses, and dhcpd is clogging my
/var/log/daemon
Before I learned about the tilde sequences, I just unplugged the USB
adapter. That quits cu.
Worked in my case since my device was under its own power. FYI.
> To reach the internet from ULA addresses you'll need NAT.
> Alternatively use *both* global and ULA prefixes in rad.conf (or I
> think you can use auto prefix). But I don't think you've got that far
> yet.
I was planning on using the ULAs for internal addressing only, and doing
port-forwarding
> I can ping6 back to my router using the IPv6 address in the prefix
> delegation from my ISP, but I cannot seem to do the same for the
> addresses in my ULA prefix.
I can see neighbor solicitation requests from my clients for the ULA
gateway address, but I see no neighbor advertisements sent in
>> interface igc1 {
>> prefix fdbf:e79a:8e3e::/48
>
> lesser operating systems will refuse to form autoconf addresses if the
> prefix length is not 64.
Thanks, this was helpful. I got addresses allocated on client machines,
but they don't seem routable.
I can
I'm not sure how to configure rad (or if rad is the right program) to
help have my devices autoconfigured ULA addresses in a given prefix
(generated from https://www.unique-local-ipv6.com).
I am debugging a new ISP and need to switch between two ISPs without
disrupting communication between my
> ... however I'm getting different errors now for the Slack-group
> specific URLs:
>
> ...
>
> validation failure : signatures from unknown keys
> from 2620:fe::fe
Was able to fix this by running `unbound-anchor` after fixing my system
clock. I think everything is working normally now.
Thanks!
> You can use rdate to jump the clock instead.
That updated my system clock to the correct time. dig queries against
Slack now work as expected, however I'm getting different errors now for
the Slack-group specific URLs:
```
# dig @::1 kubernetes.slack.com
; <<>> DiG 9.10.6 <<>>
> Wild guess, your time is off.
Huh, I think you're right. `date` shows me 7 hours ahead of my timezone.
I restarted ntpd and I see no errors in /var/log/daemon, but the time is
still off. I should be 1200 PDT but it's showing me as 1900 PDT (not
UTC).
What do I do to fix this? Pretty sure I
I have an unbound server using Quad9 as an upstream DNS provider. I have
been unable to resolve records from slack.com recently using my local
unbound.
On the server:
```
# dig @::1 slack.com
; <<>> dig 9.10.8-P1 <<>> @::1 slack.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;;
> I don't think there is at present. There are no "only use v4" or "only
> use v6" addresses modifiers, and pf isn't figuring out for itself that
> it only makes sense to use addresses from the relevant family for
> af-to translation addresses (although it _does_ do this for nat-to).
Good to
> Try changing ($wan:0) to $(wan) and see what happens.
Huh, that worked! Thanks!
> you should be able to reply to the copy in your "sent" folder
Good to know.
> I just re-sent the original messages to your new address so you should
> now have a copy to reply to.
Thanks!
Is that something you can do because you're a list administrator or
something? Still wondering if there
> Can you try if the same happens with a more specific rule (for
> testing)?
>
> i.e.:
>
> pass in on igc3 inet6 from "put actual v6 prefix here" to 64:ff9b::/96
> af-to inet from "actual IP on igc0"/32
This worked! Specifically, I think the ($wan:0) was the problem. I
could've sworn I tried this
Apologies for the newbie question: I'm new to mailing lists. ;D
I sent a message to this list earlier from a ProtonMail account, and
none of the replies have arrived (not even in Junk), even though I see
there are replies via the web archive... so I don't have a message to
reply to.
I've since
Hello,
I'm trying to get a basic OpenBSD NAT64 router setup. I'm following
along with these instructions:
- https://blog.obtusenet.com/dns64-nat64-on-openbsd/
My unbound instance looks like it's correctly configured and returning
correct IPv6 addresses, so that's good.
# dig
18 matches
Mail list logo
