Test Firewall fallito

[wicom]

Ciao Ragazzi

Ho qualche problema con il test del firewall, ovvero effettuando il test del mio firewall ho il seguente risponso:

3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.

: Phase 1, checking servers connection, please wait...
: Stun Checker service is reachable. Phase 1 check passed.
: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
: UDP SIP Port is set to 5060. Response received WITH TRANSLATION 63305::5060. Phase 2a check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/

: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
: TCP SIP Port is set to 5060. Response received WITH TRANSLATION 63305::5060. Phase 2b check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/

: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
: TCP TUNNEL Port is set to 5090. Response received WITH TRANSLATION 63318::5090. Phase 3 check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/

: Phase 4. Check Port Forwarding to RTP external port range, please wait...
: UDP RTP Port 9000. Response received WITH TRANSLATION 63319::9000. Phase 4-01 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9001. Response received WITH TRANSLATION 63320::9001. Phase 4-02 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9002. Response received WITH TRANSLATION 63321::9002. Phase 4-03 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9003. Response received WITH TRANSLATION 63322::9003. Phase 4-04 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9004. Response received WITH TRANSLATION 63323::9004. Phase 4-05 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9005. Response received WITH TRANSLATION 63324::9005. Phase 4-06 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9006. Response received WITH TRANSLATION 63325::9006. Phase 4-07 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9007. Response received WITH TRANSLATION 63326::9007. Phase 4-08 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9008. Response received WITH TRANSLATION 63327::9008. Phase 4-09 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9009. Response received WITH TRANSLATION 63328::9009. Phase 4-10 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9010. Response received WITH TRANSLATION 63329::9010. Phase 4-11 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9011. Response received WITH TRANSLATION 63330::9011. Phase 4-12 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9012. Response received WITH TRANSLATION 63331::9012. Phase 4-13 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9013. Response received WITH TRANSLATION 63332::9013. Phase 4-14 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9014. Response received WITH TRANSLATION 63333::9014. Phase 4-15 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9015. Response received WITH TRANSLATION 63334::9015. Phase 4-16 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9016. Response received WITH TRANSLATION 63335::9016. Phase 4-17 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9017. Response received WITH TRANSLATION 63336::9017. Phase 4-18 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9018. Response received WITH TRANSLATION 63337::9018. Phase 4-19 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9019. Response received WITH TRANSLATION 63338::9019. Phase 4-20 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9020. Response received WITH TRANSLATION 63339::9020. Phase 4-21 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9021. Response received WITH TRANSLATION 63340::9021. Phase 4-22 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9022. Response received WITH TRANSLATION 63341::9022. Phase 4-23 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9023. Response received WITH TRANSLATION 63342::9023. Phase 4-24 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9024. Response received WITH TRANSLATION 63343::9024. Phase 4-25 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9025. Response received WITH TRANSLATION 63344::9025. Phase 4-26 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9026. Response received WITH TRANSLATION 63345::9026. Phase 4-27 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9027. Response received WITH TRANSLATION 63346::9027. Phase 4-28 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9028. Response received WITH TRANSLATION 63347::9028. Phase 4-29 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9029. Response received WITH TRANSLATION 63348::9029. Phase 4-30 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9030. Response received WITH TRANSLATION 63349::9030. Phase 4-31 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9031. Response received WITH TRANSLATION 63350::9031. Phase 4-32 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9032. Response received WITH TRANSLATION 63351::9032. Phase 4-33 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9033. Response received WITH TRANSLATION 63352::9033. Phase 4-34 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9034. Response received WITH TRANSLATION 63353::9034. Phase 4-35 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9035. Response received WITH TRANSLATION 63354::9035. Phase 4-36 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9036. Response received WITH TRANSLATION 63355::9036. Phase 4-37 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9037. Response received WITH TRANSLATION 63356::9037. Phase 4-38 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9038. Response received WITH TRANSLATION 63357::9038. Phase 4-39 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9039. Response received WITH TRANSLATION 63358::9039. Phase 4-40 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9040. Response received WITH TRANSLATION 63359::9040. Phase 4-41 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9041. Response received WITH TRANSLATION 63360::9041. Phase 4-42 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9042. Response received WITH TRANSLATION 63361::9042. Phase 4-43 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9043. Response received WITH TRANSLATION 63362::9043. Phase 4-44 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9044. Response received WITH TRANSLATION 63363::9044. Phase 4-45 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9045. Response received WITH TRANSLATION 63364::9045. Phase 4-46 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9046. Response received WITH TRANSLATION 63365::9046. Phase 4-47 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9047. Response received WITH TRANSLATION 63366::9047. Phase 4-48 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9048. Response received WITH TRANSLATION 63367::9048. Phase 4-49 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/
: UDP RTP Port 9049. Response received WITH TRANSLATION 63368::9049. Phase 4-50 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit https://www.3cx.com/blog/docs/firewall-checker/

Come vedete mi dice OK sulla 5060 in UDP Phase 2b check passed with WARNINGS, OK sulla 5060 TCP Phase 2b check passed with WARNINGS, il Tunnel non mi interessa e poi la stessa cosa succede per il protocollo RTP.

