Posts Tagged ‘openwrt’

Upgrade del nodo Conbipel con Rocket M5

Sunday, December 29th, 2013

Oggi io e Pierluigi abbiamo finalmente concluso l’upgrade del nodo Conbipel che era iniziato qualche settimana fa. La nuova rocket ha funzionato subito come da programma, confermando la nostra ipotesi che l’hardware precedente doveva essere difettoso. Nella configurazione attuale ci sono tre apparati tutti con sistema operativo OpenWrt Scooreggione. La rocket con antenna sector raccoglie tre client, una nanostation è dedicata alla zona marconi (nodo Cruto), ed una seconda Nanostation punta i nodi in zona Tor Vergata.

Prossimamente la NanoStation smontata dal palo di Conbipel verrà installata a Gallia per provare un link diretto tra Gallia e Conbipel, andando ad agganciarsi proprio a questa rocket installata oggi.

stay tuned ! ZioPRoTo

Cubieboard as NetFlow collector with nfsen

Friday, June 28th, 2013

One month ago I bought a cubieboard to have a small, powerfull, unexpensive, low noise, low power consumption linux server at home, for my nerd projects.

The first project I started ? Run a NetFlow collector at home for my Ninux nodes.

The Cubieboard

The cubieboard is a small ARM pc. With 1Ghz processor and 1Gb of RAM is very flexible for any application. I bought it from miniand.com with the developer kit and I also got from Amazon a USB power adapter and a SD memory card. A few weeks after the new Cubieboard A20 came out ! So I suggest you get the new one even if it cost some dollars more, because it has a dual core CPU.

(more…)

IPV6 + OpenWRT + UCI + ADSL Telecom HowTo

Friday, November 2nd, 2012

In questi giorni di festa mi sono cimentato ad un upgrade dell’harware di rete a casa dei miei genitori. Avendo messo un router con Openwrt ho provato ad usare il collegamento IPV6 nativo della rete Telecom e la cosa bella è che ha funzionato!

Screenshoot Luci interface

Visto che in rete si trova una guida per router Fritz!box e router Cisco ho deciso di scrivere queste due righe per fare la medesima configurazione con OpenWrt.

La configurazione hardware è costituita da router tplink TL-WR1043ND con openwrt (Attitude Adjustment 12.09-beta) a cui è collegato un modem adsl sulla porta wan. Considerando che i modem puri vanno scomparendo è anche possibile usare un router adsl economico con firmware originale e usarlo come modem impostandolo in modalità “bridge” . Il collegamento verso il provider avviene tramite pppoe, ecco la sezione relativa del file /etc/config/network

config interface ‘wan’
option _orig_ifname ‘eth0.2′
option _orig_bridge ‘false’
option proto ‘pppoe’
option ifname ‘eth0.2′
option username ‘adsl@alice6.it’
option password ‘IPV6@alice6′
option ipv6 ’1′
option mtu ’1492′
option metric ’100

 

La configurazione software si basa sull’utilizzo di wide-dhcpv6-client e radvd. Come funziona: il client dhcp6c riceve la delega per un /64 , imposta le interfacce locali del router e scrive il prefisso ottenuto nel file /var/etc/radvd.conf in modo tale che radvd possa mandare i RA sulla rete locale.

Una volta istallati i package (opkg install wide-dhcpv6-client radvd) si configurano. Ecco i miei file.

/etc/config/config/dhcp6c

‘dhcp6c’ ‘basic’
option ‘enabled’ ’1′                            # 1 = enabled; 0 = disabled
option ‘interface’ ‘wan’                        # This is the interface the DHCPv6 client will run on
option ‘dns’ ‘dnsmasq’                          # Which DNS server you run (only dnsmasq currently supported)
option ‘debug’ ’1′                              # 1 = enable debugging; 0 = disable debugging

# Send options (1 = send; 0 = do not send)
option ‘pd’ ’1′                                 # Prefix Delegation
option ‘na’ ’1′                                 # Non-Temporary Address
option ‘rapid_commit’ ’1′                       # Rapid Commit

# Request options (1 = request; 0 = do not request)
option ‘domain_name_servers’ ’1′
option ‘domain_name’ ’0′
option ‘ntp_servers’ ’0′
option ‘sip_server_address’ ’0′
option ‘sip_server_domain_name’ ’0′
option ‘nis_server_address’ ’0′
option ‘nis_domain_name’ ’0′
option ‘nisp_server_address’ ’0′
option ‘nisp_domain_name’ ’0′
option ‘bcmcs_server_address’ ’0′
option ‘bcmcs_server_domain_name’ ’0′

