Re: howto isolate 2 nics?

Gene Heskett wrote:
On Friday 22 September 2006 14:00, Mikkel L. Ellertson wrote:
Gene Heskett wrote:
I got this back, but I'll sanitze the outside addresses to protect the
guilty. :-)

The default route is through eth1 with a gateway of 192.168.1.12. It
should be through eth0 with what ever gateway address is provided by
the ISP.

And then the local machines servers are not usable at the local address
using the local version of its FQDN, so this isn't a working option.

That sounds like another issue entirely. Are they accessible using
the IP address? If so, then what does /etc/resolv.conf look like? It
could be that by changing the default route, the system no longer
knows how to access the local name server.

This is why traffic for the Internet, that should go out
eth0, is going out eth1. It looks like the default route was set the
way it was in order to get to the 169.254.0.0 network through
192.168.1.12 instead of providing a proper route to that network. If
this is the case, then what is needed instead is a route specificity
for 169.254.0.0 using 192.168.1.12 as the gateway.

The 169 address is a red herring, that like 3 day old fish, should be
thrown out. Its a redhat/fedora artifact I believe, for what useage I
have no idea. All I know is its there on every fedora machine since about
FC3 or 4, my lappy FC5 has it, and it is not setup in any config file
anyplace. And it is not part of any network or subnet at that site.

I think we're losing track of the real problem by being distracted by the
169 address. We'd kill it if we knew how to do it.

Thanks, Mikkel

Does the machine at 192.168.1.12 have more then one NIC? Is it by
any chance running the name server for your local network, or
providing access to it? We may need to know more about your local
network setup to properly fix things

From the sounds of things, the default route was put in to fix a DNS
problem, instead of fixing it properly. So we have to fix that, as
well as get your routing working properly. DNS for the local network
should not depend on the default route using 192.168.1.12 as your
default gateway. Unless that machine has more then one NIC, and the
second NIC provides a connection to another network, it should not
be a gateway at all. If it does provide access to another network,
then you need to define routes to those networks.

Mikkel
--

Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: [SLE] connection redundancy
    ... which is the router just this side of the ... >>because it's own gateway is still up. ... You'll also need three network cards to put into this Linux box. ... your internal LAN can route packets to the Internet. ...
    (SuSE)
  • Re: AIX 1.3 Failures and Fables
    ... DESTINATION GATEWAY FLGS REFCNT USE INTERFACE ... Is my interpretation of the AIX 1.3 #man route correct? ... Manually manipulates the routing tables. ... Is the destination host or network. ...
    (comp.sys.ibm.ps2.hardware)
  • Re: AIX 1.3 Failures and Fables
    ... I don't know if 1.3 has SMIT or its equivalent but there should be some way to add a default gateway which is your router. ... Is my interpretation of the AIX 1.3 #man route correct? ... Manually manipulates the routing tables. ... Is the destination host or network. ...
    (comp.sys.ibm.ps2.hardware)
  • Re: One computer on 2 networks
    ... The gateway setting on the 172.30 NIC should be blank. ... If they are not all 172.30 you need to use a shorter network mask (so ... How exactly would the Route Add sentence be? ... and yours must point to the Internet gateway. ...
    (microsoft.public.windows.server.networking)
  • Re: ndiswrapper & SuSe 9.1 in Latitude D600
    ... >> another machine in my network if I give the ip address. ... > 2.Made sure to input the router as gateway. ... disable the wireless interface and just use the eth0 (eth0 is always ... Someone mentioned that if a dhcpcd process is already running the ...
    (alt.os.linux.suse)