OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

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

Pages: 1 [2]
16
23.1 Legacy Series / Re: IPv6 PD not work after update OPNSense from 22.7.11->23.1
« on: February 02, 2023, 03:54:42 pm »
Quote from: cayenne on February 02, 2023, 02:54:38 pm

In fact, it is as soon as I do "Apply changes" without having changed anything that IPv6 comes back for a while and the IPv6 default route is added in OPNSense.

now, as soon as "Apply changes" without having changed anything, IPv6 does not work at all

17
23.1 Legacy Series / Re: IPv6 PD not work after update OPNSense from 22.7.11->23.1
« on: February 02, 2023, 03:48:48 pm »
Quote from: franco on February 02, 2023, 03:35:53 pm
Sorry, vtnet2 it is indeed.

So.... you don't have a primary router IP but you say it works?

/tmp/vtnet2:slaac_routerv6 is created as a fallback but that apparently doesn't work.

Can you try the following?

# rm /tmp/vtnet2_oldip
# /usr/local/etc/rc.newwanipv6 vtnet2

Still not working? Try:

# rm /tmp/vtnet2_oldip /tmp/vtnet2:slaac_routerv6
# /usr/local/etc/rc.newwanipv6 vtnet2


Cheers,
Franco

"So.... you don't have a primary router IP but you say it works?" :
This is the IPv6 of the OPNSense router and not that of the Freebox.
It only works for a certain time after applying any configuration

# rm /tmp/vtnet2_oldip
# /usr/local/etc/rc.newwanipv6 vtnet2

it is rather  "rm /tmp/vtnet2_oldip6" ?

Code: [Select]
# rm /tmp/vtnet2_oldip6
# /usr/local/etc/rc.newwanipv6 vtnet2

it worked for a few minutes and "Unable to reach the destination network" as usual what no change.

Code: [Select]
# rm /tmp/vtnet2_oldip6 /tmp/vtnet2:slaac_routerv6
rm: /tmp/vtnet2_oldip6: No such file or directory
# /usr/local/etc/rc.newwanipv6 vtnet2

it doesn't work, IPv6 didn't come back at all after the 2 commands

18
23.1 Legacy Series / Re: IPv6 PD not work after update OPNSense from 22.7.11->23.1
« on: February 02, 2023, 03:24:21 pm »
Quote from: franco on February 02, 2023, 03:04:42 pm
# ls /tmp/opt2_*v6

What files do you have and what contents do they have when it works vs. when it doesn't?


Cheers,
Franco

"ls /tmp/vtnet2_*v6" rather than "ls /tmp/opt2_*v6" ?

When it works :
Code: [Select]
# ls /tmp/opt2_*v6
ls: No match.

Code: [Select]
# ls /tmp/vtnet2_*v6
/tmp/vtnet2_oldipv6


Code: [Select]
# ls /tmp/
.interfaces.apply               filter_update_tables.lock       opnsense_menu_cache.xml         php-fastcgi.socket-1            rules.debug                     template_sample                 unbound-download_blocklists.tmp vtnet2_oldipv6
configdmodelfield.data          gateway_list.json               pfctl_si_out                    pkg_update.out                  rules.debug.old                 tmpHOSTS                        unbound_start.lock
ddb.conf                        lighttpdcompress                pfctl_ss_out                    pkg_upgrade.json                rules.limits                    unbound-blocklists.conf         vtnet2:slaac_nameserverv6
filter.lock                     opnsense_acl_cache.json         php-fastcgi.socket-0            pkg_upgrade.progress            syslog_applications.json        unbound-blocklists.conf.cache   vtnet2:slaac_routerv6

Content /tmp/vtnet2_oldipv6 :
2a01:e0a:1fc:4xx0:xxxx:xxxx:xxxx:xxxx

it's IPv6 WAN_FTTH_Freebox interface (opt2, vtnet2)





When it not works :
Code: [Select]
# ls /tmp/opt2_*v6
ls: No match.

Code: [Select]
# ls /tmp/vtnet2_*v6
/tmp/vtnet2_oldipv6

Code: [Select]
# ls /tmp/
.interfaces.apply               filter_update_tables.lock       opnsense_menu_cache.xml         php-fastcgi.socket-1            rules.debug                     template_sample                 unbound-download_blocklists.tmp vtnet2_oldipv6
configdmodelfield.data          gateway_list.json               pfctl_si_out                    pkg_update.out                  rules.debug.old                 tmpHOSTS                        unbound_start.lock
ddb.conf                        lighttpdcompress                pfctl_ss_out                    pkg_upgrade.json                rules.limits                    unbound-blocklists.conf         vtnet2:slaac_nameserverv6
filter.lock                     opnsense_acl_cache.json         php-fastcgi.socket-0            pkg_upgrade.progress            syslog_applications.json        unbound-blocklists.conf.cache   vtnet2:slaac_routerv6



Content /tmp/vtnet2_oldipv6 :
2a01:e0a:1fc:4xx0:xxxx:xxxx:xxxx:xxxx

it's IPv6 WAN_FTTH_Freebox interface (opt2, vtnet2)


no difference

19
23.1 Legacy Series / Re: IPv6 PD not work after update OPNSense from 22.7.11->23.1
« on: February 02, 2023, 02:54:38 pm »
Quote from: franco on February 02, 2023, 01:39:40 pm
These "no IP change" messages are the RAs from your provider or upstream router. They are used to pass on SLAAC connectivity information. It doesn't disable/enable a gateway...

Perhaps if you can better describe how 22.7 and 23.1 behave differently in log messages and ifconfig and ping behaviour i can help.


Cheers,
Franco

I don't know what I had as a message before version 23.1 as I wasn't looking at the logs as I had no problems.

In any case, the default IPv6 route disappears at the same time as the "no IP change" log appears.
After the disappearance of the IPv6 default route, The hosts "Unable to reach the destination network."

In fact, it is as soon as I do "Apply changes" without having changed anything that IPv6 comes back for a while and the IPv6 default route is added in OPNSense.

20
23.1 Legacy Series / Re: IPv6 PD not work after update OPNSense from 22.7.11->23.1
« on: February 02, 2023, 01:36:22 pm »
Quote from: franco on February 02, 2023, 01:29:27 pm
SLAAC does not offer a prefix, so no prefix delegation takes place. I'm not sure what you had on 22.7 but indeed SLAAC behaved a bit differently there, but I think it was worse before...


Cheers,
Franco

I may have misspoken but what I mean is, I have IPv6 routing through the Prefix Delegation provided by the Freebox

I'm looking for the problem that makes IPv6 not work on version 23.1. apart from disabling/enabling the IPv6 gateway in OPNSence every 5 minutes

21
23.1 Legacy Series / IPv6 PD not work after update OPNSense from 22.7.11->23.1_6
« on: February 02, 2023, 12:00:00 pm »
Hello,
Yesterday, I updated OPNSense from 22.7.11->23.1_6.

Since the upgrade to version 23.1_6, the IPv6 default route disappears



My configuration did not change after the update



My configuration IPv6 is the prefix delegation for the OPNSense LAN.
The WAN interface is configured by SLAAC.
The LAN interface is configured to static IPv6.
Radvd advertises the /64 prefix.



After the upgrade, IPv6 does not work. The default route disappears after 3-5 minutes (the time for the IPv6 default route to disappear is random).

When the default route disappears, I have a line in log files : General :
2023-02-02T11:14:58   Notice   opnsense   /usr/local/etc/rc.newwanipv6: No IP change detected for WAN_FTTH_Freebox[opt2]


When I disable/enable the IPv6 gateway, IPv6 is OK but not more than 3-5 minutes with the same message in the logs :
2023-02-02T11:14:58   Notice   opnsense   /usr/local/etc/rc.newwanipv6: No IP change detected for WAN_FTTH_Freebox[opt2]

I have the default route disappearing at the same time.



Here is an IPv6 network diagram


Here is IPv6 PD on the Freebox (Router)




additional information added on 12/02/2023 :
I have just tried to analyse what is happening with a network analyser.

As soon as OPNSense receives an ICMPv6 type 134 (RA: Router Advertisement) from the Freebox, OPNSense removes the IPv6 default route

The IPv6 default route comes back when I disable/reactivate the IPv6 gateway in web interface system_gateways.php.

22
21.7 Legacy Series / Re: After updating to Opnsense 21.7, the webgui does not start automatically.
« on: October 02, 2021, 07:46:56 pm »
I have just updated in version 21.7.3_3 and the issue is aready present

