Messages

31

20.7 Legacy Series / Re: 20.7-BETA images with HBSD 12.1

« on: May 28, 2020, 07:26:20 am »

I installed it in a generation 2 vm on a windows 2019 hyper-v server. The installer hung a couple of times at the same places as have been reported before. Like before, I was able to get past by interrupting it using CTRL-C and re-logging in.

32

20.7 Legacy Series / Re: Updated to OPNsense 20.7.b_156-amd64, dhcpd6 not starting

« on: May 25, 2020, 04:53:12 am »

Every time I executed /sbin/rtsol, there was an RS and an RA, observed using wireshark.

Here is the output from the command line:

Code: [Select]

root@OPNsense:~ # /sbin/rtsol -a
root@OPNsense:~ # /sbin/rtsol -d -a
probing hn0
root@OPNsense:~ # /sbin/rtsol -D -a
probing hn0
checking if hn0 is ready...
hn0 is ready
set timer for hn0 to 0s
New timer is 0s
timer expiration on hn0, state = 1
send RS on hn0, whose state is 2
set timer for hn0 to 4s
New timer is 4s
received RA from fe80::ea4:2ff:fe29:5001 on hn0, state is 2
Processing RA
ndo = 0x1b285594c20
ndo->nd_opt_type = 1
ndo->nd_opt_len = 1
rsid = [hn0:slaac]
stop timer for hn0
there is no timer
root@OPNsense:~ #


33

20.7 Legacy Series / Re: Updated to OPNsense 20.7.b_156-amd64, dhcpd6 not starting

« on: May 25, 2020, 12:25:54 am »

pretty sure we've been down this road before with your system. I think we have to manually add a gateway for dpinger to use.

There is hn0_router and hn0_pdinfo, but no hn0_routerv6. We've done a lot of hacking over the past few years, but I don't recall ever having to manually add a gateway. The default route points to the gateway so the system already knows about it. Why would it have to be manually created?

34

20.7 Legacy Series / Re: Updated to OPNsense 20.7.b_156-amd64, dhcpd6 not starting

« on: May 24, 2020, 11:17:21 pm »

can you look in /tmp/ and see if you have a file called ***_defaultgw6 ?

There is no such file.

35

20.7 Legacy Series / Re: Updated to OPNsense 20.7.b_156-amd64, dhcpd6 not starting

« on: May 24, 2020, 08:15:34 pm »

ok, re-Read the message.  that's pretty odd... can you email me an image of the gateways single page.

Here are some screen captures.

36

20.7 Legacy Series / Re: Updated to OPNsense 20.7.b_156-amd64, dhcpd6 not starting

« on: May 24, 2020, 07:11:53 pm »

In the main gateways page the address is under 'Gateway'. Are you saying there's no entry for your WAN dhcp6 in gateways at all?

No, that's not what I meant. System: Gateways: Single shows both gateways. Interfaces: Overview WAN shows information about both gateways, but it does not report an address for the IPv6 gateway. The address isn't blank or ~, there is not even a line for it.

37

20.7 Legacy Series / Re: Updated to OPNsense 20.7.b_156-amd64, dhcpd6 not starting

« on: May 24, 2020, 06:33:25 pm »

Hmm.. I think I might know why.  If you look at system->gateways->single, is that showing an entry?

System / Gateways / Single shows both the IPv4 and IPv6 gateways.

So it it's only the lobby widget that's missing the IPv6 gateway then?

The lobby widget is reporting the IPv6 gateway address as ~ and there is no reported IPv6 gateway address in Interfaces / Overview / Wan. It's not blank or ~. There isn't a line for the address.

38

20.7 Legacy Series / Re: Updated to OPNsense 20.7.b_156-amd64, dhcpd6 not starting

« on: May 24, 2020, 06:03:49 pm »

Can you send me the output of netstat -6rW please.

Here you go:

Code: [Select]

root@OPNsense:~ # netstat -6rW
Routing tables

