From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 3.x network configuration error
Date: Sat, 09 Mar 2013 10:04:20 +0100 [thread overview]
Message-ID: <513AFB14.3010005@ipfire.org> (raw)
In-Reply-To: <513A4925.4090104@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2709 bytes --]
Hello Thomas,
thanks for your post on this list. Your described problem is a result of
a miss-configured network.
It is only possible to create a lan0 or a upl0 network zone.
A lanX network zone is a local Ethernet, which doesn't have an a default
route.
An uplX zone describes a network zone which has access to the next
"bigger" network - In most cases this will be the Internet.
Best regards,
Stefan
> I'm trying to configure my network with the network script, but it
> gives me errors.
>
> [root(a)ipfire3build ~]# uname -a
> Linux ipfire3build 3.7.7-2.ip3.i686 #1 SMP Fri Feb 15 17:32:00 UTC
> 2013 i686 GNU/Linux
>
> network zone create lan0/upl0 bridge
> network zone lan0/upl0 port add p0
> network zone lan0/upl0 config create ipv4-static
> --address=192.168.11.43 --prefix=24 --gateway=192.168.11.5
> network dns add 192.168.11.5
> network start lan0/upl0
> Job for network(a)lan0-upl0.service failed. See 'systemctl status
> network(a)lan0-upl0.service' and 'journalctl -xn' for details.
> Started service 'network(a)lan0/upl0.service', code=1.
> network status lan0/upl0
>
> [root(a)ipfire3build ~]# network status lan0/upl0
> Zone lan0/upl0 (bridge)
> Status DOWN
>
> network(a)lan0-upl0.service - Network Connectivity for zone lan0/upl0
> Loaded: loaded (/usr/lib/systemd/system/network(a).service;
> static)
> Active: failed (Result: exit-code) since Fri, 2013-03-08
> 22:23:34 CET; 21s ago
> Process: 597 ExecStart=/usr/sbin/network zone %I up
> (code=exited, status=128)
> CGroup: name=systemd:/system/network(a).service/lan0-upl0
>
> Mar 08 22:23:34 ipfire3build network[597]: [81B blob data]
> Mar 08 22:23:34 ipfire3build network[678]: bridge:
> error_log: 'hook_exec' called from
> /usr/lib/network/functions.hook:127
> Mar 08 22:23:34 ipfire3build network[597]: [81B blob data]
> Mar 08 22:23:34 ipfire3build network[680]: bridge: error_log:
> 'hook_zone_exec' called from /usr/lib/network/functions.zone:221
> Mar 08 22:23:34 ipfire3build network[597]: [67B blob data]
> Mar 08 22:23:34 ipfire3build network[597]: [68B blob data]
> Mar 08 22:23:34 ipfire3build network[597]: [47B blob data]
> Mar 08 22:23:34 ipfire3build systemd[1]: network(a)lan0-upl0.service:
> main process exited, code=exited, status=128/n/a
> Mar 08 22:23:34 ipfire3build systemd[1]: Failed to start Network
> Connectivity for zone lan0/upl0.
> Mar 08 22:23:34 ipfire3build systemd[1]: Unit
> network(a)lan0-upl0.service entered failed state
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
next prev parent reply other threads:[~2013-03-09 9:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <512FDB9A.1060009@gmx.de>
2013-03-01 12:06 ` IPFire 3.x packfire Michael Tremer
2013-03-01 12:43 ` Thomas Ebert
2013-03-07 17:38 ` Thomas Ebert
2013-03-07 23:00 ` Michael Tremer
2013-03-08 20:25 ` IPFire 3.x network configuration error Thomas Ebert
2013-03-09 9:04 ` Stefan Schantl [this message]
2013-03-09 10:51 ` Thomas Ebert
2013-03-09 11:04 ` Thomas Ebert
2013-03-10 13:09 ` Michael Tremer
2013-03-10 16:09 ` Thomas Ebert
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=513AFB14.3010005@ipfire.org \
--to=stefan.schantl@ipfire.org \
--cc=development@lists.ipfire.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