Development April 2016

development@lists.ipfire.org

12 participants
112 discussions

RE: Re: Possible configuration bug with >6 nics
by g6094199＠freenet.de 29 Apr '16

29 Apr '16

Hi Michael, as i said all nics are shown, even in ip link: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: mtu 1500 qdisc fq_codel master red0 state DOWN mode DEFAULT group default qlen 1000 link/ether 00:90:7f:41:2d:25 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc fq_codel master red0 state DOWN mode DEFAULT group default qlen 1000 link/ether 00:90:7f:41:2d:24 brd ff:ff:ff:ff:ff:ff 4: eth2: mtu 1500 qdisc fq_codel master red0 state DOWN mode DEFAULT group default qlen 1000 link/ether 00:90:7f:41:2d:23 brd ff:ff:ff:ff:ff:ff 5: green0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 00:90:7f:41:2d:22 brd ff:ff:ff:ff:ff:ff 6: eth4: mtu 1500 qdisc fq_codel master red0 state UP mode DEFAULT group default qlen 1000 link/ether 00:90:7f:41:2d:21 brd ff:ff:ff:ff:ff:ff 7: eth5: mtu 1500 qdisc fq_codel master red0 state DOWN mode DEFAULT group default qlen 1000 link/ether 00:90:7f:41:2d:20 brd ff:ff:ff:ff:ff:ff 8: eth6: mtu 1500 qdisc fq_codel master red0 state DOWN mode DEFAULT group default qlen 1000 link/ether 00:90:7f:41:2d:1f brd ff:ff:ff:ff:ff:ff 9: eth3: mtu 1500 qdisc fq_codel master red0 state DOWN mode DEFAULT group default qlen 1000 link/ether 00:90:7f:41:2d:1e brd ff:ff:ff:ff:ff:ff 10: red0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default link/ether 00:90:7f:41:2d:1e brd ff:ff:ff:ff:ff:ff There ist no scroll bar in the setup. Also if you try to scroll down nothing happens. setup.log is empty Since i'm running Core 100 (fresh embedded install), the limitation doesnt seem to be fixed. I'm attaching an setup screenshot to your private mail. regards sash > -----Ursprüngliche Nachricht----- > Von: Michael Tremer > Gesendet: Do. 28.04.2016 19:25 > An: g6094199(a)freenet.de, development(a)lists.ipfire.org > Betreff: Re: Possible configuration bug with >6 nics > > Hello, > > there was a limit prior to Core Update 100 but this should have gone away and > actually 20 NICs should be shown by now. > > Did you try to scroll down? Are there any errors shown? > > What is the output of "ip link"? > > Best, > -Michael > > On Thu, 2016-04-28 at 16:52 +0200, g6094199(a)freenet.de wrote: >> He guys! >> >> i recently installed IPFire core 100 to an Watchguard Firebox X 750e/1000e. >> All installed to an CF-card, booted up fine. >> Came to the general setup and asked to map the nics to an interface. While the >> x750 has 8 nics (4x Marvell 88E8001, 4x 88E8053) only 6 nics are shown in the >> setup menue via serial port. which seems to be a limitation by the GUI or a >> bug. >> >> I can see als of the interfaces on cli after i finished the initial setup >> >> lspci: >> 01:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E >> Gigabit Ethernet Controller (rev 19) >> 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E >> Gigabit Ethernet Controller (rev 19) >> 03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E >> Gigabit Ethernet Controller (rev 19) >> 04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E >> Gigabit Ethernet Controller (rev 19) >> 05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit >> Ethernet Controller (rev 13) >> 05:01.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit >> Ethernet Controller (rev 13) >> 05:02.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit >> Ethernet Controller (rev 13) >> 05:03.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit >> Ethernet Controller (rev 13) >> >> I also can use them. So it seems to be a limitation/bug of the setup menue?! >> >> Any thoughs? >> >> >> regards >> sash >> >> >> --- >> Mail & Cloud Made in Germany mit 3 GB Speicher! Jetzt kostenlos anmelden> > > -----Ursprüngliche Nachricht Ende---- --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! https://email.freenet.de/mail/Uebersicht?epid=e9900000451

