Skip to content

Ferrumgate client not routing on Debian Trixie with mDNS #63

@aurium

Description

@aurium

Thanks for this great job!

I'm using Ferrumgate with my colleagues. Most of then using Linux Mint, I'm the only one using Debian.

Ferrumgate client works out the box for everyone, but not for Debian Trixie.

I did install ferrumgate_1.10.0_linux_amd64.deb after failed with 1.9. I didn't see difference on the problem.

It correctly writes the search on /etc/resolv.conf, but all software ignores it. I couldn't find the services behind Ferrumgate using ping, curl, firefox,... but nslookup. That guy finds the service IP.

I found a (no so good) solution here:
https://askubuntu.com/questions/81797/nslookup-finds-ip-for-a-hostname-in-local-domain-but-ping-does-not

I did this change on /etc/nsswitch.conf and everiting works:

#hosts:      files myhostname mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns
hosts:       files dns

I'm not happy, because mDNS is "a good thing™". So, I believe Ferrumgate client may interact with with libnss-mdns.

I also recommend to test the client on a fresh installed Debian Trixie. I believe it expects tool that are not provided by default.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions