[Thread ufficiale] amod - firmware modificato per DGND4000, DGN3500, DGN2200V3/V4

[alfonsor]

quelli sono i firmware adsl

sono quelli che contengono le funzioni per fare la connessione ATM

cosa cambia usando uno o l'altro lo puoi sperimentare solo tu

ricorda che sul 2200V3 e sul 2200V4 ci vuole un reboot dopo aver salvato perché il firmware adsl scelto venga usato

PS alcune note sui firmware adsl

ci sono dei casi in cui un firmware di una versione permette di connettersi con il modem remoto in centrale (in centrale c'è un modem a cui ti connetti, piastra, DSLAM, ATUC di una marca specifica e con un firmware specifico) mentre con altri firmware è difficoltoso connettersi; questa è la ragione principale per cui in amod c'è la scelta del firmware adsl

di solito il firmware che funziona meglio, salvo problemi di cui al punto sopra, è quello fornito originariamente nel router stesso, che è sempre quello di default; questo per la banalissima ragione che il firmware viene richiamato da un programma che fa la connessione che funziona su driver del kernel linux e tutto l'insieme è stato scelto per andare d'accordo; ovviamente in amod non sono presenti firmware adsl che "non funzionano", ma vengono testati

le differenze non sono facili da notare e sicuramente richiedono tempo; non è che scegli un firmware, fai un reboot e prendi 1 MB in più in download ed è merito del firmware; è stato sicuramente un caso; non è che il ping diminuisce di 5 ms ed è merito del firmware; è stato un caso con certezza assoluta; il firmware adsl invece ti fa avere a parità di SNR delta meno errori nel tempo; ma ci vuole tempo

sono le classiche cose che sono in firmware mod, per giocare

[Dangze]

Hi Alfonso,

It's me again...

Today, I'm trying the DDNS functionnalities, and I must recognize that for the moment nothing is working for me !

1) Concerning my no-ip account, I input my hostname, user and password in the appropriate fields on the Dynamic DNS amod page, I check the "Active" box, I restart the device, and...nothing happens (the no-ip IP is not updated). Even if I click the Update button, nothing, niente !...
The status is always "Offline", is it normal ?
Is there a place where I can find a log of these actions ?
Where is my mistake ?

2) Concerning my dtdns account (thank you for making it available for me...), I create and telnet the ddns.user macro, also modified with the appropriate hostname and password, but also the dtdns IP is not updated !
I could not understand how and when it is supposed to work !
First, I don't find the tmp/ddns_user_cache file, is it normal ?
If I write (in telnet) the command ddns.user, I get the message :
-ash: ddns.user : not found
why ???

So, I'm very confused to ask you again to help me...

Many thanks in advance !

[alfonsor]

Offline means you are "offline"

Is the 2200V4 "online"?

online means the 2200v4 is configured as a modem/router, plugged to the telephone line and connected, or with eth4 configured as WAN, plugged and connected in some way

can the hosts wired or wireless connected to the 2200v4 go online?

I just did an update with no ip and it worked

ddns.user can't be found for how linux path work

the command to write in telnet is

ddns -d

[Dangze]

Well,

I made several tests, with my modem connected to the phone line (ADSL mode), and with my modem connected in WAN mode (through LAN port 4) to my ISP modem LAN. In both cases, I can access the Internet, surf the web and send/receive emails !
But in no case the status changes from Offline to Online ! I think this is the cause of my DDNS not updating...

When entering the ddns -d command in Telnet, I get
kill all
wait all
get wan ip try : 1
.....
get wan ip try : 16
can't obtain WAN IP
kill all
wait all
done (1)

Any idea why the status remains offline ? A box to check somewhere ?...

[alfonsor]

please, go in telnet and write

amodfunc wan
ifconfig

and post the result here

[Dangze]

Here you are...

amodfunc wan
ppp0
ifconfig
bcmsw Link encap:Ethernet HWaddr 20:0C:C8:19:7F:C6
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Base address:0xda00

br0 Link encap:Ethernet HWaddr 20:0C:C8:19:7F:C6
inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::220c:c8ff:fe19:7fc6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9320 errors:0 dropped:0 overruns:0 frame:0
TX packets:5703 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2077992 (1.9 MiB) TX bytes:2310448 (2.2 MiB)

eth0 Link encap:Ethernet HWaddr 20:0C:C8:19:7F:C6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth1 Link encap:Ethernet HWaddr 20:0C:C8:19:7F:C6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


eth2 Link encap:Ethernet HWaddr 20:0C:C8:19:7F:C6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