2 1

[PATCH] Zoneedit: Provide better error message on error 702 responses.
by Stefan Schantl 29 Apr '16

29 Apr '16

A returned error code 702 when using Zoneedit as provider now raise a request error with an corresponding message instead of a simple InternalServerError exception. This will help to clarify and debug update problems. Fixes #11042. Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org> --- src/ddns/providers.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/ddns/providers.py b/src/ddns/providers.py index 3845193..dbe9261 100644 --- a/src/ddns/providers.py +++ b/src/ddns/providers.py @@ -1576,7 +1576,7 @@ class DDNSProviderZoneedit(DDNSProvider): elif output.startswith("<ERROR CODE=\"704\""): raise DDNSRequestError(_("No valid FQDN was given.")) elif output.startswith("<ERROR CODE=\"702\""): - raise DDNSInternalServerError + raise DDNSRequestError(_("Too frequent update requests have been sent.")) # If we got here, some other update error happened. raise DDNSUpdateError -- 2.5.5

1 0

Need info for documentation
by R. W. Rodolico 29 Apr '16

29 Apr '16

Is there someone who can spend a bit of time with me to explain how the vlan works now? I would like to update http://wiki.ipfire.org/en/optimization/vlan/start There are several questions in the forum about problems with vlan. Sorry about using the development list for this, but I figure this is the best place to gather the info I need for the documentation. Rod -- Rod Rodolico Daily Data, Inc. POB 140465 Dallas TX 75214-0465 214.827.2170 http://www.dailydata.net

1 0

Possible configuration bug with >6 nics
by g6094199＠freenet.de 28 Apr '16

28 Apr '16

He guys! i recently installed IPFire core 100 to an Watchguard Firebox X 750e/1000e. All installed to an CF-card, booted up fine. Came to the general setup and asked to map the nics to an interface. While the x750 has 8 nics (4x Marvell 88E8001, 4x 88E8053) only 6 nics are shown in the setup menue via serial port. which seems to be a limitation by the GUI or a bug. I can see als of the interfaces on cli after i finished the initial setup lspci: 01:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 19) 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 19) 03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 19) 04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 19) 05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13) 05:01.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13) 05:02.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13) 05:03.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13) I also can use them. So it seems to be a limitation/bug of the setup menue?! Any thoughs? regards sash --- Mail & Cloud Made in Germany mit 3 GB Speicher! Jetzt kostenlos anmelden

2 1

[PATCH] Update: file to 5.26
by Sascha Kilian 28 Apr '16

28 Apr '16

Signed-off-by: Sascha Kilian <sascha(a)sakisoft.de> --- lfs/file | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lfs/file b/lfs/file index 49829d0..4d10fb4 100644 --- a/lfs/file +++ b/lfs/file @@ -24,7 +24,7 @@ include Config -VER = 5.24 +VER = 5.26 THISAPP = file-$(VER) DL_FILE = $(THISAPP).tar.gz @@ -40,7 +40,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_MD5 = ec161b5a0d2aef147fb046e5630b1408 +$(DL_FILE)_MD5 = bdd12400b90b78ce3c57e79c8d4e0e17 install : $(TARGET) -- 1.7.9.5

1 0

Replace portmap with rpcbind
by Jonatan Schlag 27 Apr '16

27 Apr '16

Hi, this patch series replaces portmap with rpcbind. Portmap is not maintained anymore and was replace by rpcbind. Rpcbind provides also the rpcinfo binary, which is quite useful for debugging. If there are other questions just asks me :-). Regards Jonatan

2 5

Core101 testing
by Daniel Weismüller 27 Apr '16

27 Apr '16

Hi I recently installed core101 from the testingtree and noticed some things. after the upgrade / before the reboot - it seems that new clamav did not accept the old databases or they were deleted and did not start. squidclamav and squid won't work anymore - freshclam start to download new databases this would take a while and if you won't wait ... see after the reboot after the reboot - clamav has no database and don't start --> squidclamav and squid don't work - freshclamav started and succesfully downloaded the databases but don't start clamav so you have to start clamav and squid manually - All rrds are empty Is there someone who may confirm these things as a bug? - Daniel

