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

How does company router install packerbeat? #92

Open
Iateautumn opened this issue Oct 16, 2024 · 4 comments · May be fixed by #98
Open

How does company router install packerbeat? #92

Iateautumn opened this issue Oct 16, 2024 · 4 comments · May be fixed by #98
Assignees

Comments

@Iateautumn
Copy link

Hi

I want to install new application in hosts, however it seems that there is no any dns configuration in all host of socbed, which means they are not capable to resolve any domain name, but how does this ansible script work:

- name: Download packetbeat to /tmp
  get_url:
    url: "https://artifacts.elastic.co/downloads/beats/packetbeat/{{ packetbeat_name }}.tar.gz"
    dest: "/tmp"
  retries: 2
  register: result
  until: result is succeeded

by the way, I find that the gateway of internet router disappear sometimes, do you have any idea of this?

if my memory serves me right, all hosts can visit external network by ip instead of domain because internet router have a network interface which is nat mode, and none of them configure dns right?

thanks

@Iateautumn Iateautumn changed the title How does comany router install packerbeat? How does company router install packerbeat? Oct 16, 2024
@Iateautumn
Copy link
Author

oh, I find that unbound serve as a dns resolver in socbed, but they sometimes don't work well, hence I update internet router to latest version. It seems unbound works well in most cases

@Maspital Maspital self-assigned this Oct 23, 2024
@Maspital
Copy link
Collaborator

Hi, sorry for the long wait (here and in your other issue) — development for this project finished over two years ago, so we can’t answer most questions off the top of our heads without revisiting the details ourselves.
Your issues are definitely helpful and appreciated, but it does take some time to resolve them as day-to-day priorities often take precedence.

Regarding this issue, I'll first check which parts of the provisioning process break when IPFire is upgraded a couple of versions. Perhaps its also a feasible solution to leave it as is and upgrade in the last step of the corresponding ansible playbook.

@Maspital
Copy link
Collaborator

Maspital commented Oct 28, 2024

oh, I find that unbound serve as a dns resolver in socbed, but they sometimes don't work well, hence I update internet router to latest version. It seems unbound works well in most cases

By "updating", do you mean to latest core version of 2.25 or to the next version 2.29? The former didn't work reliably for me, I haven't tried the latter (as it has somewhat major implications for provisioning). I found that setting the DNS server manually seems to prevent the issue.

@Iateautumn
Copy link
Author

oh, I find that unbound serve as a dns resolver in socbed, but they sometimes don't work well, hence I update internet router to latest version. It seems unbound works well in most cases

By "updating", do you mean to latest core version of 2.25 or to the next version 2.29? The former didn't work reliably for me, I haven't tried the latter (as it has somewhat major implications for provisioning). I found that setting the DNS server manually seems to prevent the issue.

hello, sry for late replay, we solve this problem by updating ipfire from 2.25 to 2.29 and setting DNS server manually. you can see it in detail from the issur proposed by 1ncludeSteven. I have no idea if it work well by only setting DNS server. We just update ipfire considering our following work.

@Maspital Maspital linked a pull request Nov 4, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants