public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sub-net 0.0.0.0
Date: Sat, 27 Aug 2005 09:55:03 +0800	[thread overview]
Message-ID: <1125107703.5526.31.camel@rattus.localdomain> (raw)
In-Reply-To: <1125098412.20770.108.camel@sysconcept.ca>

This seems to be similar to the dlink adsl modem I am using (no routing
function).

Think of the 192.168.0.0 network as being the network between the modem
and the gateway machine.  In my case, the 10. (equiv) networks are on
the internal side of the gateway.  My gateway machine runs dhcp on eth0
(the 192.168.0.0/24 network).  When the adsl modem is unlocked, I get a
192.168.0.2 address from the adsl modem.  When locked, the 192.168.0.2
is replaced by the ISP allocated address.  The default gateway then
becomes the *ISP end* (far) of the adsl connection, and is normally set
by dhcp on your gateway machine.  The modem web server is always
reachable via 192.168.0.1, even after the ISP allocated
addresses/gateway are set.

In my case
1) ISP -> unlocked -> adsl modem -> 192.168.0.1 -> 192.168.0.2 ->gateway
-> 192.168.1.x

2) ISP -> x.x.x.x -> adsl modem -> x.x.x.(x-1) -> gateway -> 192.168.1.x
                                |                |
                                -> 192.168.0.1 ->
Edited route -n for my gateway:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0
eth1
192.168.43.0    0.0.0.0         255.255.255.0   U     0      0        0
eth2
x.x.x.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
127.0.0.0       127.0.0.1       255.0.0.0       UG    0      0        0
lo
0.0.0.0         x.x.x.21   0.0.0.0         UG    0      0        0 eth0


the .43 is a wireless network
the x.x.x.x is my ISP dhcp allocated IP as set by dhcp running on my
gateway.

I would steer clear of adding anything else to the 192.168.0.0/24
network as (in my case) things dont always work as expected (with an
accidental misconfiguration, I ended up with "wild" packets present on
my internal network).

BillK

On Fri, 2005-08-26 at 17:20 -0600, Joseph wrote:
> On Fri, 2005-08-26 at 19:04 -0300, José Pablo Ezequiel Fernández wrote:
> > > > Try this:
> > > >
> > 

...

-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2005-08-27  1:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-26 16:02 [gentoo-user] sub-net 0.0.0.0 Joseph
2005-08-26 16:05 ` Joseph
2005-08-26 17:38 ` Willie Wong
2005-08-26 17:50   ` Joseph
2005-08-26 18:21     ` A. Khattri
2005-08-26 18:23     ` Willie Wong
2005-08-26 18:47       ` Joseph
2005-08-26 18:33     ` Neil Bothwick
2005-08-26 18:51     ` Alec Shaner
2005-08-26 19:15       ` Joseph
2005-08-26 20:34     ` Nick Rout
2005-08-26 21:56       ` Joseph
2005-08-26 22:04         ` José Pablo Ezequiel Fernández
2005-08-26 23:20           ` Joseph
2005-08-26 23:32             ` Jonathan A. Kollasch
2005-08-27  0:04               ` Joseph
2005-08-27  1:55             ` William Kenworthy [this message]
2005-08-27  9:23             ` Neil Bothwick
2005-08-28  5:35               ` [gentoo-user] sub-net 0.0.0.0 [SOLVED] Joseph
2005-08-28  8:33                 ` Nick Rout
2005-08-27  1:14         ` [gentoo-user] sub-net 0.0.0.0 Nick Rout

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1125107703.5526.31.camel@rattus.localdomain \
    --to=billk@iinet.net.au \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox