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.

Sign up for GitHub

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

PacketFence 13: dns server on a inline l2 interface should be define in the network on not on the interface. #7739

Open
fdurand opened this issue Jul 6, 2023 · 3 comments · May be fixed by #7973
Open

PacketFence 13: dns server on a inline l2 interface should be define in the network on not on the interface. #7739

fdurand opened this issue Jul 6, 2023 · 3 comments · May be fixed by #7973
Assignees
@satkunas
Labels
Priority: Low Type: Bug Type: Feature / Enhancement
Milestone
+1 (patch release)

Comments

@fdurand
Copy link
Member

fdurand commented Jul 6, 2023

Describe the bug
When you have an inline l2 interface configured then to define the dns server for this network you have to edit the interface and not in the network section.
This parameter should be close to the dhcp definition. (on the Layer2 Networks section)
@fdurand fdurand added this to the PacketFence-13.0 milestone Jul 6, 2023
@satkunas
Copy link
Contributor

satkunas commented Jul 6, 2023

DNS Servers:

  • remove from general interface
  • add to L2 networks under max lease time
  • add to L3 networks under ip addresses assigned

@satkunas satkunas modified the milestones: PacketFence-13.0, PacketFence-13.1 Jul 6, 2023
@satkunas
Copy link
Contributor

satkunas commented Jul 6, 2023

See https://github.com/inverse-inc/packetfence/tree/fix/7739

@satkunas satkunas linked a pull request Jan 16, 2024 that will close this issue
Open
@satkunas satkunas modified the milestones: PacketFence-13.1, +1 (patch release) Jan 17, 2024
@fdurand
Copy link
Member Author

fdurand commented Mar 5, 2024

The dns parameter was moved to the other place but the backend complain about missing dns server

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@satkunas satkunas

Labels
Priority: Low Type: Bug Type: Feature / Enhancement
Projects
None yet
Milestone
+1 (patch release)
Development

Successfully merging a pull request may close this issue.

Fix/7739 inverse-inc/packetfence
2 participants
@fdurand @satkunas