Date: Sun, 15 Nov 2020 07:41:50 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 251047] Multicast: Not possible to add MFC entry's when MAXVIFS = 64 Message-ID: <bug-251047-7501-dgwfxnXimr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-251047-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-251047-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251047 --- Comment #2 from Louis <louis.freebsd@xs4all.nl> --- Thanks for your reaction, which made me realize that I had to do more than = one change, to get a changed maxvifs working. I think I managed that. Not in the proper way yet, and surely not the way it IMHO should work. Problem is that the actual package has to be recompiled for every machine having a different number of vifs. And you need to know the number of vifs = of the (unkown) target machine at compile time.=20 And that where ...... IMHO the package should be machine independent ! So what I would like to archive is: - start the program - do an OS-call to read/obtain the maxvifs number - open structures based on the obtained maxvifs - start the actions where the program is designed for Do not know if this is possible, but compiling the package maxvif number / os-instance depended .....is bad !! So you would help me with an OS-call/method providing the maxvifs number on= the actual OS-instance ..... Of course this is just a question. As far as I can see now, the problem is = not in the os. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-251047-7501-dgwfxnXimr>