Recent posts

#1

Virtual private networks / Re: Followed the official wire...

Last post by user12314 - Today at 02:45:42 PM

What does your OPNsense display in Interfaces > Overview or in the Interfaces dashboard widget?

There, the wan ipv4 starts with 100.83, and the ipv6 with 2a00:1598

#2

Virtual private networks / Re: Followed the official wire...

Last post by Patrick M. Hausen - Today at 02:42:56 PM

What does your OPNsense display in Interfaces > Overview or in the Interfaces dashboard widget?

#3

26.7 Series / Re: SSD drive died - I disable...

Last post by Patrick M. Hausen - Today at 02:41:41 PM

Apologies for answering in German. I got confused, somehow.

One possible "solution" would be to simply buy a large (1T or so) high write endurance SSD. Yeah, easier said then done in the current state of the market. Back when those used to cost a hundred or so, I personally would have thrown money at the problem. Maybe try to get one used. Samsung 970, WD Black, ... that kind of devices.

#4

Virtual private networks / Re: Followed the official wire...

Last post by user12314 - Today at 02:40:15 PM

Is your Uplink behind CGNAT, possibly? Or your OPNsense behind an ISP router? Post the first two octets of your WAN address, please.

I'm not sure about CGNAT, it is not behind a ISP router, it directly connects to the internet.
`curl icanhazip.com` gives me 94.255 as the first 2 octets.
Thank you

#5

Virtual private networks / Re: Followed the official wire...

Last post by Patrick M. Hausen - Today at 02:38:05 PM

Is your Uplink behind CGNAT, possibly? Or your OPNsense behind an ISP router? Post the first two octets of your WAN address, please.

#6

Virtual private networks / Re: Followed the official wire...

Last post by user12314 - Today at 02:20:12 PM

just tried to do a packet capture using interface WAN, port 51830, protocol UDP and nothing showed up when trying to connect to the vpn.

#7

26.7 Series / Re: SSD drive died - I disable...

Last post by RamSense - Today at 02:07:10 PM

I have still an ungoing ticked with zenarmour about the rootcause of my extreme SSD wear and having to replace the SSD. Since I have replaced the SSD and I have removed Zenarmour (at least until a decent sollution from Zenarmour), no more problems here.

#8

Virtual private networks / Followed the official wireguar...

Last post by user12314 - Today at 01:34:12 PM

I have followed https://docs.opnsense.org/manual/how-tos/wireguard-client.html and I'm not making a handshake. I see on my android wireguard app that data does leave, but no data comes back in my phone.

I read through the guide 3 times to make sure I did it correctly. I used an interface as recommended, and did not make any outbound NAT rules.

I also tried filtering the live view logs for the WAN rule that redirects incoming vpn connections, i did not see any logs.

I tried 2 ports, 51820 and 51830, both did not work.

I'm stuck, can anyone help?

#9

General Discussion / Re: DNS over tls when running...

Last post by DEC740airp414user - Today at 12:49:37 PM

I still am just using one dns over TLS server.  but using quad 9 now.    this option called forward first.   is this new?    I am not seeing this in any documentation.    it seems like it would fix my issue if forwarding to quad 9 or similar stopped.   it would use standard unbound.. correct?

where do I define the server time out setting?

later edit.  my googlefu has been bad this morning.   I did find this that explains what it is https://forum.opnsense.org/index.php?topic=45521.0

#10

Russian - Русский / Re: os-xray — плагин Xray-core...

Last post by ha_harbor_ws - Today at 09:53:35 AM

Кастомные конфиги с разными протоколами добавлены, так же мульти инстанс добавлен

Привет, спасибо, хороший пакет. Отправил тебе pr в github, основные добавленные фичи:
- Поддержка dual stack ipv4 ipv6 для multi instance, включая вариант когда один или несколько instance не поддерживают ipv6.
- Поддержка routing split через маршрутизацию (раздельно для ipv4 ipv6), а не средствами xray.
- Routing strategy block->proxy-direct, block->direct-proxy, system
- Поддержка bgp routing на основе community c тремя добавленными bgp peer по умолчанию.
- Поддержка dnstap  через связку пакетов dnstap-bgp - unbound, dnstap добавляется четвертым локальным bgp peer с поддержкой community (через jail net).
- Поддержка автоматического скачивания списков ip, domain и geodat файлов с категориями для block, direct, proxy и дальнейшего преобразования в правила маршрутизации через механизмы dnstap и static routing.
- Поддержка локальных extra списков block, direct, domain.
- Поддержка autorouting для multi instance на основе http 200 ok (failover) и latency http response (best instance), раздельно для ipv4 и ipv6.
- Поддержка диагностики выбора текущего маршрута для конкретного домена или ipv4/ipv6.
- Отображение emoj в instance name :-)
ну и всякие исправления/улучшения.