2 2

[PATCH] clamav: Create backup of signature files
by Michael Tremer 27 Apr '16

27 Apr '16

After clamav is updated, the signature files need to be re-downloaded. This is often unnecessary and delays restarting clamd, squidclamav and other dependent services. This takes a long time on slow internet connection and transfers about 110MB of data. This change will backup these files and freshclam will update or re-download them only if necessary. Reported-by: Daniel Weismüller <daniel.weismueller(a)ipfire.org> Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org> Cc: Arne Fitzenreiter <arne.fitzenreiter(a)ipfire.org> --- config/backup/includes/clamav | 2 ++ lfs/clamav | 2 +- src/paks/clamav/install.sh | 1 + src/paks/clamav/uninstall.sh | 2 ++ 4 files changed, 6 insertions(+), 1 deletion(-) create mode 100644 config/backup/includes/clamav diff --git a/config/backup/includes/clamav b/config/backup/includes/clamav new file mode 100644 index 000000000000..435d5912463c --- /dev/null +++ b/config/backup/includes/clamav @@ -0,0 +1,2 @@ +/usr/share/clamav/*.cvd +/usr/share/clamav/mirrors.dat diff --git a/lfs/clamav b/lfs/clamav index 3c778c3c326e..3794b33cdd7f 100644 --- a/lfs/clamav +++ b/lfs/clamav @@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE) DIR_APP = $(DIR_SRC)/$(THISAPP) TARGET = $(DIR_INFO)/$(THISAPP) PROG = clamav -PAK_VER = 31 +PAK_VER = 32 DEPS = "" diff --git a/src/paks/clamav/install.sh b/src/paks/clamav/install.sh index 3b7610cd42c1..02dbd5cc9858 100644 --- a/src/paks/clamav/install.sh +++ b/src/paks/clamav/install.sh @@ -23,4 +23,5 @@ # . /opt/pakfire/lib/functions.sh extract_files +restore_backup ${NAME} /usr/local/bin/clamavctrl enable & diff --git a/src/paks/clamav/uninstall.sh b/src/paks/clamav/uninstall.sh index db0999f30acf..b0d2722f55d1 100644 --- a/src/paks/clamav/uninstall.sh +++ b/src/paks/clamav/uninstall.sh @@ -23,4 +23,6 @@ # . /opt/pakfire/lib/functions.sh /usr/local/bin/clamavctrl disable +extract_backup_includes +make_backup ${NAME} remove_files -- 2.5.5

1 0

Samba Domain-Member-Login (Windows7-PC) broken?!
by Stephan Witt Privat 27 Apr '16

27 Apr '16

Hi @ all! I'm new to (this) mailinglist - so: Hello to everyone;-) I've updated the Samba-3.6.25-61-Package - and now I cannot login with my Domain-Member-Workstation (Warning is kind of: "Konnte keine Vertrauenstellung zur Domaine herstellen...") Maybe it is the same problem like reported under: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821811 or https://bugzilla.redhat.com/show_bug.cgi?id=1326918 Is there a possibility to "downgrade" the Samba-Package "temporary" until there will be working solution? BTW: I can use this "solution" as it works (described above): "...unplug the network cable (or disable WiFi) then login. It's similar to a local login (versus a network login). Once you've logged in you can re-plug in the network cable and use your resources as normal." Many thanks in advance & best regards Stephan

2 1

PSA: Rootfile updates
by Michael Tremer 27 Apr '16

27 Apr '16

Hello all, I just would like to remind you that you will have to check for rootfile changes before sending patches. I will constantly have to fix these which just costs me unnecessary time. You will have to rebuild this any way. And I urge you all one again to properly test your patches before sending them in. Just be more careful, because correcting these problems later requires way too much work which could easily be avoided. This is not a race. We care about quality. Best, -Michael

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

Development April 2016