23
21.7 Legacy Series / Re: After updating to Opnsense 21.7, the webgui does not start automatically.
« on: September 27, 2021, 07:23:20 pm »
Last Log Files Web Gui :
Code: [Select]
Date Process Line
2021-09-27T18:43:59 lighttpd[16053] (server.c.1513) server started (lighttpd/1.4.59)
2021-09-27T18:43:59 lighttpd[20226] (server.c.1976) server stopped by UID = 0 PID = 8327
2021-09-27T18:43:58 lighttpd[20226] (server.c.1513) server started (lighttpd/1.4.59)
2021-09-27T18:21:53 lighttpd[12807] (server.c.1513) server started (lighttpd/1.4.59)
2021-09-27T18:20:27 lighttpd[43189] (server.c.1513) server started (lighttpd/1.4.59)
2021-09-27T18:20:27 lighttpd[48810] (server.c.1976) server stopped by UID = 0 PID = 82892
2021-09-27T18:17:35 lighttpd[48810] (server.c.1513) server started (lighttpd/1.4.59)
2021-09-27T17:36:00 lighttpd[34226] (server.c.1513) server started (lighttpd/1.4.59)
2021-09-27T17:33:29 lighttpd[29391] (server.c.1513) server started (lighttpd/1.4.59)
2021-09-27T17:26:48 lighttpd[65435] (server.c.1513) server started (lighttpd/1.4.59)
2021-09-27T17:26:48 lighttpd[54568] (server.c.1976) server stopped by UID = 0 PID = 56152
2021-09-27T17:19:13 lighttpd[54568] (server.c.1513) server started (lighttpd/1.4.59)
2021-09-27T17:19:13 lighttpd[39628] (server.c.1976) server stopped by UID = 0 PID = 37764
2021-09-27T17:14:26 lighttpd[39628] (server.c.1513) server started (lighttpd/1.4.59)
2021-09-27T17:07:03 lighttpd[22483] (server.c.1513) server started (lighttpd/1.4.59)
2021-09-08T14:02:31 lighttpd[30903] (server.c.1513) server started (lighttpd/1.4.59)
2021-09-08T14:02:31 lighttpd[89385] (server.c.1976) server stopped by UID = 0 PID = 97959
2021-08-17T01:37:40 lighttpd[89385] (server.c.1513) server started (lighttpd/1.4.59)
2021-07-09T18:34:02 lighttpd[80133] (server.c.1513) server started (lighttpd/1.4.59)
2021-07-08T23:35:11 lighttpd[91414] (server.c.1513) server started (lighttpd/1.4.59)
2021-07-08T23:28:17 lighttpd[83152] (server.c.1513) server started (lighttpd/1.4.59)
2021-07-08T23:26:48 lighttpd[61459] (server.c.1513) server started (lighttpd/1.4.59)
2021-07-08T23:26:48 lighttpd[73643] (server.c.1976) server stopped by UID = 0 PID = 11541
2021-07-04T18:48:10 lighttpd[73643] (server.c.1513) server started (lighttpd/1.4.59)
2021-07-04T18:48:10 lighttpd[50795] (server.c.1976) server stopped by UID = 0 PID = 95346
2021-07-01T21:20:57 lighttpd[50795] (server.c.1513) server started (lighttpd/1.4.59)
2021-07-01T21:19:29 lighttpd[2372] (server.c.1513) server started (lighttpd/1.4.59)
2021-07-01T19:19:29 lighttpd[68214] (server.c.1971) server stopped by UID = 0 PID = 22117
2021-06-26T11:49:48 lighttpd[68214] (server.c.1508) server started (lighttpd/1.4.58)
2021-06-26T07:53:58 lighttpd[89979] (server.c.1508) server started (lighttpd/1.4.58)
2021-06-26T07:53:58 lighttpd[9037] (server.c.1971) server stopped by UID = 0 PID = 39290
2021-06-26T07:51:30 lighttpd[9037] (server.c.1508) server started (lighttpd/1.4.58)
2021-06-26T07:51:30 lighttpd[45964] (server.c.1971) server stopped by UID = 0 PID = 44449
2021-06-26T07:51:05 lighttpd[45964] (server.c.1508) server started (lighttpd/1.4.58)
2021-06-26T07:51:05 lighttpd[9011] (server.c.1971) server stopped by UID = 0 PID = 72144
2021-06-26T07:49:29 lighttpd[9011] (server.c.1508) server started (lighttpd/1.4.58)
2021-06-26T07:49:29 lighttpd[27547] (server.c.1971) server stopped by UID = 0 PID = 23214
2021-06-26T07:47:57 lighttpd[27547] (server.c.1508) server started (lighttpd/1.4.58)
2021-06-26T07:47:57 lighttpd[48881] (server.c.1971) server stopped by UID = 0 PID = 47848
2021-06-26T07:47:22 lighttpd[48881] (server.c.1508) server started (lighttpd/1.4.58)
2021-06-26T07:47:22 lighttpd[10307] (server.c.1971) server stopped by UID = 0 PID = 85425
2021-06-26T07:45:03 lighttpd[10307] (server.c.1508) server started (lighttpd/1.4.58)
2021-06-25T19:42:51 lighttpd[8674] (server.c.1508) server started (lighttpd/1.4.58)
2021-06-25T19:21:04 lighttpd[75477] (server.c.1508) server started (lighttpd/1.4.58)

24
21.7 Legacy Series / After updating to Opnsense 21.7, the webgui does not start automatically.
« on: September 27, 2021, 07:18:48 pm »
Hello,
I updated Opnsense to version 21.7 and since the update, each time I start Opnsense, I can't access the web interface.
every time I start Opnsense, I have to restart the webgui to have access to the web interface with the command :
Code: [Select]
configctl webgui restart

Pages: 1 [2]
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