HP ProCurve Switches UDP and other issues

A short note about dealing with UDP issues on daisy-chained managed ProCurve switches.

I noticed a funny problem on a AWMN node that uses two daisy-chained managed HP ProCurve switches. The routers on one of the switches were not able to get NTP updates from the time-servers connected to the other switch.

The routers having the issues were running RouterOS with their ntp clients set to unicast. The same RouterOS routers could get ntp updates just fine from interfaces not attached to the switch.

OpenWrt routers on the same switch did not have any problems talking-to and synchronizing-with time-servers attached to the other switch.



What Solved it?

On the switch
Security -> Advanced Security -> Disable Auto DoS & Disable Storm Control



hp pro curve madness

Tor Node Setup Notes debian

Notes Taken while setting up a Tor Relay Node.

The Debian System

# cat /etc/issue /etc/debian_version;lsb_release -c
Debian GNU/Linux 7 \n \l

7.1
Codename: wheezy

Add the TorProject repository to the apt sources.

# echo "deb http://deb.torproject.org/torproject.org wheezy main" >> /etc/apt/sources.list

Add the torproject gpg key

# gpg --keyserver keys.gnupg.net --recv 886DDD89
# gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | apt-key add -

TorProject debian based Install

Update apt

# apt-get update

Optionally

# apt-get install deb.torproject.org-keyring

You may need to comment out the main repository, apt-get update again, and then Install Tor with apt-get

# apt-get install tor

The configuration: /etc/tor/torrc.

I did set a few more directives in torrc
but I think that at least the following should be set

SocksPort
SocksPolicy
ORPort
Address
OutboundBindAddress
Nickname
ContactInfo

TorProject torrc

To minimize the abuse complaints you may want to use a reduced exit policy eg:

ExitPolicy accept *:80                   #g0
ExitPolicy accept *:110                  #g0
ExitPolicy accept *:143                  #g0
ExitPolicy accept *:443                  #g0
ExitPolicy accept *:993                  #g0
ExitPolicy accept *:5222-5223            #g0
ExitPolicy accept *:8080                 #g0
ExitPolicy accept *:11371                #g0
ExitPolicy reject *:*                    #g0

Or use The Reduced Exit Policy recommended by the Tor Project
TorProject ReducedExitPolicy

You may want to set the BandwidthRate and RelayBandwidthBurst.

URI: http://alog.ipduh.com/2013/08/tor-node-setup-notes-debian.html

which installed debian packages depend on a debian package

Which installed debian packages depend on a debian package?

It must be a lazier way doing this.

I was not able to find that lazier way while searching the interwebz for over five minutes and it took me 10 minutes to write the following script and this post.

whatdependsonfrominstalled.sh

#!/bin/bash
#g0 2013 http://alog.ipduh.com/2013/08/which-installed-debian-packages-depend.html
## whatdependsonfrominstalled.sh: find out which installed debian packages depend on the passed debian package
## whatdependsonfrominstalled.sh: usage:: whatdependsonfrominstalled.sh debian-package-name :::eg::: whatdependsonfrominstalled.sh libc6

ME="whatdependsonfrominstalled.sh"
MEAT="/usr/bin/${ME}"

if [ -z $1 ]; then
 egrep '^##' ${MEAT}
 exit 3
fi

for i in `dpkg -l |egrep "^ii" |cut -f3 -d' '`;do 
 
 apt-cache depends ${i} |grep Depends: |grep ${1} > /dev/null
 if [ $? -eq 0 ]; then
 echo "--"
 echo ${i};
 apt-cache depends ${i}|grep ${1}
 echo "--"
 fi
done

 
     

To get and install whatdependsonfrominstalled.sh

# wget kod.ipduh.com/lib/whatdependsonfrominstalled.sh
# chmod 755 whatdependsonfrominstalled.sh
# mv whatdependsonfrominstalled.sh /usr/bin

Usage example

$ whatdependsonfrominstalled.sh rpcbind
--
nfs-common
  Depends: rpcbind
--

URI: http://alog.ipduh.com/2013/08/which-installed-debian-packages-depend.html