Archive for the ‘Net’ Category

[Errno 14] curl#56 – “Network error recv()” – impostare proxy yum Fedora Core

Sunday, August 7th, 2011

Se dopo aver lanciato yum update:

[usertest@fedoratest ~]$ sudo yum update
[sudo] password for usertest:

Compare:

Loaded plugins: langpacks, presto, refresh-packagekit
fedora/metalink | 33 kB 00:00
http://fedora.mirror.garr.it/mirrors/fedora/linux/releases/15/Everything/i386/os/repodata/repomd.xml: [Errno 14] curl#56 - "Network error recv()"
Trying other mirror.
ftp://ftp.ciril.fr/pub/linux/fedora/linux/releases/15/Everything/i386/os/repodata/repomd.xml: [Errno 14] curl#7 - "Couldn't connect"
Trying other mirror.
http://mirror.nl.leaseweb.net/fedora/linux/releases/15/Everything/i386/os/repodata/repomd.xml: [Errno 14] curl#56 - "Network error recv()"
Trying other mirror.
[...]

Potrebbe essere necessario impostare il vostro proxy nel file yum.conf. Quindi andiamo ad editare tale file:

[usertest@fedoratest ~]$ sudo gedit /etc/yum.conf

e aggiungiamo le seguenti righe al suo interno, dopo il tag [main]:

proxy=http://proxy.mioDominio.it:portaDelProxy
proxy_username=nomeUtente
proxy_password=miaPassword

Es:
[main]
proxy=http://proxy.gabriele.it:8080
proxy_username=gabriele
proxy_password=My_V3rY_Str0Ng_P4$$wW0rD!
cachedir=/var/cache/yum/$basearch/$releasever
keepcache=0
debuglevel=2
...

N.B. 1: ricordatevi che il file yum.conf è aperto in lettura a tutti gli utenti… la password è scritta in chiaro…

N.B. 2: a quanto parte Fedora Core 15 ha un bug per l’impostazione del proxy. Leggi qui.

 

SIOCSIFNETMASK No such device

Thursday, January 20th, 2011

Mentre avviavo una Debian, ho visto dei messaggi che mi hanno insospettito:

SIOCSIFNETMASK: No such device
SIOCSGIFADDR: No such device
eth0: ERROR while getting interface flags: no such device
eth1: ERROR while getting interface flags: no such device

Facendo:

$ ifconfig

veniva visualizzata solo l’interfaccia loopback, mentre con:

$ ifconfig -a

non c’erano più la eth0 e la eth1, ma la eth2 e eth3 (Figura 1):

ifconfig -a

Figura 1: ifconfig -a

Andando a vedere il log: /var/log/messages ho notato:

kernel: [..] udev: renamed network interface eth0 to eth2
kernel: [..] udev: renamed network interface eth1 to eth3

Successivamente ho controllato il file:

/etc/udev/rules.d/70-persistent-net.rules

e ho visto le seguenti righe:

# PCI device 0x8086:0x1076 (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="*:*:*:*:*:*c",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x8086:0x1076 (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="*:*:*:*:*:*d",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
# PCI device 0x8086:0x1076 (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="*:*:*:*:*:*6",
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
# PCI device 0x8086:0x1076 (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="*:*:*:*:*:*7",
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

A questo punto sono andato a controllare (sempre da ifconfig -a, vedi Figura 1) i MAC delle schede, ho commentato le prime due righe (con MAC diverso) e ho modificato le ultime due mettendo “eth0″ e “eth1″ al posto di “eth2″ e “eth3″ (Figura 2):

# PCI device 0x8086:0x1076 (e1000)
#SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="*:*:*:*:*:*c",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x8086:0x1076 (e1000)
#SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="*:*:*:*:*:*d",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
# PCI device 0x8086:0x1076 (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="*:*:*:*:*:*6",
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x8086:0x1076 (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="*:*:*:*:*:*7",
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

70-persistent-net.rules

Figura 2: 70-persistent-net.rules

Dopo aver fatto ciò, ho riavviato ed è tornato tutto come prima.

SIOCSIFNETMASK: No such device
SIOCSGIFADDR: No such device

Firewall Linux e BSD

Wednesday, October 13th, 2010

Distribuzioni dedicate per firewall (Linux e BSD based):

  • Neobewall (basato sul progetto M0n0wall)
  • ipcop distribuzione firewall Linux
  • Zeroshell “[...] Zeroshell is a small Linux distribution for servers and embedded devices aimed at providing the main network services a LAN requires[...]“
  • pfSense “[...] pfSense is a free, open source customized distribution of FreeBSD tailored for use as a firewall and router[...]“
  • SmoothWall “[...]a free firewall that includes its own security-hardened GNU/Linux operating system and an easy-to-use web interface[...]“
  • Devil-Linux “Devil-Linux is a distribution which boots and runs completely from CDROM [...]“
  • ClarkConnect “ClarkConnect is a powerful server/gateway software solution designed for the small/medium-sized organization. [...]“
  • redWall “redWall is a bootable CD-ROM Firewall. [...]“

Altre soluzioni (commerciali):

File hosting websites

Saturday, October 24th, 2009

Siti che offrono servizi di file hosting:

Aggiunte e/o correzioni sono bene accette.

Digital Forensics tools

Saturday, November 1st, 2008
  • Autopsy “[...] The Autopsy Forensic Browser is a graphical interface to the command line digital investigation tools in The Sleuth Kit [...]“
  • Sleuthkit “[...] is a library and collection of command line tools that allow you to investigate volume and file system data”
  • Foremost (for data carving)
  • sha256deep command (to compute file hash)
  • grep command (to search keywords)
  • awk command (to analyse the output)
  • sed command (to analyse the output)
  • dd command

Other Data Carving Tools