OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of dariuszszyc »
  • Show Posts »
  • Messages
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

  • Messages
  • Topics
  • Attachments

Messages - dariuszszyc

Pages: [1]
1
22.7 Legacy Series / Re: OpnSense WAN stops working after upgrade to 22.7.8
« on: November 26, 2022, 10:30:02 pm »
So... I don't know why but I have this issue only when I create VLANs via OPNSense.
Once I create VLAN network devices from Proxmox - all works fine...

///
One more thing to mention - this issue happens not only with 22.7.8 but with 22.7 as well.
Somehow it worked with live CD and right after installation on HDD. But then it stops working properly.
Not sure if its because of another reboot or it just stops...

Anyway - for now I've created all VLANs via Proxmox network devices

2
22.7 Legacy Series / Re: OpnSense WAN stops working after upgrade to 22.7.8
« on: November 26, 2022, 06:50:03 pm »
FYI, even though I have all the problems - WAN (VLAN5) is able to get IP via DHCP - 192.168.3.3 .

Next thing, this message
Code: [Select]
arpresolve: can't allocate llinfo for 192.168.3.1 on vtnet0_vlan5
Disappears when I set the static IP on WAN (VLAN5). I did set it to the same one as it had from DHCP: 192.168.3.3

Once I changed IP from DHCP to fixed - my Gateway disappeared.
I added it manually but I cannot enable it (it stays disabled).


///
Routes page is also empty (not sure how ?)

3
22.7 Legacy Series / Re: OpnSense WAN stops working after upgrade to 22.7.8
« on: November 26, 2022, 06:23:39 pm »
It also seems I cannot ping the WAN gateway

Code: [Select]
# /sbin/ping -4 -S '192.168.3.3'  -c '3' '192.168.3.1'
PING 192.168.3.1 (192.168.3.1) from 192.168.3.3: 56 data bytes

--- 192.168.3.1 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
ping: sendto: Invalid argument
ping: sendto: Invalid argument
ping: sendto: Invalid argument
//
Disabling firewall completely also didn't help.

4
22.7 Legacy Series / OpnSense WAN stops working after upgrade to 22.7.8
« on: November 26, 2022, 05:57:32 pm »
Hello,

I just installed OpnSense 22.7 on my Proxmox VM, installed VLANS and all worked fine (VLANS, WAN etc).

FYI: my WAN is on vtnet0_vlan5 .

I then wanted to upgrade it to 22.7.8 which also worked.
However after reboot my WAN doesn't work anymore.

Can you please help me understand what needs to be fixed ?

In the console I see lots of messages (regarding WAN vlan):
Code: [Select]
arpresolve: can't allocate llinfo for 192.168.3.1 on vtnet0_vlan5
Here's the health audit log:

Code: [Select]
***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 22.7.8 (amd64/OpenSSL) at Sat Nov 26 16:52:17 UTC 2022
>>> Check installed kernel version
Version 22.7.7 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 22.7.7 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense
>>> Check installed plugins
No plugins found.
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
Checking all packages: .......... done
>>> Check for missing or altered package files
Checking all packages: .......... done
>>> Check for core packages consistency
Core package "opnsense" has 63 dependencies to check.
Checking packages: .
beep-1.0_1 has no upstream equivalent
Checking packages: .
ca_root_nss-3.83 has no upstream equivalent
Checking packages: .
choparp-20150613 has no upstream equivalent
Checking packages: .
cpustats-0.1 has no upstream equivalent
Checking packages: .
dhcp6c-20200512_1 has no upstream equivalent
Checking packages: .
dnsmasq-2.87,1 has no upstream equivalent
Checking packages: .
dpinger-3.2 has no upstream equivalent
Checking packages: .
expiretable-0.6_2 has no upstream equivalent
Checking packages: .
filterlog-0.6 has no upstream equivalent
Checking packages: .
flock-2.37.2 has no upstream equivalent
Checking packages: .
flowd-0.9.1_3 has no upstream equivalent
Checking packages: .
hostapd-2.10_5 has no upstream equivalent
Checking packages: .
ifinfo-13.0 has no upstream equivalent
Checking packages: .
iftop-1.0.p4 has no upstream equivalent
Checking packages: .
isc-dhcp44-relay-4.4.3P1 has no upstream equivalent
Checking packages: .
isc-dhcp44-server-4.4.3P1 has no upstream equivalent
Checking packages: .
lighttpd-1.4.67 has no upstream equivalent
Checking packages: .
monit-5.32.0 has no upstream equivalent
Checking packages: .
mpd5-5.9_12 has no upstream equivalent
Checking packages: .
ntp-4.2.8p15_5 has no upstream equivalent
Checking packages: .
openssh-portable-8.9.p1_4,1 has no upstream equivalent
Checking packages: .
openssl-1.1.1s,1 has no upstream equivalent
Checking packages: .
openvpn-2.5.8 has no upstream equivalent
Checking packages: .
opnsense-22.7.8 has no upstream equivalent
Checking packages: .
opnsense-installer-22.1 has no upstream equivalent
Checking packages: .
opnsense-lang-22.7.3 has no upstream equivalent
Checking packages: .
opnsense-update-22.7.7 has no upstream equivalent
Checking packages: .
pam_opnsense-19.1.3 has no upstream equivalent
Checking packages: .
pftop-0.8 has no upstream equivalent
Checking packages: .
php80-ctype-8.0.25 has no upstream equivalent
Checking packages: .
php80-curl-8.0.25 has no upstream equivalent
Checking packages: .
php80-dom-8.0.25 has no upstream equivalent
Checking packages: .
php80-filter-8.0.25 has no upstream equivalent
Checking packages: .
php80-gettext-8.0.25 has no upstream equivalent
Checking packages: .
php80-google-api-php-client-2.4.0 has no upstream equivalent
Checking packages: .
php80-ldap-8.0.25 has no upstream equivalent
Checking packages: .
php80-pdo-8.0.25 has no upstream equivalent
Checking packages: .
php80-pecl-radius-1.4.0b1_2 has no upstream equivalent
Checking packages: .
php80-phalcon-5.1.1 has no upstream equivalent
Checking packages: .
php80-phpseclib-3.0.16 has no upstream equivalent
Checking packages: .
php80-session-8.0.25 has no upstream equivalent
Checking packages: .
php80-simplexml-8.0.25 has no upstream equivalent
Checking packages: .
php80-sockets-8.0.25 has no upstream equivalent
Checking packages: .
php80-sqlite3-8.0.25 has no upstream equivalent
Checking packages: .
php80-xml-8.0.25 has no upstream equivalent
Checking packages: .
php80-zlib-8.0.25 has no upstream equivalent
Checking packages: .
pkg-1.17.5_1 has no upstream equivalent
Checking packages: .
py39-Jinja2-3.1.2 has no upstream equivalent
Checking packages: .
py39-dnspython-2.2.1_1,1 has no upstream equivalent
Checking packages: .
py39-netaddr-0.8.0 has no upstream equivalent
Checking packages: .
py39-requests-2.28.1 has no upstream equivalent
Checking packages: .
py39-sqlite3-3.9.15_7 has no upstream equivalent
Checking packages: .
py39-ujson-5.0.0 has no upstream equivalent
Checking packages: .
py39-vici-5.9.3 has no upstream equivalent
Checking packages: .
radvd-2.19_1 has no upstream equivalent
Checking packages: .
rrdtool-1.8.0_1 has no upstream equivalent
Checking packages: .
samplicator-1.3.8.r1_1 has no upstream equivalent
Checking packages: .
squid-5.7 has no upstream equivalent
Checking packages: .
strongswan-5.9.8_1 has no upstream equivalent
Checking packages: .
sudo-1.9.12p1 has no upstream equivalent
Checking packages: .
suricata-6.0.8_1 has no upstream equivalent
Checking packages: .
syslog-ng-3.38.1 has no upstream equivalent
Checking packages: .
unbound-1.17.0 has no upstream equivalent
Checking packages: .
wpa_supplicant-2.10_6 has no upstream equivalent
Checking packages: .
zip-3.0_1 has no upstream equivalent
***DONE***

5
Tutorials and FAQs / Re: HOWTO - Redirect all DNS Requests to Opnsense
« on: January 15, 2022, 09:32:48 pm »
Hello,

I just wanted to say that this HOWTO saved me a ton of trouble I had with my Android mobiles, that were not seeing local hosts even though they are added in the default DNS (which is piHole).

Apparently, my mobiles were still looking for them outside and so it failed.
Once I redirected all external DNS queries to my piHole - everything works great !

Thanks for this !

Pages: [1]
OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy     | XHTML | RSS | WAP2