OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 17.1 Legacy Series »
  • Track Interface - RA Issue
« previous next »
  • Print
Pages: [1]

Author Topic: Track Interface - RA Issue  (Read 3676 times)

korbinian

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
    • View Profile
Track Interface - RA Issue
« on: March 20, 2017, 10:49:39 pm »
Hello,

when an interface is configured as tracking interface on an IPv6 enabled gateway, you can not configure the settings for router advertisements. Why is this only possible with an static configured interface?

Thanks.
Logged

mschaeffler

  • Newbie
  • *
  • Posts: 14
  • Karma: 0
    • View Profile
Re: Track Interface - RA Issue
« Reply #1 on: May 07, 2017, 11:19:24 am »
Hello,

I'm also interested in this question.

Thank you
Logged

djGrrr

  • Full Member
  • ***
  • Posts: 112
  • Karma: 22
    • View Profile
Re: Track Interface - RA Issue
« Reply #2 on: May 07, 2017, 04:35:57 pm »
Track interface automatically enables and configures Router Advertisements when it get's it's prefix delegation.
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 13671
  • Karma: 1175
    • View Profile
Re: Track Interface - RA Issue
« Reply #3 on: May 08, 2017, 06:40:00 am »
Let's ask a different question... what setting do you want to change?


Cheers,
Franco
Logged

djGrrr

  • Full Member
  • ***
  • Posts: 112
  • Karma: 22
    • View Profile
Re: Track Interface - RA Issue
« Reply #4 on: May 08, 2017, 03:52:24 pm »
Personally i think that Router Advertisements should be able to be configured for Track Interface interfaces.
Even the DHCPv6 server should be able to be configured, with Static Mappings, Range and Prefix Delegation Range config options being disabled when Track Interface is used. It should be easy enough to startup the DHCPv6 server when a valid range has been assigned to the interfaces, just like it starts up the RA deamon.
Logged

mschaeffler

  • Newbie
  • *
  • Posts: 14
  • Karma: 0
    • View Profile
Re: Track Interface - RA Issue
« Reply #5 on: May 08, 2017, 06:03:17 pm »
Hello,

I would like to use DHCPv6 to get the IPV6 addresses (leases) available via DNS.
Logged

korbinian

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
    • View Profile
Re: Track Interface - RA Issue
« Reply #6 on: May 10, 2017, 12:41:10 pm »
Quote from: djGrrr on May 08, 2017, 03:52:24 pm
Personally i think that Router Advertisements should be able to be configured for Track Interface interfaces.
Even the DHCPv6 server should be able to be configured, with Static Mappings, Range and Prefix Delegation Range config options being disabled when Track Interface is used. It should be easy enough to startup the DHCPv6 server when a valid range has been assigned to the interfaces, just like it starts up the RA deamon.

I am with djGrrr. Configurable Router Advertisements and DHCPv6 with Track Interface interfaces would be the feature for me to switch to OPNsense in production.
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 13671
  • Karma: 1175
    • View Profile
Re: Track Interface - RA Issue
« Reply #7 on: May 10, 2017, 03:43:21 pm »
Jolly good, who's up for some coding? :)
Logged

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • Archive »
  • 17.1 Legacy Series »
  • Track Interface - RA Issue
 

OPNsense is an OSS project © Deciso B.V. 2015 - 2023 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2