Internet6:
Destination        Gateway            Flags       Use    Mtu    Netif Expire
default            fe80::ea4:2ff:fe29:5001%hn0 UG     9025   1500      hn0
localhost          link#1             UH            0  16384      lo0
node-1w7jr9ql8gh2x5hajvvh1dr7k.ipv6.telus.net link#6 U          2894   1500      hn1
OPNsense           link#6             UHS           0  16384      lo0
fe80::%lo0/64      link#1             U             0  16384      lo0
fe80::1%lo0        link#1             UHS           0  16384      lo0
fe80::%hn0/64      link#5             U         83596   1500      hn0
fe80::215:5dff:fe67:5b19%hn0 link#5   UHS           0  16384      lo0
fe80::%hn1/64      link#6             U        128314   1500      hn1
fe80::215:5dff:fe67:5b1a%hn1 link#6   UHS           0  16384      lo0
root@OPNsense:~ #


39

20.7 Legacy Series / Re: Updated to OPNsense 20.7.b_156-amd64, dhcpd6 not starting

« on: May 24, 2020, 05:59:01 pm »

Hmm.. I think I might know why.  If you look at system->gateways->single, is that showing an entry?

System / Gateways / Single shows both the IPv4 and IPv6 gateways.

40

20.7 Legacy Series / Re: Updated to OPNsense 20.7.b_156-amd64, dhcpd6 not starting

« on: May 24, 2020, 01:11:53 am »

That's perfectly normal.


Under the original pfSense, and this is where Opnsense was forked from so it suffered from the same problem, with certain ISPs you needed to send a dhcp6 solicit before router advertisements or should I says you had to send both independently. Now, the problem was that pfSense would wait for a advertisement response before it launched dhcp6c, thus no advertisement response, no dhcp6c. Now, my original fix on pfSense was to to give the option to launch dhcpc6 regardless of the state of the advertisements, but the option was also added to turn that on and off.


Franco and co did some research and found that it causes no issues with ISPs that don't require it and works fine with those that do - so now the option to disable it has been removed and you could say it's permanently on, in fact they both run pretty much simultaneously.

Understood. OPNsense is receiving RA messages, so I'm not clear why the gateway status on the dashboard reports the address as ~ rather than the actual address.

41

20.7 Legacy Series / Re: Updated to OPNsense 20.7.b_156-amd64, dhcpd6 not starting

« on: May 23, 2020, 08:13:49 pm »

I used wireshark to capture DHCPv6 and ICMPv6 messages.

When OPNsense starts, the following sequence of messages are exchanged:

send ICMPv6 router solicitation
send DHCPv6 solicit
receive DHCPv6 advertise
receive ICMPv6 router advertisement
send DHCPv6 request
receive DHCPv6 reply

After that, the link is up and the gateway periodically sends router advertisement messages, at random intervals usually not longer than 30 minutes. The router advertisements come from the gateway always using the same link-local address which is used in the default route.

Later on,

Send DHCPv6 renew
Receive DHCPv6 reply

The router advertisements continued after the renew / reply.

42

20.7 Legacy Series / Re: Updated to OPNsense 20.7.b_156-amd64, dhcpd6 not starting

« on: May 19, 2020, 02:53:16 am »

A few comments / questions.

In Lobby / Dashboard / Gateways, WAN_DHCP6 shows statistics and status, but the address is ~, rather than the (link-local) address of the gateway.

In Interfaces / Overview / WAN, it shows the link-local address of the IPv6 gateway.

43

20.7 Legacy Series / Re: Updated to OPNsense 20.7.b_156-amd64, dhcpd6 not starting

« on: May 19, 2020, 12:44:51 am »

You'll find the dhcp6c debug and no-release options are now in interfaces->settings.

Would it be helpful for me to enable debug logging and post the log?

44

20.7 Legacy Series / Re: Updated to OPNsense 20.7.b_156-amd64, dhcpd6 not starting

« on: May 19, 2020, 12:36:41 am »

Do this, from the shell.


# cd /usr
# git clone https://github.com/opnsense/dhcp6c.git
# cd dhcp6c
# ./configure
# make
# killall -TERM dhcp6c
# make install


Now reboot.

Done and it's working.

45

20.7 Legacy Series / Re: Updated to OPNsense 20.7.b_156-amd64, dhcpd6 not starting

« on: May 19, 2020, 12:35:48 am »

Directly send solicit does not exist anymore, and hasn't since 20.1.1 or even earlier.

I didn't notice that. I guess that's the result of upgrading in place and not paying attention until something doesn't work.