# Override the used DUID, by default it is derived from the interface MAC
# The given value must be uppercase and globally unique!
#option ‘duid’ ’00:03:00:06:D8:5D:4C:A5:03:F2′

# Script to run when a reply is received
option ‘script’ ‘/usr/bin/dhcp6c-state’

# Define one or more interfaces on which prefixes should be assigned
config ‘interface’ ‘loopback’
option ‘enabled’ ’0′                            # 1 = enabled; 0 = disabled
option ‘sla_id’ ’0′                             # Site level aggregator identifier specified in decimal (subnet)
option ‘sla_len’ ’0′                            # Site level aggregator length (64 – size of prefix being delegated)

config ‘interface’ ‘lan’
option ‘enabled’ ’1′
option ‘sla_id’ ’1′
option ‘sla_len’ ’0′

Come potete vedere l’unica interfaccia che ottiene l’IPV6 è la lan. In realtà ho provato ad fare in modo che anche la porta WAN abbia un IPV6 ma essendo l’interfaccia nello stato “UNKNOW” invece che “UP” dhcpv6c non gli fornisce un ipv6 global, comunque il routing è garantito da indirizzi link (classe fe80::) tra il router e il provider.

L’altro file da configurare è /etc/config/radvd

config interface
option interface        ‘lan’
option AdvSendAdvert    1
option MinRtrAdvInterval 3
option MaxRtrAdvInterval 10
option AdvLinkMTU 1280
option AdvManagedFlag   0
option AdvOtherConfigFlag 0
list client             ”
option ignore           0

config prefix
option interface        ‘lan’
# If not specified, a non-link-local prefix of the interface is used
list prefix             ”
option AdvOnLink        1
option AdvAutonomous    1
option AdvRouterAddr    1
option ignore           0

config route
option interface        ‘lan’
list prefix             ”
option ignore           0

Una volta avviato il tutto vi dovreste trovare il file generato /var/etc/radvd.conf che assomiglia a questo:

interface br-lan
{
MaxRtrAdvInterval 10;
MinRtrAdvInterval 3;
AdvLinkMTU 1280;
AdvSendAdvert on;
AdvManagedFlag off;
AdvOtherConfigFlag off;

prefix 2a01:2003:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
};

That’s all folk

FaByS

Improve OpenWrt monitoring and managing Completed!

Monday, August 20th, 2012

The GSoC work to improve eigenNet ( the OpenWrt based firmware ) is finally finished!

All the planned features and more are now implemented and the code is ready to rock on ours roof, moreover the eigenNet firmware community is very enthusiast on the work done so the code is going to be completely marged ( the most part is already in :D ) on the official git branch!

What was implemented:

  • Selectable custom community CRDA
  • Pointing GUI
  • Bandwidth test server and GUI
  • Conditional  IPv4 gateway announcing
  • ATH5K driver support
  • 5GHz device support
  • Export info via http (future integration into NodeShot)
  • Ebtables based firewall

Future plan:

  • OpenWrt trunk madwifi support is rapidly changing we have to take that in account for the future
  • Batman-adv is evolving so rapidly too adding new features and changing some paradigms so we should take advantage of that in the future
  • Light and secure web management ( NodeShot is not ready yet to do that so we should wait )

Checkout the code  and give us feedback for the final merge :D !

Improve remote monitoring and managing of OpenWrt

Monday, June 4th, 2012

After the good news of being accepted for the Google Summer of Code 2012, I have started to work hard on my project; first of all I have learned a lot of things about git, the version control system used by the community around eigenNet firmware to collaborate on the development of the OpenWRT based firmware suitable for community mesh networks, then I have created my own clone of the master repository, I started editing the code and then requested to merge into master when a set of feature was complete and tested enough.

What is done:

  • Selectable custom community CRDA
  • Pointing GUI
  • Bandwidth test server and GUI
  • Conditional  IPv4 gateway announcing
  • ATH5K driver support
  • 5GHz device support

What is not done yet:

  • Node Shot integration schema/classes
  • Community broad testing
  • Final adjustment

More news and updates soon!


Switch to our mobile site