From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Ebert <th.ebert@gmx.de>
To: development@lists.ipfire.org
Subject: Re: IPFire 3.x network configuration error
Date: Sat, 09 Mar 2013 11:51:06 +0100
Message-ID: <513B141A.4020905@gmx.de>
In-Reply-To: <513AFB14.3010005@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2698459460238388764=="
List-Id: <development.lists.ipfire.org>

--===============2698459460238388764==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

Finally, i wanna say thank you for the great support.

As you described, your method works now.

Best Regards
Thomas

Am 09.03.2013 10:04, schrieb Stefan Schantl:
> 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
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
>


--===============2698459460238388764==--