Hiya, just a quick note to say that using the iproute2 module, baselayout-2_alpha1 can fail to start the network device, giving the following output: * Caching service dependencies ... [ ok ] * Bringing up interface eth0 /etc/init.d/net.eth0: line 414: 0 + : syntax error: operand expected (error token is " ") * ERROR: net.eth0 failed to start On further investigation, it turns out this line deals with setting the metric, and fails on the _ifindex function from the iproute2 module. Looking in that code, it appears that it uses /proc/net/dev to determine the available interfaces, so I checked my /proc/net/dev and saw the following: Inter-| Receive | Transmit face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed lo: 42352 550 0 0 0 0 0 0 42352 550 0 0 0 0 0 0 eth0:184251109 129760 0 0 0 0 0 0 8952765 116518 0 0 0 0 0 0 cipsec0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Despite the wrapping, it shows eth0:18, looking in the iproute2 module it appears to be looking for a space following a colon (and dies when it doesn't find one). Patch to follow. Let me know if you need any further information... 5:)
Created attachment 116439 [details, diff] iproute2.sh net module patch for baselayout-2.0.0.0_alpha1
Applied to our svn repo thanks. We've also fixed ifconfig.sh as well :)
There seems to be simillar problem with bridge.sh. First it doesn't add interfaces to created bridge (brctl show only bridge br0 without interfaces ethX). Then it doesn't up new bridge interface (even when interface adding was fixed). Last it cannot add default route and vlan to new bridge (because it was down). My config: bridge_br0="eth0 eth1" config_eth0=( "null" ) config_eth1=( "null" ) vlans_br0="5" config_br0=( "ip_4_1/23" "ip_6_1/64" "ip_6_2/64" ) routes_br0=( "default via ip_4_gw" "default via ip_6_gw" ) config_br0_5=("ip_4_2/26") (ip_4*,ip_6* are real ip address) There is "a patch", I have used to start my workstation with working networking. But its not intended to be merged, because it was made by quite silly changes, just for start it asap. Maybe someone will be able to pick the main reason from it, maybe I'll later.
Created attachment 116498 [details, diff] net.Linux/bridge.sh.patch What I have done to start it with working networking. It's NOT a patch to be used :).
(In reply to comment #4) > Created an attachment (id=116498) [edit] > net.Linux/bridge.sh.patch > > What I have done to start it with working networking. > It's NOT a patch to be used :). Um, we aleady have that patch in our svn repo, but thanks anyway.
(In reply to comment #5) > Um, we aleady have that patch in our svn repo, but thanks anyway. It's different patch and I have to apply it even to this recent revision martin@jama /home/install/baselayout-2.0.0_alpha1_p1 $ svn up At revision 2615.
(In reply to comment #6) > martin@jama /home/install/baselayout-2.0.0_alpha1_p1 $ svn up > At revision 2615. Your config should work with revision 2616 ;)
*** Bug 176234 has been marked as a duplicate of this bug. ***
Fixed in baselayout-2.0.0_alpha2
