Re: IPFire 3.x network configuration error

[Thomas Ebert <th.ebert@gmx.de>]

[-- Attachment #1: Type: text/plain, Size: 6926 bytes --]

Hi Michael,

i've tested the fix. It works. After that I've to delete the old 
configuration and create a new one.

Thank you.
Thomas

Am 10.03.2013 14:09, schrieb Michael Tremer:
> Hi Thomas,
>
> I just fixed the default route problem in this commit:
> http://git.ipfire.org/?p=network.git;a=commitdiff;h=2741ce5581c3dc5d34942d0b83380cf9b21ee898
>
> Just check out the git repository on your box and run make install to
> get the fix. Maybe you will have to reconfigure some ports.
>
> -Michael
>
> On Sat, 2013-03-09 at 12:04 +0100, Thomas Ebert wrote:
>> A little problem here. Network settings are working and the network is
>> autmatically configured static after a reboot.
>> The default-route which i've set isn't working:
>>
>> [root(a)ipfire3build ~]# network status upl0
>> Zone upl0 (bridge)
>>     Status                            UP
>>     MTU                          1500
>>
>>     Statistics
>>       Received        4218 packets   196k (0 errors)
>>       Sent             220 packets    30k (0 errors)
>>
>>     Spanning Tree Protocol information
>>       Version                    Spanning Tree Protocol
>>       ID                         0200.000c29057a38
>>       Priority                   512
>>       This bridge is root.
>>
>>       Topology changing          no
>>       Topology change time       0s
>>       Topology change count      0
>>
>>     Ports
>>       p0            FORWARDING  - DSR: 00:0c:29:05:7a:38 - Cost: 100
>>
>>     Configurations
>>       ipv4-static       UP
>>         IPv4 address             192.168.11.43/24
>>         Gateway                  192.168.11.5
>>
>>
>> [root(a)ipfire3build ~]# ping www.google.de
>> connect: Network is unreachable
>> [root(a)ipfire3build ~]# netstat -rn
>> Kernel IP routing table
>> Destination     Gateway         Genmask         Flags   MSS Window  irtt
>> Iface
>> 192.168.11.0    0.0.0.0         255.255.255.0   U         0 0          0
>> upl0
>> [root(a)ipfire3build ~]# ip a
>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>>       link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>>       inet 127.0.0.1/8 scope host lo
>>       inet6 ::1/128 scope host
>>          valid_lft forever preferred_lft forever
>> 2: p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>> master upl0 state UNKNOWN qlen 1000
>>       link/ether 00:0c:29:05:7a:38 brd ff:ff:ff:ff:ff:ff
>>       inet6 fe80::20c:29ff:fe05:7a38/64 scope link
>>          valid_lft forever preferred_lft forever
>> 3: upl0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
>> noqueue state UP
>>       link/ether 00:0c:29:05:7a:38 brd ff:ff:ff:ff:ff:ff
>>       inet 192.168.11.43/24 scope global upl0
>>       inet6 fe80::20c:29ff:fe05:7a38/64 scope link
>>          valid_lft forever preferred_lft forever
>>
>> Regards
>>
>> Am 09.03.2013 11:51, schrieb Thomas Ebert:
>>> 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
>>>>
>>> _______________________________________________
>>> 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
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
>