Messages

1

General Discussion / Re: Secondary IPv6 address aka VirtualIP- how?

« on: February 15, 2019, 10:34:24 am »

bump

2

General Discussion / Secondary IPv6 address aka VirtualIP- how?

« on: February 13, 2019, 04:10:10 pm »

Hi guys,

normaly i add secondary IPs via VirtualIP (Firewall -> Virtual IPs -> Settings -> Add). It works for me if the IP is v4 format.
If i use a single v6/128 as VirtualIP it dosent show up withing ifconfig or elsewhere.

If i use CARP it works. No Problem with that, but shouldn it work als within as a IP-Alias?

Did i missed something?

11.2-RELEASE-p8-HBSD FreeBSD 11.2-RELEASE-p8-HBSD  31af16db12b(stable/19.1)  amd64

3

German - Deutsch / Re: Letsencrypt: Create domain key error

« on: February 07, 2019, 03:49:28 pm »

[Thu Feb  7 15:46:17 CET 2019] Le_NextRenewTime='1554640665'
[Thu Feb  7 15:46:17 CET 2019] _saved_domain='XXXX'
[Thu Feb  7 15:46:17 CET 2019] _saved_alt='no'
[Thu Feb  7 15:46:17 CET 2019] Domains not changed.
[Thu Feb  7 15:46:17 CET 2019] Skip, Next renewal time is: Mon Apr  8 12:37:45 UTC 2019
[Thu Feb  7 15:46:17 CET 2019] Add '--force' to force to renew.

Jemand ne Idee wie ich das forcen kan?

4

German - Deutsch / Re: Letsencrypt: Create domain key error

« on: February 07, 2019, 01:35:30 pm »

Hi,

ist das noch immer ein Problem?
HAProxy -> LE integration. Auch mein System verwendet für /var den RAM. Das Key File liegt im Pfad/ist vorhanden. Meldet aber "Create domain key error."

E: hat sich erledigt, hab den Account neu angelegen müssen da die E-Mail schon auf einen anderen Host verwendet wurde, nicht bedacht. Das hat ihn dann wohl außer tritt gebracht da ich nur die E-Mail angepasst habe. Das hat er nicht gefressen, erst wie ich den Account gelöscht habe und neu angelegt habe ging es weiter.

Aktuell habe ich aber das Problem von Env->Produktion

Code: [Select]

[Thu Feb  7 13:46:00 CET 2019] ACME_DIRECTORY='https://acme-v01.api.letsencrypt.org/directory'
[Thu Feb  7 13:46:00 CET 2019] DOMAIN_PATH='/var/etc/acme-client/home/XXX'
[Thu Feb  7 13:46:00 CET 2019] Using ACME_DIRECTORY: https://acme-v01.api.letsencrypt.org/directory
[Thu Feb  7 13:46:00 CET 2019] _init api for server: https://acme-v01.api.letsencrypt.org/directory
[Thu Feb  7 13:46:00 CET 2019] GET
[Thu Feb  7 13:46:00 CET 2019] url='https://acme-v01.api.letsencrypt.org/directory'
[Thu Feb  7 13:46:00 CET 2019] timeout=
[Thu Feb  7 13:46:00 CET 2019] _CURL='curl -L --silent --dump-header /var/etc/acme-client/home/http.header  -g '
[Thu Feb  7 13:46:00 CET 2019] ret='0'
[Thu Feb  7 13:46:00 CET 2019] ACME_KEY_CHANGE='https://acme-v01.api.letsencrypt.org/acme/key-change'
[Thu Feb  7 13:46:00 CET 2019] ACME_NEW_AUTHZ='https://acme-v01.api.letsencrypt.org/acme/new-authz'
[Thu Feb  7 13:46:00 CET 2019] ACME_NEW_ORDER='https://acme-v01.api.letsencrypt.org/acme/new-cert'
[Thu Feb  7 13:46:00 CET 2019] ACME_NEW_ACCOUNT='https://acme-v01.api.letsencrypt.org/acme/new-reg'
[Thu Feb  7 13:46:00 CET 2019] ACME_REVOKE_CERT='https://acme-v01.api.letsencrypt.org/acme/revoke-cert'
[Thu Feb  7 13:46:00 CET 2019] ACME_AGREEMENT='https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf'
[Thu Feb  7 13:46:00 CET 2019] ACME_NEW_NONCE
[Thu Feb  7 13:46:00 CET 2019] ACME_VERSION
[Thu Feb  7 13:46:00 CET 2019] Le_NextRenewTime='1554640665'
[Thu Feb  7 13:46:00 CET 2019] _saved_domain='XXXX'
[Thu Feb  7 13:46:00 CET 2019] _saved_alt='no'
[Thu Feb  7 13:46:00 CET 2019] Domains not changed.
[Thu Feb  7 13:46:00 CET 2019] Skip, Next renewal time is: Mon Apr  8 12:37:45 UTC 2019
[Thu Feb  7 13:46:00 CET 2019] Add '--force' to force to renew.


5

German - Deutsch / Re: openVPN auf ipv6

« on: September 16, 2017, 02:38:53 am »

Hallo,

unter den VPN Einstellungen zum Client/Server findest du die Option das "Protocol" zu wählen UDP/TCP und eben da auch v6 oder v4. Dann noch deine V6 Adressen setzen btw. deine v4 Tunnelsettings.

Gruß

6

General Discussion / Re: where to find onlder builds? specifically the 32 bit based on freeBSD 8.3

« on: April 22, 2016, 12:53:07 am »

dont know why the use 1 as default, maybe

NOTE: TSO requires Tx checksum, if Tx checksum is disabled, TSO will also
be disabled.

but how knows. also vote for 0 (default).
its a trublemaker
if you virtualize OPNsense, u have to disbale it. also at the hypervisor (host)

btw. CRC, TSO, LRO  =1 will give u some headache to
(System -> Settings ->Networking)

7

General Discussion / Re: where to find onlder builds? specifically the 32 bit based on freeBSD 8.3

« on: April 21, 2016, 07:10:40 pm »

hey guys,
hey franco,

any good reason why net.inet.tcp.tso is set by default to 1?

almost all hardware/drivers have issues with these settings, it should be 0 by default or?

8

15.7 Legacy Series / Re: vmware disk timeout

« on: January 14, 2016, 11:51:36 am »

didnt test esxi5.5 with OPNsense. No issues with esxi6 - iscsi hdd (vm version11)