Re: Network Problem: Redirection
On Fri, 2024-02-02 at 16:47 -0700, Charles Curley wrote:
> On Fri, 2 Feb 2024 15:52:41 -0700
> Charles Curley <charlescurley@charlescurley.com> 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 alias in the
> virtual zone, so I don't need that line at all.
>
> Thanks, Greg, for spotting that. Sometimes I'm dense. It took me a
> while to realize what you were getting at.
>
This is not a routing problem in the first place.
If you have a DNS server configured that can resolve for you LAN(s)
(like you should), you don't need to (and should not) change anything
in /etc/hosts. When you specify different addresses for the same host
at arbitrary places, you're likely to create confusion, especially
when you're using addresses that are supposed to have the same
meaning. If you need to specify different names for the same host,
use CNAME records. If you need to specify different addresses for the
same host, use different host names (at least I don't have a better
idea for that).
If you have vlans in use, make sure the addresses in the networks do
not overlap. Otherwise your networks may not be as virtual as you
think, vlans or not, and you may create something that looks like a
routing problem. If you're not using vlans and want virtual netwoks,
it's probably a very good idea to use vlans (and to use routing if
desirable and necessary).
Reply to: