Re: IPFire 3.x packfire

Re: IPFire 3.x packfire

[Michael Tremer]

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

The content of /var/cache/pakfire should be:

[root(a)rice-oxley pakfire]# pwd
/var/cache/pakfire
[root(a)rice-oxley pakfire]# ll
total 68
drwxr-xr-x.  19 root root  4096 Dec  8  2011 ccache
drwxr-xr-x  259 root root  4096 Feb 12 19:43 downloads
drwxr-xr-x.   6 root root  4096 Feb 20  2012 repos
drwxr-xr-x.   3 root root 49152 Feb 24 11:45 sources

The download directory contains the following:

[root(a)rice-oxley pakfire]# tree downloads/ | head
downloads/
├── 00
│   ├── 12c06bfdca3fa5454e4f6c3fc07a5b21e2a0e3
│   │   └── gcc-c++-4.7.2-2.ip3.i686.pfm
│   ├── 4ac3f83e78944c4df70f0319fafc650f7bc9a4
│   │   └── perl-Test-Harness-3.23-11.ip3.noarch.pfm
│   ├── 6e4f8ee4f82665e052b9d08d28410870c34794
│   │   └── cpp-4.7.2-2.ip3.i686.pfm
│   ├── aaf07ddbf21bdc95dca317881b7351577b653b
│   │   └── perl-Digest-1.16-11.ip3.noarch.pfm

There is absolutely no code that cleans up the download directory on the
builders.

Michael

On Thu, 2013-02-28 at 23:35 +0100, Thomas Ebert wrote:
> Then is something wrong with my installation:
> 
> [root(a)ipfire cache]# find . -name \.gz
> [root(a)ipfire cache]# find . -name \*.gz
> ./man/cat8/network-zone.8.gz
> ./pakfire/sources/lldpd-0.5.4.tar.gz
> ./pakfire/sources/lldpd-0.7.1.tar.gz
> [root(a)ipfire cache]# find . -name \*.bz2
> [root(a)ipfire cache]#
> 
> You see the only packages which are in there is the lldpd package which 
> first is from the packfire server and the second i manually downloaded?
> 
> What files or command output can i provide to trigger the problem?
> 
> Am 28.02.2013 23:24, schrieb Michael Tremer:
> > Hi,
> >
> > On Thu, 2013-02-28 at 22:47 +0100, Thomas Ebert wrote:
> >> I've the following problem. Everytime i want to make a package the
> >> script is entirely downloading all needed software for pakfire-builder
> >> again.
> >>
> >> Example: pakfire-builder shell
> >> ...
> >> Installing:          105  packages
> >> Installed size: 391M
> >> ...
> >>
> >> Then i'm leaving the shell and enter the command again. Then he is again
> >> downloading and installing all files with dependencies.
> >>
> >> Is it normal? That's cost much of bandwith and installation time in my
> >> virtual machine.
> > This is not normal. Repository metadata get updated when they are older
> > than 10 minutes and the package database will be downloaded when ever it
> > has changed.
> >
> > Packages will be stored in /var/cache/pakfire and of course they will be
> > reused. Maybe you have a look into that directory and check your time
> > (signatures)?
> >
> > Michael
> >
> > _______________________________________________
> > 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

Re: IPFire 3.x packfire

[Thomas Ebert]

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

Sorry. I missunderstood the output. Packfire is using local packages as 
you described. But what about the build chroot environment. Is it normal 
that the build environment is cleaned everytime if you exit from it and 
start the command "pakfire-builder shell".

Here is the paste from my shell: http://pastebin.com/fKn3UECQ

This is my configuration /etc/pakfire/builder.conf

[logger]

# Use a different log file for the builder stuff.
file = /var/log/pakfire-builder.log

[builder]
# Select the distribution to build for.
distro = ipfire3

# Use ccache in order to build rebuilds in less time.
use_ccache = true

# Use icecream in order to speed up builds.
use_icecream = false

# Create build environments in a tmpfs.
# This requires a lot of RAM.
# Only enable if you know what your are doing.
#use_tmpfs = false

# Create loop devices in build environment.
#use_loop_devices = true

Regards

Re: IPFire 3.x packfire

[Thomas Ebert]

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

Hello out there.

I know most of you are very busy at the moment, but could anybody of you 
provide an answer of my question?
... Is it normal that the build environment is cleaned everytime if you 
exit from it and start the command "pakfire-builder shell"?

Regards
Thomas

Am 01.03.2013 13:43, schrieb Thomas Ebert:
> Sorry. I missunderstood the output. Packfire is using local packages 
> as you described. But what about the build chroot environment. Is it 
> normal that the build environment is cleaned everytime if you exit 
> from it and start the command "pakfire-builder shell".
>
> Here is the paste from my shell: http://pastebin.com/fKn3UECQ
>
> This is my configuration /etc/pakfire/builder.conf
>
> [logger]
>
> # Use a different log file for the builder stuff.
> file = /var/log/pakfire-builder.log
>
> [builder]
> # Select the distribution to build for.
> distro = ipfire3
>
> # Use ccache in order to build rebuilds in less time.
> use_ccache = true
>
> # Use icecream in order to speed up builds.
> use_icecream = false
>
> # Create build environments in a tmpfs.
> # This requires a lot of RAM.
> # Only enable if you know what your are doing.
> #use_tmpfs = false
>
> # Create loop devices in build environment.
> #use_loop_devices = true
>
> Regards

Re: IPFire 3.x packfire

[Michael Tremer]

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

Yes, the build environment is cleaned up after every build. This is
intentional, so you start every build in a clean environment and don't
get caught up in any errors.

However, the downloaded package files are never deleted.

Are you sure you see a re-download or just the extraction?

-Michael

On Thu, 2013-03-07 at 18:38 +0100, Thomas Ebert wrote:
> Hello out there.
> 
> I know most of you are very busy at the moment, but could anybody of you 
> provide an answer of my question?
> ... Is it normal that the build environment is cleaned everytime if you 
> exit from it and start the command "pakfire-builder shell"?
> 
> Regards
> Thomas
> 
> Am 01.03.2013 13:43, schrieb Thomas Ebert:
> > Sorry. I missunderstood the output. Packfire is using local packages 
> > as you described. But what about the build chroot environment. Is it 
> > normal that the build environment is cleaned everytime if you exit 
> > from it and start the command "pakfire-builder shell".
> >
> > Here is the paste from my shell: http://pastebin.com/fKn3UECQ
> >
> > This is my configuration /etc/pakfire/builder.conf
> >
> > [logger]
> >
> > # Use a different log file for the builder stuff.
> > file = /var/log/pakfire-builder.log
> >
> > [builder]
> > # Select the distribution to build for.
> > distro = ipfire3
> >
> > # Use ccache in order to build rebuilds in less time.
> > use_ccache = true
> >
> > # Use icecream in order to speed up builds.
> > use_icecream = false
> >
> > # Create build environments in a tmpfs.
> > # This requires a lot of RAM.
> > # Only enable if you know what your are doing.
> > #use_tmpfs = false
> >
> > # Create loop devices in build environment.
> > #use_loop_devices = true
> >
> > Regards
> 
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development

IPFire 3.x network configuration error

[Thomas Ebert]

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

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

Re: IPFire 3.x network configuration error

[Stefan Schantl]

[-- 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

Re: IPFire 3.x network configuration error

[Thomas Ebert]

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

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
>

Re: IPFire 3.x network configuration error

[Thomas Ebert]

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

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
>

Re: IPFire 3.x network configuration error

[Michael Tremer]

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

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

Re: IPFire 3.x network configuration error

[Thomas Ebert]

[-- 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
>