Re: Two ISPs, One NAT'ed Internal Subnet, Firewall Policys

From: jludwig (wralphie_at_comcast.net)
Date: 09/21/04

  • Next message: James Kosin: "[FC1] ClamAV update"
    To: Daniel Bartlett <bartlett.d@gmail.com>, For users of Fedora Core releases <fedora-list@redhat.com>
    Date: Tue, 21 Sep 2004 09:37:14 -0400
    
    

    On Tue, 2004-09-21 at 05:11, Daniel Bartlett wrote:
    > Hi,
    >
    > >
    > > That's the simple part. The more interesting part is detecting the "dead"
    > > gateway, for some definition of "dead". In the typical external ADSL
    > > or cable modem configuration, there can be a failure of communication
    > > between the Linux firewall and the ADSL/cable router, between the
    > > ADSL/cable router and the ISP, and between the ISP and the wider Internet
    > > (usually due to routing screwups, etc., at the ISP). So detecting whether
    > > the local gateway (i.e., the ADSL/cable router) is alive is of only
    > > marginal utility; one usually wants to detect reachability of the wider
    > > Internet, via pinging highly-available sites, or an equivalent method.
    > >
    > > Then there is the issue of DNS resolution. For many clients, if the ISP's
    > > DNS servers are not working, the route to the internet is again of marginal
    > > utility. One can configure DNS to use the nameservers of both ISP's, though
    > > that doesn't help with certain Byzantine failures (that seem to occur in
    > > real life), where one ISP's nameserver returns nonsense. For this and
    > > other reasons, it is generally desirable to give priority to the DNS server
    > > of the ISP that you are routing through, and a more active approach to
    > > DNS server monitoring is often used.
    >
    > The DNS issue i was thinking of setting up a caching DNS server that
    > had its configs updated on the connection failing, ie for the ISP
    > nameservers.
    >
    > >
    snip

    Convoluted, but ---

    You could set up an say in INPUT, FORWARD, etc rule to look for an ICMP
    error and send that to syslog or some such that could trigger a script
    to change your ISP.

    -- 
    jludwig <wralphie@comcast.net>
    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: James Kosin: "[FC1] ClamAV update"

    Relevant Pages

    • Re: Routers and resolv.conf: [was: extremely slow to ssh out from my machine]
      ... >> ISP, and gets two nameservers from there. ... >> the router also serves names by proxy, so instead of simply passing those on ... > query-forwarding DNS server) doesn't respond to DNS queries... ...
      (Debian-User)
    • Re: Glue is different from what parent servers report
      ... we had a dns server crash, so i had to install it from scratch again, ... the second network card the ip 192.168.0.15 and started importing the ... Remove the unwanted IP addresses from the Nameservers tab, ... How to Configure OEx for Internet News ...
      (microsoft.public.windows.server.dns)
    • Re: Win2k3 DNS
      ... >own proxy DNS server to the rest of Internet; ... my other ISP. ... >customers exceeds the size alloted to the cache. ... >am using my own resolving proxy DNS server rather than the proxy DNS ...
      (microsoft.public.windows.server.dns)
    • Re: Using Microsoft DNS for Public domains
      ... I have a DMZ at my location. ... >> name I registered two nameservers at my registrar. ... >> the internal DMZ IP of the primary DNS server. ... or do I leave them as is with the private DMZ IP? ...
      (microsoft.public.windows.server.dns)
    • Re: Revers Lookup Path
      ... If that's not your ISP then you will still have to raise it with your ISP because you won't be able to deal with anyone upstream from your ISP. ... So if you use a tool to find it, it first goes to the DNS server you use and asks it for the answer, if that is authoritative for the zone it will return the answer immediately. ... Server 1 is outside our domain in a data center and is the primare DNS server for the registered domain. ... This will become the new Primary DNS server at the domain authority. ...
      (microsoft.public.windows.server.dns)