Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

radvd does not start #1273

Closed
Shadesh opened this issue Nov 24, 2016 · 19 comments
Closed

radvd does not start #1273

Shadesh opened this issue Nov 24, 2016 · 19 comments
Assignees
@fichtner
Labels
bug Production bug
Milestone
17.1

Comments

@Shadesh
Copy link

Shadesh commented Nov 24, 2016

On OPNsense 16.7.9-amd64 the radvd service dies and never comes up again. My setup is simple, i get new IPv6 subnets via DHCP from my ISP. My WAN interface has one /128 address and the LAN interface gets a /64 assigned.

The radvd service dies everytime this happens:

Nov 24 18:31:47 gw opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Informational is starting re0.
Nov 24 18:31:47 gw opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: on (IP address: 2001::::a585:fe6d::1230) (interface: wan) (real interface: re0).
Nov 24 18:31:48 gw opnsense: /usr/local/etc/rc.newwanipv6: ROUTING: setting IPv4 default route to 111.122.133.1

There is no error or something when i try to start it via the webinterface. It just does not start. When is start it via Shell, it's up, working and the "green" symbol is also shown at the dashboard, but everytime the script rc.newwanipv6 runs, it stops again... This didn't happen on a previous release.

Anyone with the same problem?
@netrixtardis
Copy link

netrixtardis commented Nov 25, 2016 •
edited

I just encountered this bug (or I did not notice it until after I rebooted). It was working even after the upgrade to OPNsense 16.7.9-i386 earlier in the week, but I had not performed a reboot. After a reboot a couple of hours ago, I noticed it did not come back. I've re-configured my device to remove IPv6 configuration, and re-did them to no change. not even sure where to troubleshoot the issue....

For the time being I have reverted back to 16.7.8 using the following method:
opnsense-update -sn "MINT/16.7.8/OpenSSL"
opnsense-update -pf

and a reboot for good measure. This has restored radvd functions.

@netrixtardis
Copy link

Looks like a lot of work done under commit: ab1cf69 tagged for 16.7.9. May be the commit that broke radvd.

@fichtner
Copy link
Member

Hi guys,

Right, I needed to make sure that the following works... On 16.7.9 run this command to undo the commit (rerun to reapply, etc.):

# opnsense-patch ab1cf69

If it works afterwards, I'm going to need both /var/etc/radvd.conf files from when this works and when it doesn't.

Please send to franco AT opnsense DOT org

Thanks,
Franco

@fichtner fichtner self-assigned this Nov 25, 2016
@fichtner fichtner added the bug Production bug label Nov 25, 2016
@fichtner fichtner added this to the 17.1 milestone Nov 25, 2016
@netrixtardis
Copy link

Performed as requested, undoing the commit has made radvd work normally. I compared radvd.conf between each time - they are identical. The commit changed something else breaking radvd.

@fichtner
Copy link
Member

ok, will take a closer look at the commit, thanks for testing so far

@fichtner
Copy link
Member

@netrixtardis what's your setting for ra mode? and is dhcpv6 enabled in your setup or not?

@Shadesh
Copy link
Author

Shadesh commented Nov 25, 2016

Same here. No DHCPv6 enabled, only radvd to distribute the /64.

@fichtner
Copy link
Member

@Shadesh what's your selected router advertisement mode (first setting on the page)?

@netrixtardis
Copy link

netrixtardis commented Nov 25, 2016 •
edited

I am not using DHCPv6 internally to handle IPv6 address assignment.

WAN - IPv6 Configuration Type: DHCPv6
LAN - IPv6 Configuration Type: Track Interface

ISP assigns a /128 for WAN, then provides a /64 to LAN.

Most residential US IPv6 deployments don't provide static IPv6 IPs to use for configuration.

@fichtner
Copy link
Member

still need to know which router advertisement mode is set in the respective GUI page... could it be it's set to something other than "unmanaged"?

@Shadesh
Copy link
Author

Shadesh commented Nov 25, 2016

There is nothing you can set afaik. It just picks the /64 and distributes it to the LAN. Don't know the exact words (I'm at work at the moment) but when i go to the services pages for DHCPv6 and then to "Advertisements" it only says "No Interfaces with static IPv6 adresses found". but it worked like a charm before that commit. Please correct me @netrixtardis if i'm wrong here, because it looks like we're using the same setup ;)

@fichtner
Copy link
Member

this is an interesting clue. so your LAN is set to track and radvd was automatic... more code review ensues...

fichtner added a commit that referenced this issue Nov 25, 2016
@fichtner
radvd: fix two regressions from 16.7.9
0ec8569 
o Mark interface used in case of interface tracking
o Don't inject local DNS server when there is no IP

PR: #1273
@fichtner
Copy link
Member

This should do the trick:

# opnsense-patch 0ec8569

@Shadesh
Copy link
Author

Shadesh commented Nov 25, 2016

Looks good here. Let's see if it survives the next rc.newwanipv6 run ;)
Thanks!

@fichtner
Copy link
Member

fingers crossed, and thanks for the quick testing :D

@netrixtardis
Copy link

netrixtardis commented Nov 25, 2016 •
edited

Shadesh is correct. I'm going to apply the fix myself real quick and I'll report back in a little while.

Attempted update, received the following message:
Hunk #2 failed at 267.

@fichtner
Copy link
Member

You may have the the reverted patch installed. Try again after:

# pkg install -f opnsense

@netrixtardis
Copy link

Yes - that worked this time, it applied cleanly. Fix applied, and after reboot, radvd is running.

@fichtner
Copy link
Member

@netrixtardis @Shadesh thanks, closing this now. if anything else pops up let me know.

fichtner added a commit that referenced this issue Nov 28, 2016
@fichtner
radvd: fix two regressions from 16.7.9
1e3a4c3 
o Mark interface used in case of interface tracking
o Don't inject local DNS server when there is no IP

PR: #1273
(cherry picked from commit 0ec8569)
@kgleason kgleason mentioned this issue Nov 30, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fichtner fichtner

Labels
bug Production bug
Milestone
17.1
Development

No branches or pull requests
3 participants
@fichtner @Shadesh @netrixtardis