eth3 Link encap:Ethernet HWaddr 20:0C:C8:19:7F:C7
inet addr:192.168.0.27 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::220c:c8ff:fe19:7fc7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5588 errors:0 dropped:0 overruns:0 frame:0
TX packets:5270 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1915840 (1.8 MiB) TX bytes:1258512 (1.2 MiB)


lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:643 errors:0 dropped:0 overruns:0 frame:0
TX packets:643 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:180944 (176.7 KiB) TX bytes:180944 (176.7 KiB)

wl0 Link encap:Ethernet HWaddr 20:0C:C8:19:7F:C6
inet6 addr: fe80::220c:c8ff:fe19:7fc6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9027 errors:0 dropped:0 overruns:0 frame:0
TX packets:8989 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2149494 (2.0 MiB) TX bytes:3258251 (3.1 MiB)
Interrupt:31

[alfonsor]

on the netgear configuration pages, int Setup / Internet setup, how did you setup the internet connection?

it seems you are using the 2200v4 not as a primary router, but with wan set as dhcp, is it a secundary router?

if so, ddns would not work; wan must be up and with a public ip assigned

In my humble opinion, but I write amod so :P, a ddns client must be run only from a router with a public ip address interface

in the 2200v3 I set up a mechanism that makes ddns work even if the router is used as an access point, but I don't like that

[Dangze]

OK, I will chech that, but DDNS was also not working (Status Offline !) when I was directly connected to the phone line, with the device working as ADSL modem and receiving public IP !...

Later on the evening, I will try again to directly connect as ADSL modem, Telnet the same commands and post the results...

[alfonsor]

when you are connected at the telephone, wich protocol do you use?

pppoe
pppoa
ipoa
static ip address?

only the first two are actually working with ddns in amod, for the simple reason I can't test the latter

[random566]

Originariamente inviato da alfonsor

in the 2200v3 I set up a mechanism that makes ddns work even if the router is used as an access point, but I don't like that

perchè non ti piace?
a volte potrebbe essere utile avere un client ddns su un router che non è quello che realizza la connessione wan, oppure su un access point.
ad esempio, con quelle connessioni in cui si è obbligati a utilizzare il router del provider e questo non ha i client ddns che servono

[alfonsor]

Originariamente inviato da random566

perchè non ti piace?
a volte potrebbe essere utile avere un client ddns su un router che non è quello che realizza la connessione wan, oppure su un access point.
ad esempio, con quelle connessioni in cui si è obbligati a utilizzare il router del provider e questo non ha i client ddns che servono

puoi sempre fare lo update; in amod puoi lanciare all'avvio una piccola macro che fa così

per_sempre_fai {
  ip=curl -s ip.changeip.com
  ip è diverso da ultimo ip memorizzato ? {
    salva ip
    fa lo update ddns
  }
  attendi 10 minuti
}

questo funziona benissimo; ma a me non piace; nel peggiore dei casi hai un ritardo di 10 minuti più il tempo che ci mette il dns del provider di ddns a modificare la entry; non è una cosa seria

sul 2200 in modalità access point, ddns fa più o meno così; ogni tanto usa curl per prendersi lo ip ed ogni tanto fa il test degli update; mahhhhh non credo sia una cosa buona e giusta; se l'utente vuole proprio in un coso con amod, lo può fare lui a mano

[Dangze]

Originariamente inviato da alfonsor

when you are connected at the telephone, wich protocol do you use?

pppoe
pppoa
ipoa
static ip address?

only the first two are actually working with ddns in amod, for the simple reason I can't test the latter

That's it : I connect under ipoa protocol !!!

I can do some test for you if you want...

[alfonsor]

while you are connected with ipoa, enter telnet and do a ifconfig and post a result here; in the next days, I will try to make ddns work with ipoa if possible (in the next dayS

[dimakx]

Salve alfonsor,
prima di tutto le voglio fare i complimenti per l'incredibile progetto che ha deciso di portare avanti. Il mio DGN3500 ha ripreso vita!

Ma ho alcune domande inerenti alla sicurezza: analizzando il router dall'esterno della LAN ho notato che molte porte rimangono aperte anche all'esterno. il rischio di ricevere accessi non-autorizzati personalmente credo possa essere elevato. Il problema è che il firewall dice che nessuna incoming-connection ha porte attive; è possibile solo aprire le porte verso la lan e basta? Grazie e complimenti per il grande lavoro!

[alfonsor]

dalle pic minuscole non capisco molto;

quali porte secondo te sarebbero aperte dall'esterno? indicami i numeri ed il protocollo tipo 80/tcp

e dammi del tu per l'amor di dio

[RazerXXX]

Complimenti per il lavoro!

Ho appena aggiornato dalla 10.7 ed ho guadagnato mezzo MB

Grazie mille!

[dimakx]

Le porte rilevabili dall'esterno sono:

1) 80 -> http

2) 139 -> netbios-ssn

3) 443 -> http

4) 445 ->netbios-ssn

5) 5100 -> admd

6) 8080 -> soap

7) 8200 -> trivnet1

Grazie della disponibilità.

[alfonsor]

online ci sono un'infinità di siti per fare lo scan delle porte; per dire http://www.whatsmyip.org/port-scanner/

nessuno di questi rileva le porte aperte

non solo

usando nmap nella LAN

Not shown: 993 closed ports
PORT STATE SERVICE
21/tcp open ftp
23/tcp open telnet
53/tcp open domain
80/tcp open http
5000/tcp open upnp
5100/tcp open admd
8080/tcp open http-proxy

direi che quel programma che hai usato è del tutto non affidabile

[Dangze]

Originariamente inviato da alfonsor

while you are connected with ipoa, enter telnet and do a ifconfig and post a result here; in the next days, I will try to make ddns work with ipoa if possible (in the next dayS

Hi Alfonso,

here are the results. I've just replaced the public IP by xx.yy.zz.uu

DGN2200V4 / # amodfunc wan
ppp0
DGN2200V4 / # ifconfig
bcmsw Link encap:Ethernet HWaddr 20:0C:C8:19:7F:C6
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Base address:0xda00

br0 Link encap:Ethernet HWaddr 20:0C:C8:19:7F:C6
inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::220c:c8ff:fe19:7fc6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8844 errors:0 dropped:0 overruns:0 frame:0
TX packets:8233 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:821152 (801.9 KiB) TX bytes:9821730 (9.3 MiB)

eth0 Link encap:Ethernet HWaddr 20:0C:C8:19:7F:C6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth1 Link encap:Ethernet HWaddr 20:0C:C8:19:7F:C6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


eth2 Link encap:Ethernet HWaddr 20:0C:C8:19:7F:C6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


eth3 Link encap:Ethernet HWaddr 20:0C:C8:19:7F:C7
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


ipoa0 Link encap:Point-to-Point Protocol
inet addr:xx.yy.zz.uu P-t-P:xx.yy.zz.uu Mask:255.255.255.0
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:7496 errors:0 dropped:0 overruns:0 frame:0
TX packets:7449 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:9175316 (8.7 MiB) TX bytes:658965 (643.5 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:297 errors:0 dropped:0 overruns:0 frame:0
TX packets:297 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:54832 (53.5 KiB) TX bytes:54832 (53.5 KiB)

wl0 Link encap:Ethernet HWaddr 20:0C:C8:19:7F:C6
inet6 addr: fe80::220c:c8ff:fe19:7fc6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8825 errors:0 dropped:0 overruns:0 frame:0
TX packets:8975 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:942206 (920.1 KiB) TX bytes:10008428 (9.5 MiB)
Interrupt:31

I have to precise something :
My DGN2200V4 will be later on installed in another place (in Greece...) where the ADSL protocol is PPoE or PPoA (both working, but PPoA seems more stable...) with a dynamic IP. In this location, I run 2 IP cams and one temperature server, so I use No-IP and/or dtdns hostnames to access them from remote. I also connect to my modem a DD-WRT router (Linksys E1200) running OpenVPN to get a French IP necessary for my Smart TVs...
For the moment I am in France, where I normally use an ISP "Triple play Internet box" with a static IP. The protocol to be used when connecting through a standard modem is IPoA.

Since I bought the DGN2200V4, I was interested to test all its functionnalities, including uamod ones, and particularly the ddns functionnalities. But I can understand that they are not available with IPoA or Static IP protocols as they are not necessary in these cases where the IP never changes !...

So, If you can do something easily to test the ddns with IPoA, "just do it" , but don't waste your time with it just for me...

Thank you again for your work, have a nice day.

[asfdfdfd]

Hi Alfonso.

I use your firmware from the first versions and it is great. Thanks!

Recently i've decided to upgrade my DGN2200V3 from 1.0.x (probably 1.0.10, could not remember) to 3.0.7 and found that WiFi works pretty unstable.

It works for some time (maybe day or so) but then some devices drop connections and could not reconnect until router reboot (and new devices could not connect until router reboot too).

wpa_supplicant log from my android device told me that it has authentication timeout.

Do you know what may be the reason? What can i tune on router?

Also, where could i download old versions of your firmware?