LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-17-2014, 04:53 AM   #1
theCalcaholic
LQ Newbie
 
Registered: Jan 2014
Posts: 15

Rep: Reputation: Disabled
swaret: connection down (eth0)


Hello there,

After dozens of threads read and lots of hours without a clou I've finally come to admit that I'm stuck with this problem...
I installed swaret on my Slackware running machine - as far as I can tell successfully - and configured it, but every time I try to run "swaret --update" or "swaret --upgrade" I get the following output:

Code:
swaret 1.6.3-2

Network Connection down!
Please, take a look to 'NIC' in /etc/swaret.conf!
Which I took not only once but it still seems well configured. I am using ethernet and according to ifconfig my connection goes through eth0 as it is configured in swaret.conf.

My ifconfig output:

Code:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.30.12  netmask 255.255.255.0  broadcast 192.168.30.255
        inet6 fe80::20f:b0ff:fec7:38d0  prefixlen 64  scopeid 0x20<link>
        ether 00:0f:b0:c7:38:d0  txqueuelen 1000  (Ethernet)
        RX packets 29077  bytes 3349763 (3.1 MiB)
        RX errors 0  dropped 5  overruns 0  frame 0
        TX packets 12139  bytes 2226592 (2.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 23  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 4  bytes 320 (320.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4  bytes 320 (320.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
At least the connection seems to be alright, I'm also able to connect to the local net and internet (wether I try pinging or request webpages in a browser). As far as I interprete this output eth0 should be the right configuration, shouldn't it?

I also thought that maybe the firewall could block swaret from connecting (what I would consider as quite strange since other programs like firefox or wget had no troubles with at least partially the same protocolls and - as i guess - also the same ports). So I tried turning the firewall off for testing purposes but I got just the same result of swaret claiming my connection to be down.

Now I've no clue how to continue and also found no thread in which this problem occured with the correct NIC-configuration (as mentioned, I'm quite sure that this part is correct).

Since I'm actually a Linux-Noob I would appreciate your help and suggestions.


Regards, theCalcaholic


A few attachments:

my swaret.conf...

Code:
###########################################################
#
# swaret.conf, Version: 1.6.3
#
### /etc/swaret.conf - SWARET EXAMPLE CONFIGURATION FILE ###
#
# Define a valid Slackware Linux Version.
# (Used for Dependency Support and other Features)
#
# NOTE: If you want to use Slackware Linux Current,
#       set VERSION to 'current' (VERSION=current).
#
VERSION=12.0
#
# Define the language for status and error messages
LANGUAGE=ENGLISH
#
# ----------------------------------------------------------
# Define Slackware (8.1 or Higher or Current) Linux Mirror(Used for Official Slackware Linux Packages)
# (Slackware Linux Mirrors available at http://www.slackware.com)
#
# Syntax: ROOT=PROTOCOL:URL
#
# NOTE: swaret will use the order of the specified ROOT URL's.
#
#ROOT=file:/mnt/cdrom
#ROOT=file:/mnt/dvdrom
#ROOT=file:/mnt/usbmemstick
#ROOT=ftp://ftp.slackware.at/slackware-$VERSION
ROOT=ftp://ftp.nluug.nl/pub/os/Linux/distr/slackware/slackware-$VERSION
ROOT=http://sunsite.cnlab-switch.ch/ftp/mirror/slackware/slackware-$VERSION
ROOT=ftp://ftp.slackware.no/pub/linux/slackware/slackware-$VERSION
ROOT=http://www.slackware.no/slackware/slackware-$VERSION
ROOT=ftp://ftp.slackware.at/slackware-$VERSION
ROOT=http://www.slackware.at/data/slackware-$VERSION
ROOT=ftp://ftp.planetmirror.com/pub/slackware/slackware-$VERSION
ROOT=http://ftp.planetmirror.com/pub/slackware/slackware-$VERSION
#ROOT=rsync://rsync.slackware.no/slackware/slackware-$VERSION
#ROOT=rsync://rsync.slackware.at/slackware/slackware-$VERSION
#ROOT=file:/pub/slackware
#ROOT=file:/mnt/nfsshare/slackware
#ROOT=file:/mnt/sambashare/slackware
#
# -----------------------------------------------------------
# Define Repository URL's with Slackware Linux Packages.
# (Used for Repository Slackware Linux Packages)
# (Repository URL's available at http://swaret.sourceforge.net and
#   at http://www.linuxpackages.net/mirrors.php)
#
# NOTE 1: To use a Local Repository or Remote Repository,
#         be sure it contains the following Files:
#         - CHECKSUMS.md5 (For MD5 Sum, REQUIRED)
#         - FILELIST.TXT (For Package Name + Size, REQUIRED)
#         - PACKAGES.TXT (For Package Description, NOT REQUIRED)
#         - MANIFEST.bz2 (For Dependency Support, NOT REQUIRED)
# NOTE 2: To create your own Repository, use 'swaret-tools'.
#         You can get 'swaret-tools' at http://swaret.sourceforge.net!
#
# Syntax: REPOS_ROOT=REPOSITORYNAME%PROTOCOL:URL
#
# NOTE 1: The REPOSITORY NAME can only be ONE Keyword!
# NOTE 2: swaret will use the order of the specified REPOS_ROOT URL's.
# 
#REPOS_ROOT=LinuxPackagesDOTNET%http://www2.linuxpackages.net/packages/Slackware-10.0
#
#REPOS_ROOT=My_Slackware_Packages_On_CD-ROM%file:/mnt/cdrom
#REPOS_ROOT=My_Slackware_Packages_On_DVD-ROM%file:/mnt/dvdrom
#REPOS_ROOT=My_Slackware_Packages_On_USB_Memory_Stick%file:/mnt/usbmemstick
#REPOS_ROOT=SomeRemoteRepository%ftp://ftp.someremoterepository.net/slackware/slackware-10.0
#REPOS_ROOT=SomeRemoteRepository%http://www.someremoterepository.net/slackware/slackware-10.0
#REPOS_ROOT=SomeRemoteRepository%rsync://rsync.someremoterepository.net/slackware/slackware-10.0
#
# ------------------------------------------------------------
# Define Libraries (8.1 or Higher or Current) List Mirrors.
# (Used for Dependency Support)
#
# NOTE 1: You need to specify a Libraries List Mirror which
#         contains a 'libraries-VERSION' File.
#
# NOTE 2: To create the Libraries List, use 'swaret-tools'.
#         You can get 'swaret-tools' at http://swaret.sourceforge.net!
#         You can also clear all DEP_ROOT Variable(s) which will
#         allow swaret to create the Libraries List for you
#         during Dependency Check using the defined ROOT Variable(s) above.
#
# Syntax: DEP_ROOT=PROTOCOL:URL
#
# NOTE: swaret will use the order of the specified DEP_ROOT URL's.
#
DEP_ROOT=http://swaret.sourceforge.net
DEP_ROOT=http://swaret.sourceforge.net/libraries-$VERSION
#DEP_ROOT=file:/mnt/cdrom
#DEP_ROOT=file:/mnt/dvdrom
#DEP_ROOT=file:/mnt/usbmemstick
#DEP_ROOT=file:/pub/swaret
#DEP_ROOT=file:/mnt/nfsshare/swaret
#DEP_ROOT=file:/mnt/sambashare/swaret
#
# ----------------------------------------------------------
# General Settings
#
# Do you want swaret to use Random Slackware Linux Mirrors?
# -> 1 for yes, 0 for no.
#
RANDOMR=0
#
# Do you want swaret to back-up your packages when upgradeing? 
# -> If set to 1, old packages are backed up in $CACH_DIR/rollback.
#    Normally this is /var/swaret/rollback.  ROLLBACKMAX is the number
#    of "upgrades" that will be backed up before old backups will be
#    removed.  Turning on rollback means upgrading packages takes 
#    longer, but it is more safe.
# -> If set to 0, swaret will not back up packages.  
#
ROLLBACK=0
ROLLBACKMAX=3
#
# Do you want swaret to parse all the Package Descriptions?
# -> If set to 1, swaret will also match Packages whose Description
#    is matching the Keyword(s) you specify after --ACTION.
#    NOTE: swaret will parse all the Package Descriptions for this,
#          and might slow down swaret when using an older System.
# -> If set to 0, swaret will not use Package Descriptions 
#    to match one or more Packages.
#
USEPKGDESC=1
#
# If you don't want swaret to Upgrade, Install, Re-Install, Download,... 
# some Packages, add the KEYWORDS to the EXCLUDE Variable.
# To disable Exclude Method: swaret --exclude -off
# To enable Exclude Method: swaret --exclude -on
#
# NOTE: You can add ANY EXTENDED REGEXP (Regular Expression) to the EXCLUDE Variable(s)
#
# Basic Exclude
EXCLUDE=kernel alsa lilo
#EXCLUDE=swaret
EXCLUDE=aaa_
EXCLUDE=MANIFEST.bz2$
EXCLUDE=.*dl$ .*PACKAGER$ .*MYBUILD$
EXCLUDE=alsa
#
# Advanced Exclude
# Syntax: KEYWORD[DONT_EXCLUDE_ME_KEYWORD1,DONT_EXCLUDE_ME_KEYWORD2,...]
# Example: kde-i18n[nl,en_GB] koffice-i18n[nl,en_GB]
#
#EXCLUDE=kde-i18n[nl,en_GB] koffice-i18n[nl,en_GB]
#
# Do you want to enable Dependency Check?
# -> If set to 1, swaret will start the Dependency Check after 
#    every Upgrade, Install and Re-Install Procedure.
# -> If set to 0, swaret will not start the Dependency Check 
#    after any Procedure.
#
DEPENDENCY=1
#
# Do you want swaret to Search for missing Libraries (and Fix) 
# which could be found on your System, but not tracked by ldconfig?
# -> 1 for yes, 0 for no.
#
DSEARCHLIB=1
#
# Set to 1, if you want swaret to use the 'slocate' program
# to Search for missing Libraries.
# (be sure to issue the 'updatedb' Command regularly!)
# If DSEARCHM is set to 0, swaret will use 
# the 'find' program to locate missing Libraries.
# -> 1 for yes, 0 for no.
#
DSEARCHM=1
#
# Start MD5 Check after Fetching Packages, Patches and Sources?
# -> 1 for yes, 0 for no.
#
MD5CHECK=1
#
# Start GPG Signature Check after Fetching Packages, Patches and Sources?
#
# NOTE: Check out F.A.Q. (--faq gpg) how to Import a Public GPG Key which
#       will be used by the GPG Signature Check.
#
# -> 1 for yes, 0 for no.
#
GPGCHECK=0
#
# Show Description for Packages during
# Upgrade, Install, Re-Install,... Procedures?
# -> If set to 0, you will not see a Description.
# -> If set to 1, you will see a Description.
#
DESC=1
#
# Cache Directory for (Repository) Packages and Sources.
#
CACHE_DIR=/var/swaret
#
# Enable Logging?
# -> 1 for yes, 0 for no.
#
LOG=1
#
# swaret Log File
#
LOG_FILE=/var/log/swaret
#
# Show Warnings?
# -> 1 for yes, 0 for no.
#
WARNINGS=1
#
# Show Information?
# -> 1 for yes, 0 for no.
#
INFORMATION=1
#
# -------------------------------------------------------------
# Network Settings
#
# Network Interface
# Use this if you have a Network Interface.
#
NIC=eth0
#
# Local Interface
# Use this if you do not have a Network Interface.
#
# For Example (CD-ROM):
# You got a Slackware Linux CD-ROM,
# mount the CD-ROM to /mnt/cdrom and
# set ROOT to 'file:/mnt/cdrom' in /etc/swaret.conf.
# Also, set NIC to 'lo' (Local Loop Device).
#
# NIC=lo
#
# Progress
# If set to 0, swaret will use the '%' Download Interface.
# If set to 1, swaret will use the 'size' Download Interface.
# If set to 2, swaret will use the 'wget/rsync' Download Interface.
#
PROGRESS=0
#
# Timeout for wget and/or rsync.
# -> Number of seconds for Timeout
#
TIMEOUT=35
#
# Retries for wget and/or rsync.
# -> Number of Retries
#
RETRIES=5
#
# Behind a Firewall? Using FTP Mirrors?
# -> 1 for yes, 0 for no
#
PASSIVE_FTP=1
#
# If you want HTTP or FTP Proxy Support,
# uncomment and Setup the following Variable:
#
# WGET_PROXY=http://IP or HOST:PORT
#
# If you want RSYNC Proxy Support,
# uncomment and Setup the following Variable:
#
# RSYNC_PROXY=IP or HOST:PORT
#
### /etc/swaret.conf - SWARET EXAMPLE CONFIGURATION FILE ###

my hosts.deny (it's quite simple):
Code:
#
# hosts.deny	This file describes the names of the hosts which are
#		*not* allowed to use the local INET services, as decided
#		by the '/usr/sbin/tcpd' server.
#
# Version:	@(#)/etc/hosts.deny	1.00	05/28/93
#
# Author:	Fred N. van Kempen, <waltje@uwalt.nl.mugnet.org
#
#

ALL:ALL

# End of hosts.deny.
my hosts.allow...

Code:
#
# hosts.allow	This file describes the names of the hosts which are
#		allowed to use the local INET services, as decided by
#		the '/usr/sbin/tcpd' server.
#
# Version:	@(#)/etc/hosts.allow	1.00	05/28/93
#
# Author:	Fred N. van Kempen, <waltje@uwalt.nl.mugnet.org
#
#

ALL: 127.0.0.1
sshd: ALL: ALLOW


# End of hosts.allow.
and my rc.firewall.

Code:
# iptables -P INPUT DROP
# iptables -P FORWARD DROP

# iptables -A INPUT -m state ESTABLISHED,RELATED -j ACCEPT
# iptables -A INPUT -s 127.0.0.0/8 -d 127.0.0.0/8 -i lo -j ACCEPT


# iptables -A INPUT -p tcp --dport 80 -i ppp0 -j ACCEPT
# iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE

# iptables -A INPUT -p ssh --dport 22 -i ppp0 -j ACCEPT




# !/bin/bash

# rc.firewall for
# Basic Slackware Security

# These two rules set the default policies, i.e. what to do if a
# packet doesn't match any other rule, to drop any packet coming
# into (INPUT) or routing through (FORWARD) the box.
  iptables -P INPUT DROP
  iptables -P FORWARD DROP

# These rules are added (-A) to the INPUT chain.  They allow packets
# from any previously established connections and accept anything
# from the loopback interface.
  iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
  iptables -A INPUT -s 127.0.0.1 -d 127.0.0.1 -i lo -j ACCEPT

# This rule added to the INPUT chain accepts any ssh connections.
  iptables -A INPUT -p tcp --dport 22 -i eth0 -j ACCEPT

# This rule is added to the INPUT chain to allow access to the webserver (port 80)
  iptables -A INPUT -p tcp --dport 80 -i ppp0 -j ACCEPT
 
Old 01-17-2014, 08:42 AM   #2
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,175

Rep: Reputation: Disabled
I'm afraid swaret belongs to the abandonware category, as last release date back 2006-10-27 according to sourceforge.net

Maybe try to get support from this page.
 
Old 01-17-2014, 09:00 AM   #3
theCalcaholic
LQ Newbie
 
Registered: Jan 2014
Posts: 15

Original Poster
Rep: Reputation: Disabled
swaret: connection down (eth0)

Thank you for you reply.

Is there an alternative to using swaret? If it is like you say I would prefer using something different.

Last edited by theCalcaholic; 01-17-2014 at 09:02 AM.
 
Old 01-17-2014, 09:03 AM   #4
KeithE
Member
 
Registered: Jan 2003
Location: Mesa, AZ
Distribution: Linux Mint
Posts: 155

Rep: Reputation: 35
Quote:
Originally Posted by theCalcaholic View Post
Well is there an alternative to Swaret?
Try slapt-get. I've used it for years and have never had an issue. Current version is 0.10.2p but don't let the 0.x spook you. It's rock stable.

http://software.jaos.org
 
1 members found this post helpful.
Old 01-17-2014, 09:07 AM   #5
theCalcaholic
LQ Newbie
 
Registered: Jan 2014
Posts: 15

Original Poster
Rep: Reputation: Disabled
swaret: connection down (eth0)

Thank you! I'll give it a try.
 
Old 01-17-2014, 06:04 PM   #6
theCalcaholic
LQ Newbie
 
Registered: Jan 2014
Posts: 15

Original Poster
Rep: Reputation: Disabled
EDIT: made up a new thread for this.

Last edited by theCalcaholic; 01-19-2014 at 03:45 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Network eth0 activated upon boot in ifcfg-eth0; but no network connection after login TomRaaijmakers Linux - Networking 1 06-17-2010 08:29 AM
eth0 going down (connection reset by peer, then connection refused) Astarath Slackware 1 09-05-2007 05:14 AM
Deleting Swaret files in /var/swaret?? Garibaldi3489 Slackware 2 12-30-2004 04:10 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:54 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration