Krond
Make sure you treat both networks as insecure.
Lunokjod
@xsuuu you mean ipnat_enable="yes" is needed to do a route?
Krond
no, just nat
XS
that is! you have all my atention :)
to get them right you need some knowledge about networking packet filters, here you go for FreeBSD: https://docs.freebsd.org/en/books/handbook/firewalls/
Krond
You need to enable ipfw or pf and define how you will be allowing packets through your host.
Lunokjod
ok :) thanks :*
XS
we can't just create a config for you because we have no idea what's your topology and interfaces names, ect
Krond
PF can do nat by itself.
XS
but there's examples around
Lunokjod
we can't just create a config for you because we have no idea what's your topology and interfaces names, ect
ohh thanks, but I prefer to learn to do myself :)
XS
so I recommand you to chose pf
Lunokjod
(the topology is the same as the example of the book)
XS
and follow up to 31.3.2.1 section
Lunokjod
thanks, I going to learn it, thank you!
Lunokjod
(and you @krond :)
XS
as well as 31.3.2.3. Managing ICMP
XS
yw
Krond
Heh, mine definitely wouldn't work, I'm using fibs to balance traffic between 2 inbound connections.
XS
I'm using carp and pfsync but my routers are running OpenBSD. But I have some pf running on TrueNAS in production.
Krond
In my case those are two different providers with different networks.
XS
for inbound traffic as well ?
XS
I mean, do you host services behind a shared IP between ISP's ?
Krond
No, for that cases like email I just add both on DNS.
XS
okay!
D.M
Hi, How can I make it colored like coreutils does when exporting LS_COLORS?
XS
FreeBSD's ls have the -G option or CLICOLOR and LSCOLORS environment variables to enable this feature. As you can see in ls(1), it's advised to set CLICOLOR according to the TERM you use.
D.M
🇵🇸🍉
Why bsd distros not gpl however it's use all gnu utilities
XS
Which BSD, which all utilities ?
🇵🇸🍉
Freebsd use vim, nano, emcs, kde, gnome, sddm, gdm,etc
I fell its gnu/linux but gnu/bsd
XS
uhhh
XS
no, FreeBSD don't use what you mentionned
XS
it's just that those software are portable
XS
and someone made ports for them, it's not shipped by the FreeBSD devs
🇵🇸🍉
Vim installed by default
ɴꙩᴍᴀᴅ
XS
no, it's vi
XS
and vim is not GPL btw
Lunokjod
@xs @krond at last the freebsd router (yesterday) works :) some nat magic with /etc/pf.conf thanks!
XS
great to hear, good job
Krond
🇵🇸🍉
Can freebsd team one day make it closed source
Krond
Yes, definitely. You still have your downloaded source open under same license.
Krond
They have full right to do what they want with their code. Right now they choose to publish it, and this can't be undone.
XS
The FreeBSD project argues on the advantages of BSD-style licenses for companies and commercial use-cases due to their license compatibility with proprietary licenses and general flexibility, stating that the BSD-style licenses place only "minimal restrictions on future behavior" and are not "legal time-bombs", unlike copyleft licenses.[20] The BSD License allows proprietary use and allows the software released under the license to be incorporated into proprietary products. Works based on the material may be released under a proprietary license as closed source software, allowing usual commercial usages under them.
XS
Basically anyone can
🇵🇸🍉
Freebsd it self like next version 14 for example
XS
for example sony did with his playstation operating system
XS
but I don't think that's a coherent goal for the FreeBSD project itself
XS
It's a closed source fork of FreeBSD
Krond
Well, you are asking question like "can people who are responsible for FreeBSD release process make closed source release?" And the answer is "Yes".
Krond
Whereas any other team can release FreeBSD 14 on their own.
Krond
So making a closed-source release kindda doesn't make any sense.
🇵🇸🍉
License is very complicated
🇵🇸🍉
So making a closed-source release kindda doesn't make any sense.
Like openindiana and oracle solaris
Openzfs and orcale zfs
Krond
Indeed. And one huge difference between GPL and BSD is that IP rights are retained in BSD world. So actually release team doesn't have right to change licensing status of most of the files, because it's not their property.
Anonymous
Freebsd use vim, nano, emcs, kde, gnome, sddm, gdm,etc
I fell its gnu/linux but gnu/bsd
Those are not standard UNIX utilities, they're third party software
Anonymous
Can freebsd team one day make it closed source
The author of any software can do that, not just FreeBSD
Krond
Well, not exactly author, but IP rights handler, in GPL world this is GNU Software or FSF, dunno for sure.
Krond
So actually "Can any GPL software be released as closed source?" can also be answered as "Yes".
🇵🇸🍉
So actually "Can any GPL software be released as closed source?" can also be answered as "Yes".
Wait that's also not right
🇵🇸🍉
Because Torvalds refused to change linux license to gpl v3 because of tivo
K
Because Torvalds refused to change linux license to gpl v3 because of tivo
He couldn’t. Right are not only his but of all contributors (both people and companies)
🇵🇸🍉
The author and ip right handler
🇵🇸🍉
But we don't talk about one author there are hundreds
🇵🇸🍉
And bsd authors are alot and maybe some of them are dead
🇵🇸🍉
So bsd license impossible to be changed
Anonymous
And bsd authors are alot and maybe some of them are dead
I think the very original author is still the University of California
Anonymous
since BSD was originally made by them and I saw them in COPYRIGHT
🇵🇸🍉
Yeah what about others?
🇵🇸🍉
That is same problem with open zfs is not gpl