why can freebsd get ipv6 address with wire network card, but can not get address with wireless device ?

both ways use dhcp to get address.

where might it be wrong ?

using freebsd 13.x

iirc, dhcpv6 is not supported in the base system

this is because ipv6 is not supposed to use it, it has its own address discovery mechanisms, and dhcpv6 is a hack

what makes you think it's using dhcp when on wire?

sorry, I don't know that.

how to setup ipv6 connect with wireless connection?

I don't know, sorry

I searched some web pages on how to configure dhcpv6 on wireless network but I can't duplicate that.

ifconfig_vtnet0_ipv6="accept_rtadv"

Add that to your rc.conf, only switch vtnet0 for your wifi interface.

occ: did you see CrtxReavr's response?

I have yet to find a public use (coffee shop) WiFi Access Point that passes IPv6 through. Here they are all IPv4 only.

RhodiumToad: I was finding more information on accept_rtadv ...

rwp: in my case, I happened seeing the phenomenon that freebsd could get ipv6 address with wire connection but only ipv4 address with wireless connection at the same time. freebsd can visit public network with above both connections.

s/both/two

two default routes work fine, one is ipv6 ,the other is ipv4.

The more I learn about IPv6 the more I think DHCPv6 is the better option over SLAAC/RA

I didn't use ifconfig_vtnet0_ipv6 in /etc/rc.conf.

just ifconfig_(device)="DHCP"

I didn't use ifconfig_vtnet0_ipv6 like options in /etc/rc.conf.

dammit, what's a good way to compare a constant like SIZE_MAX against a value without triggering -Wtautological-constant-out-of-range-compare

they make compilers out of warnings now

RhodiumToad, Hmm... SIZE_MAX is the largest size possible, right? So won't by definition all values either be equal to it or less than it? Can't ever be larger.

In other words... Does it make much useful sense to ever compare against it?

yes

assume you have a variable foo which is of an (assumed unsigned) type defined by some library header

you want to know if you can safely cast (size_t)foo preserving the value

now, size_t isn't guaranteed to be the largest unsigned type, in particular on 32-bit sustems it's not

so you might try if (foo <= SIZE_MAX) on the assumption that whichever of the two sides is a smaller type should be promoted to the larger one

on 32 bit where foo is a uint64_t, this works without error

but on 64 bit, you get the warning

I'll play Devil's Advocate here and say then that sizeof target needs to be >= sizeof source.

sizeof isn't really the right tool to compare type ranges

Well... Neither is foo <= SIZE_MAX either.

Since that must always be true.

and it's explicitly OK for foo to be of a larger _size_ than size_t, as long as the actual value fits in a size_t

no, foo <= SIZE_MAX is not always true since foo can be of a larger sized type than size_t

the other method is if ((size_t)foo == foo)

(assuming foo's type is unsigned, this is well-defined)

if foo's type is no larger than size_t then the cast preserves the value and the result is true,

whereas if foo's type is larger and the value fits in size_t, the result is still true,

but if foo's type is larger and the value doesn't fit, then the cast reduces the value mod 2^N for some N, and the comparison is now false

but annoyingly, that version generates much worse code

how do you run du -b on fbsd?

welp, installed busybox I guess

nmz-: if it comes from gnu du, install sysutils/coreutils

I have to admit, I had a "Eureka!" moment earlier today that I think is pretty cool.

how do i install a man page for my port?

do i have to do it myself in the source Makefile or can i set something in the port Makefile?

Title: Chapter 5. Configuring the Makefile | FreeBSD Documentation Portal

thanks. i only read the quick ports part :[

it should be installed by source Makefile, yes, ports are not really a build system, rather a wrapper around original one and patching as needed

is there a freebsd way to do that?

i don't see something like `install-man`

if you use the system mk files, it's MANx= something.x, where x is the section

(ugh, or is it only MAN= something.x now, correctly parsing the .x for section)

both should work anyway :)

Hi, I'm struggling with a devd rule where my action can't resolve a variable: bsd.to/LkHX

Title: dpaste/LkHX (Plain Text)

sorry, better formatting: bsd.to/nWev

Title: dpaste/nWev (Bash)

I guess it's more a problem with su shell and my bad shell scripting skills in general than devd :)

espen_: devd.conf(5) has a "Notes on Variable Expansion" subsection

(and i think the bottom line there is "don't use single quotes" :)

yuripv, thanks! and yes you're right.. now I need to figure out how to replace those o_O

Title: 240411 – devd behaves odd when action uses single quotes

I think I'll have to get rid of the variable and have one rule per device :/

espen_: you need single quotes for -c argument to su?

espen_: may be try using escaped double quotes in place of single ones? i.e. -c \"...\"

Not necessarily I think, but I'm failing to escape it and devd accept it.

Yeah that doesn't work..

for install(1), is it true that you can't actually do -d to create parent dirs and install files at the same time?

fwiw on (other) systems man install shows for -d: treat all arguments as directory names; create all components of the specified directories

Which vaguely goes back to my distant memories of POSIX

istr there was a pr for it

Title: 230620 – "install -d" issue

rustyaxe: the problem seems to be creating directories *and* installing files at the same time

yea i think posix says -d treats all args s directories

thus GNU's behavior and what i remember from 30 years ago :)

-d Create directories. Missing parent directories are created as required. This option cannot be used with the -B, -b, -C, -c, -f, -p, or -s options.

im thinking htats expected behaviour

Deal with directories first, then deal with files

yuripv: yep that's it. thanks

i just used mkdir -p instead

extra step but whatever

if not expected, at least the most common behavior -- ie if you care of portability, dont do it

why would you need to have `make package` succeed as non-root if the ports dir is /usr/ports?

(following quick port steps)

hey folks, where do i find the libc-devel package/sources? im building the linux kernel from scratch and its complaining that it cant find bytewswap.h header

gzar: wrong channel?

no

im on freebsd

basically just looking for the libc devel files

i'm curious as huge as linux kernel has grown if cross compiling has even been tested in decades :P

oh, well i guess i am testing it now

i've been thinking of an experiment for a while with the linux kernel

but will probably ask in some linux channel

if my printer (samsung M2026) has no drivers for FreeBSD, is there chance to get any support beyond ascii printing?

hubertm: cups has some generic drivers when I tried that on my printer it worked fine

so thought it didn't show my specific model it still worked when I looked around for something more generic