On 2/4/24 09:03, Marco Moock wrote:
Am 04.02.2024 um 07:12:50 Uhr schrieb Gremlin:
I also slay all the mDNS non sense.
mDNS works fine if the host names are properly set and no other way of
setting the addresses (Unicast DNS, /etc/hosts) is being used.
It is not needed if the network is
Am 04.02.2024 um 07:12:50 Uhr schrieb Gremlin:
> I also slay all the mDNS non sense.
mDNS works fine if the host names are properly set and no other way of
setting the addresses (Unicast DNS, /etc/hosts) is being used.
--
kind regards
Marco
Spam und Werbung bitte an
On 2/4/24 02:39, Marco Moock wrote:
Am 02.02.2024 um 17:12:06 Uhr schrieb Gremlin:
On 2/2/24 16:28, Greg Wooledge wrote:
On Fri, Feb 02, 2024 at 02:03:46PM -0700, Charles Curley wrote:
root@hawk:~# host samba
samba.localdomain is an alias for hawk.localdomain.
hawk.localdomain has address
On Fri, 2024-02-02 at 16:47 -0700, Charles Curley wrote:
> On Fri, 2 Feb 2024 15:52:41 -0700
> Charles Curley wrote:
>
> > But I don't think that will solve the routing problem.
>
> Well, I was wrong. That did solve the routing problems.
>
> I moved the apt-proxy line for the VMs' benefit into
Am 02.02.2024 um 17:12:06 Uhr schrieb Gremlin:
> On 2/2/24 16:28, Greg Wooledge wrote:
> > On Fri, Feb 02, 2024 at 02:03:46PM -0700, Charles Curley wrote:
> >> root@hawk:~# host samba
> >> samba.localdomain is an alias for hawk.localdomain.
> >> hawk.localdomain has address 192.168.100.6
> >
On Fri, 2 Feb 2024 15:52:41 -0700
Charles Curley wrote:
> But I don't think that will solve the routing problem.
Well, I was wrong. That did solve the routing problems.
I moved the apt-proxy line for the VMs' benefit into a VM's /etc/hosts
and took it out of hawk's /etc/hosts. samba is now an
On Fri, 2 Feb 2024 16:52:48 -0500
Greg Wooledge wrote:
> Well, we don't know what's "right" or "wrong" on your networks. These
> are private (non-routable) addresses with no meaning to anyone but you
> and your fellow network denizens.
Agree.
>
> If you need different name resolution
On 2/2/24 16:28, Greg Wooledge wrote:
On Fri, Feb 02, 2024 at 02:03:46PM -0700, Charles Curley wrote:
root@hawk:~# host samba
samba.localdomain is an alias for hawk.localdomain.
hawk.localdomain has address 192.168.100.6
host(1) looks in DNS only. It doesn't do the standard name resolution
> > > # For the benefit of virtual machines.
> > > 192.168.100.12 apt-proxy
> > > 192.168.122.1 samba samba.localdomain
> >
> > And that's where it came from (/etc/hosts). If this IP address is
> > wrong, then it shouldn't be in here.
>
> Gnrrr. It's right for the virtual network
On Fri, 2 Feb 2024 22:10:19 +0100
Marco Moock wrote:
> Sorry for the first post.
> Your problem is located in the name resolution.
>
> Show /etc/nsswitch.conf
I have not touched this.
root@hawk:~# cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service
On Fri, 2 Feb 2024 16:28:06 -0500
Greg Wooledge wrote:
> > However, when I try to ping samba by host name:
> >
> > root@hawk:~# ping samba
> > PING samba (192.168.122.1) 56(84) bytes of data.
>
> Note that this is a *different* IP address.
Good catch, thank you.
>
> > # For the benefit of
On Fri, Feb 02, 2024 at 02:03:46PM -0700, Charles Curley wrote:
> root@hawk:~# host samba
> samba.localdomain is an alias for hawk.localdomain.
> hawk.localdomain has address 192.168.100.6
host(1) looks in DNS only. It doesn't do the standard name resolution
that applications do.
> root@hawk:~#
Am 02.02.2024 um 14:03:46 Uhr schrieb Charles Curley:
> root@hawk:~# host samba
> samba.localdomain is an alias for hawk.localdomain.
> hawk.localdomain has address 192.168.100.6
> root@hawk:~# ping samba
> PING samba (192.168.122.1) 56(84) bytes of data.
Sorry for the first post.
Your
Am 02.02.2024 um 14:03:46 Uhr schrieb Charles Curley:
> From apt-proxy (192.168.100.12): icmp_seq=2 Redirect Host(New
> nexthop: hawk.localdomain (192.168.100.6))
Check the routing table on apt-proxy.
ICMP redirect happens if you have 2 routers on the same ethernet link
and the router you try to
14 matches
Mail list logo
