OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of schup »
  • 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 - schup

Pages: [1]
1
22.7 Legacy Series / Re: Upgraded to 22.7.4 now unable to check for updates
« on: October 19, 2022, 04:30:32 pm »
Quote from: franco on October 19, 2022, 12:49:24 pm
To be frank, the "this breaks that and then it works and now it's back" just means nothing related to updates happens to your setup that breaks intermittently for other reasons.
With the update to 22.7 this started happening to me - and not only to me.

See https://forum.opnsense.org/index.php?topic=29748.0

After a minor version update I disabled the outbound nat rule and it worked.
Now it is back to not working after the update.

I do not know what this is caused by. If you can tell me what could help in getting to the bottom of the issue I'd be happy to investigate.

2
22.7 Legacy Series / Re: Upgraded to 22.7.4 now unable to check for updates
« on: October 19, 2022, 12:33:35 pm »
I had the same problem after a previous update, a later update fixed it and it is now back with 22.7.6 (22.7.5 worked)

A ping (Interfaces > Diagnostics > Ping) doesn't work with default settings but does work when specifying the "Source Address"

To work around the update problem I created an output NAT rule.

Firewall > NAT > Outbound - see attached screenshot.

With this change ping and updat work.
Not a fix but at least updates are working.



3
22.7 Legacy Series / Re: All traffic not bound to specific interface leaves firewall as 0.0.0.0
« on: August 22, 2022, 06:16:00 pm »
Thanks a lot for this.

This finally fixed my update problem and I believe it will fix my wireguard problem as well.

I only had automatic NAT rules before - none of which changed IP.



4
22.7 Legacy Series / Re: Fetching changelog information, please wait... fetch: transfer timed out
« on: August 22, 2022, 06:13:39 pm »
I finally have a fix for my problem.

Found it in topic "All traffic not bound to specific interface leaves firewall as 0.0.0.0" -> https://forum.opnsense.org/index.php?topic=29992.0


5
22.7 Legacy Series / Re: Fetching changelog information, please wait... fetch: transfer timed out
« on: August 19, 2022, 02:13:07 pm »
None of the options worked for me
- Disabling gateway switching (wasn't on before but enabled and disabled with restarts after each change)
- Do not use the local DNS service as a nameserver for this system
- MTU is using default 1500

This breaks opensense update and Lets Encrypt certificate update.

Code: [Select]
# /sbin/ping -4 -c '3' 'example.com'
PING example.com (93.184.216.34): 56 data bytes

--- example.com ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss

When I set the source for the ping it works

Code: [Select]
# /sbin/ping -4 -S '185.151.22.135'  -c '3' '93.184.216.34'
PING 93.184.216.34 (93.184.216.34) from 185.151.22.135: 56 data bytes
64 bytes from 93.184.216.34: icmp_seq=0 ttl=58 time=92.916 ms
64 bytes from 93.184.216.34: icmp_seq=1 ttl=58 time=92.944 ms
64 bytes from 93.184.216.34: icmp_seq=2 ttl=58 time=92.844 ms

--- 93.184.216.34 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 92.844/92.901/92.944/0.042 ms

Any ideas what I can do next?

6
22.7 Legacy Series / Re: Fetching changelog information, please wait... fetch: transfer timed out
« on: August 10, 2022, 09:19:17 am »
Same for me.

From a browser https://pkg.opnsense.org/FreeBSD:13:amd64/22.7 works fine.

Code: [Select]
***GOT REQUEST TO AUDIT CONNECTIVITY***
Currently running OPNsense 22.7_4 (amd64/OpenSSL) at Tue Aug  9 17:11:20 CEST 2022
Checking connectivity for host: pkg.opnsense.org -> 89.149.211.205
PING 89.149.211.205 (89.149.211.205): 1500 data bytes

--- 89.149.211.205 ping statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss
Checking connectivity for repository (IPv4): https://pkg.opnsense.org/FreeBSD:13:amd64/22.7
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.7/latest/meta.txz: Operation timed out
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.7/latest/packagesite.pkg: Operation timed out
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.7/latest/packagesite.txz: Operation timed out
Unable to update repository OPNsense
Error updating repositories!
Checking connectivity for host: pkg.opnsense.org -> 2001:1af8:4f00:a005:5::
ping: UDP connect: No route to host
Checking connectivity for repository (IPv6): https://pkg.opnsense.org/FreeBSD:13:amd64/22.7
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.7/latest/meta.txz: Non-recoverable resolver failure
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.7/latest/packagesite.pkg: Non-recoverable resolver failure
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.7/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository OPNsense
Error updating repositories!
***DONE***

ping from OpnSense box isn't working, from a PC connecting through this box it does work however.
Code: [Select]
# /sbin/ping -4 -c '3' 'pkg.opnsense.org'
PING pkg.opnsense.org (89.149.211.205): 56 data bytes

--- pkg.opnsense.org ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss

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