Re: 126.0.0.0 network

From: Jonathan de Boyne Pollard (J.deBoynePollard_at_Tesco.NET)
Date: 10/21/04 

Date: Thu, 21 Oct 2004 03:42:11 GMT

GL> However, if you need to communicate with any internet destinations on
GL> the 126 network, then your private network will not route them to
GL> your firewall/gateway.

... and datagrams from everyone else addressed to 126.0.0.0/8 won't
arrive. (-:

Relevant Pages

  • Re: Zones/Containers and routing
    ... > Of course my question is why would you want to use a private network ... > space if you want to communicate with other hosts? ... which are running in a non-global zone, ...
    (comp.unix.solaris)
  • Re: route takes long time to give the table
    ... >> Nevertheless if your dns server is setup correctly ... and the response from route -n should be faster than ... Also if you have a private network and route try to ... resolve the ip's from your private network to names, ...
    (Debian-User)
  • Re: (more) the coffee house broke my auto
    ... Is the IP address of your gateway actually ... route 2 network: route add default gw outer and route private network ... host in private network zone set this: ...
    (Debian-User)
  • Re: simple routing setup ...
    ... It's not a problem routing a private network to the internet via another ... Simply connecting the interfaces and setting up the computer to route ... point to 172.17.0.1 as their default gateway, then you'll need to add a ...
    (comp.os.linux.networking)
  • Re: Why does this route not work ?
    ... Internet connectivity works fine. ... The other interface connects to a private network. ... the traceroute results do not change no matter what route I ...
    (microsoft.public.windows.server.networking)