From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] baselayout-1.12.* and "Network is unreachable"
Date: Sat, 23 Sep 2006 07:09:14 -0700 [thread overview]
Message-ID: <49bf44f10609230709rc2ba365j7969cc72b866a184@mail.gmail.com> (raw)
In-Reply-To: <20060923064613.GA4918@waltdnes.org>
> > >This all I have for eth0 is /etc/conf.d/net :
> > >
> > >routes_eth0="default via 192.168.1.1"
> > >config_eth0="192.168.1.2"
> > >
> > >Can anyone help me with this?
> > >
> > >- Grant
> >
> > I'm very sorry about the subject line. It should have read:
> >
> > "baselayout-1.12.* and "Network is unreachable"
>
> I don't see the original, so I'm replying to this message. My
> (somewhat non-standard) setup has the following lines...
>
> config_eth0="192.168.123.252 broadcast 192.168.123.255 netmask 255.255.255.248 mtu 1454"
> routes_eth0=("default via 192.168.123.254")
>
> I think that you should specify netmask and the broadcast address in
> "config_eth0". First, we need to know...
> - what IP address range is allocated to the machines behind the router?
> - what IP address does the router display to the machines behind it
> (presumably on eth1)?
>
> I've dealt with a multi-port router sitting behind a single-port ADSL
> modem, and I'm aware that you have to take care that they don't step on
> each other's address ranges.
Thank you very much. That fixed it, I needed to specify the netmask.
- Grant
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-09-23 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49bf44f10609161527h36d535dtec8e5a26800f544b@mail.gmail.com>
2006-09-16 22:28 ` [gentoo-user] Re: basalayout-1.12.* and system1 ~ # /etc/init.d/net.eth0 restart * Starting eth0 * Bringing up eth0 * 192.168.1.2 [ ok ] * Adding routes * default via 192.168.1.1 ... baselayout-1.12.* and "Network is unreachable" Grant
2006-09-23 6:46 ` [gentoo-user] " Walter Dnes
2006-09-23 14:09 ` Grant [this message]
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=49bf44f10609230709rc2ba365j7969cc72b866a184@mail.gmail.com \
--to=emailgrant@gmail.com \
--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