Faccio notare che sul mio router non ho forwardato nessuna porta, ho fatto una prova a forwardare la 5060 TCP e UDP ma non cambia il test segnale sempre gli stessi errori, quindi al momento le porte non sono forwardate sul router... cosa pensate possa essere?

 

[eurylink.com]

appunto le porte non Nattate sul router....

Ciao

 

[wicom]

Ciao eurylink

se leggi bene il mio post c'è scritto che ho fatto il test del firewall anche nattando le porte sul router e il problema non cambia rimane tale e quale, a questo punto mi chiedo a cosa serve aprire le porte sul router se cmq il centralino funziona uguale??

 

[eurylink.com]

Il problema che hai non è imputabile al centralino a unicamente all'hardware o al software che utilizzi. I problemi potrebbero essere molti. Ti elenco i principali:
1) Porte non Nattate sul router o problemi sul router ad eseguire il Nat (soprattutto su modelli molto economici o datati).
2) Firewall attivo sul router (inutile indirizzare le porte se poi sono chiuse dela firewall).
3) Firewall attivo sul PC che ospita il centralino (es quello di windows oppure le diverse versioni incorporate nei sistemi antivirus tipo Symantec, Kaspersky......)

Quindi assicurati di non ricadere in uno dei seguenti casi .... per il resto ti assicuro che con le configurazioni fatte a dovere 3CX non ha assolutamente problemi.

Ciao

 

[wicom]

Ciao Matteo

Leggendo il tuo post mi sono accorto che possibilmente mi manchi qualche direttiva ovvero:

1) Probabilmente il mio router non esegue bene il NAT e quindi nonostante io vada nattare le porte poi lui non gestisce bene questa cosa e il problema resta li dov'è.
2) Volendo analizzare il discorso firewall ecco qua vorrei aprire una piccola parentesi, il primo test che ho fatto sul centralino è stato eseguitonel mio ufficio dove ho una serie di cose tra il mio centralino e il mondo esterno ovvero:
connessione internet con Albacom --> Router di albacom --> Server Linux SME Server --> SME ha 2 schede di rete una guarda il router e l'altra guarda lam ia rete interna --> sulla rete interna c'è il mio centralino.
Adesso sul router ho chiesto ad albacom di aprire tutte le porte verso un solo indirizzo IP che è quello della prima scheda di rete di SME, quella che sta tra il router e SME, così posso gestire io l'apertura delle porte tramite il mio server linux e fin qui tutto bene il problema sta su IPtables cioè il firewall di SME, perchè la gestione delle porte mi viene facile ma con IPtables non ho molta dimistichezza quindi è possibile che il problema sia proprio li e qui mi rifaccio al quesito nr 2 che mi hai evidenziato tu.
3) per quanto riguarda il firewall di windows nessun problema ho disattivato tutto e non ho installato nessun software antivirus come avg, kaspesky o altro.

Fatto questo ho pensato bene di portare il centralino a casa dove ho una connessione ADSL semplice con telecom ed un router sitecom (giocattolo) quindi la cosa è facilmente gestibile.
Il router ha il firewall disattivato, e lo porte nattate come sappiamo 5060, 3478, 9000-9049, ma nonostante ciò il problema continua a persistere, e qui credo entri in gioco il quesito nr 1 ovvero problemi sul router (giocattolo) ad eseguire il NAT.
Che dire sono stato sfortunato faccio altre prove almeno che qualcuno non sa lavorare con IPtables e mi spiega come disattivare il firewall di SME Server.

Max

 

[eurylink.com]

Mi domando cosa tu ci faccia con un firewall Linux se poi di fatto non lo utilizzi. Te lo chiedo perchè mi sembra un controsenso installare un firewall solo per dire che è installato specie se poi genera tutti quei problemi ogni volta che devi apportare una modifica.
Multinazionali e Situazioni critiche a parte, la mia opinione è che sia meglio orientarsi su un firewall che garantisca un buon livello di protezione e che sia alla portata dell'amministratore di sistema. Io personalmente preferisco sempre utilizzare apparecchiature che conosco almeno all'80-90% delle potenzialità. Mi spaventerebbe installare un sistema su cui non ho il pieno controllo. Con i firewall il discorso vale ancora di più...decisamente meglio un apparato di livello medio ben configurato ed ottimizzato piuttosto che un sistema molto più complesso ma poco o per nulla ottimizzato.
Ovviamente il discorso non vale se il server linux è dell'azienda per cui lavori e tu non hai potere decisionale in merito.

Considera che guardando la tua configurazione aziendale credo che tu abbia un problema di doppio, se non di triplo NAT. In quelle condizioni direi che utilizzare un sistema Voip in maniera efficace sia un'impresa titanica.

Ovviamente la mia è solo una considerazione, un suggerimento, e non certo una critica.

Ciao

 

[wicom]

Ciao Matteo il firewall di linux si installa automaticamente quando installi una distro, presumo che nel mio caso avendo installato SME server il firewall prenda un impostazione di default con alcune restizione, ma come ti dicevo nel precedente post non avendo dimistichezza con Ip Tables non saprei cosa fare per verificare se ci sono particolari configurazioni.
Non so magari c'è un comando per disattivarlo completamente.