Bug #26531
Make sure mDNS starts
Description
After installing FreeNAS I normally expect to be able to access it by http://freenas.local, and should be able to ping freenas.local. This does not work after the changes to mdns. A service like SMB must be started first in order to be able to access using mdns.
Related issues
Associated revisions
History
#1
Updated by Kris Moore about 3 years ago
- Status changed from Untriaged to Unscreened
- Assignee changed from Release Council to William Grzybowski
- Priority changed from No priority to Expected
- Target version set to 11.1
William: Please load balance
#2
Updated by William Grzybowski about 3 years ago
- Assignee changed from William Grzybowski to John Hixson
#3
Updated by Sean Fagan about 3 years ago
Also see #26168. This has been flaky -- it seems to work sometimes but not others.
#4
Updated by Dru Lavigne about 3 years ago
- Related to Bug #26168: mdns is not working added
#5
Updated by John Hixson about 3 years ago
- Status changed from Unscreened to Screened
#6
Updated by Kris Moore about 3 years ago
- Target version changed from 11.1 to 11.1-U1
#7
Updated by Dru Lavigne about 3 years ago
Note that this invalidates the Guides that ship with hardware which specifically state to connect to freenas.local.
#8
Updated by John Hixson about 3 years ago
- Status changed from Screened to 15
I'm pretty sure this is intentional. We do have options here though. We can manually register _workstation or _device-info on startup. Thoughts?
#9
Updated by John Hixson about 3 years ago
- Target version changed from 11.1-U1 to 11.1
Well, I see the problem and the fix here ;-) The middleware daemon starts early, it starts even before mdnsd does, so not even _middleware is getting registered. I need to either change the RC ordering or make the mdns plugin smart enough to hold out for mdnsd to start. Once this is done, this should fix this issue.
#10
Updated by John Hixson about 3 years ago
John Hixson wrote:
Well, I see the problem and the fix here ;-) The middleware daemon starts early, it starts even before mdnsd does, so not even _middleware is getting registered. I need to either change the RC ordering or make the mdns plugin smart enough to hold out for mdnsd to start. Once this is done, this should fix this issue.
Changing the RC order is probably very bad, so going to work on the latter.
#11
Updated by John Hixson about 3 years ago
#12
Updated by John Hixson about 3 years ago
- Status changed from 15 to Needs Developer Review
- Assignee changed from John Hixson to Release Council
#13
Updated by Dru Lavigne about 3 years ago
- Subject changed from mdns does not work until a service is started to Make sure mDNS starts
#14
Updated by Dru Lavigne about 3 years ago
- Assignee changed from Release Council to William Grzybowski
William: can you review this one?
#15
Updated by William Grzybowski about 3 years ago
- Assignee changed from William Grzybowski to Vladimir Vinogradenko
I could but Vladimir is already in the review list for the PRs, lets give him a shot first.
#16
Updated by John Hixson about 3 years ago
William Grzybowski wrote:
I could but Vladimir is already in the review list for the PRs, lets give him a shot first.
William^H^H^H^H^H^H^HPEP8 fixes have been committed.
#17
Updated by Vladimir Vinogradenko about 3 years ago
- Status changed from Needs Developer Review to Reviewed by Developer
- Assignee changed from Vladimir Vinogradenko to William Grzybowski
#18
Updated by William Grzybowski about 3 years ago
- Assignee changed from William Grzybowski to John Hixson
#19
Updated by Dru Lavigne about 3 years ago
- Status changed from Reviewed by Developer to Ready For Release
#20
Updated by Joe Maloney about 3 years ago
- Needs QA changed from Yes to No
- QA Status Test Passes FreeNAS added
- QA Status deleted (
Not Tested)
#21
Updated by Dru Lavigne about 3 years ago
- Status changed from Ready For Release to Resolved