• Dieses Thema hat 63 Antworten, 14 Teilnehmer, und wurde zuletzt am vor 8 Jahre, 5 Monate von Anonym aktualisiert.
Ansicht von 15 Beiträgen - 46 bis 60 (von insgesamt 64)
  • Autor
    Beiträge
  • #25557
    Anonym
    Inaktiv

    … ahh ok. Das die FW- Version schon vorher abgefragt wird, wusste ich nicht.
    Da ich fast ausschließlich s.g. Labor- Versionen benutze, habe ich wohl erstmal mit Zitronen gehandelt; na egal…

    Vielen Dank für die schnelle Klärung.

    #25558
    Babbel
    Teilnehmer

    ICh bin angemeldet aber bekomme nach den anderen anfänglichen Problemen nach einer gewissen Zeit immer eine Fehlermeldung angezeigt, dass es einen Verbindungsabruch gäbe.

    Ist das normal?

    #25559
    Thilo Brandt
    Keymaster

    Wenn du per WLAN mit der FB verbunden bist, da kann das passieren. Bei LAN sollte das eigentlich nicht vorkommen, es sei denn deine Netzwerkkarte oder ein anderes Netzwerkgerät (Router, Switch) haben Probleme…

    #25560
    Babbel
    Teilnehmer

    ICh dachte weil es der Port 80 ist, dass die sich da dann ab und an mal abmeldet. Hier stand nämlich mal etwas, dass auf einem anderen Port die Daten immer fliessen.

    #25561
    Thilo Brandt
    Keymaster

    Port 80 UND Port 1012 sind die FB Verbindungsports. Port 80 kann durch 443 ersetzt werden, wenn die FB auf SSL läuft. Port 1012 ist fix im Programm hinterlegt und kann nicht geändert werden. Ansonsten kann man keine Ports ändern. Auf Port 1012 ist eine TCP Sockel permanent verbunden, Port 80 ist per HTTP nur bei bedarf geöffnet.

    #25562
    Babbel
    Teilnehmer

    OK. Dann gehe ich mal davon aus das die FB Cable sich irgendwie in der Telefonie in den RUhemodus bringt, sodass es da zu Unterbrechungen kommt.

    #25563
    Thilo Brandt
    Keymaster

    Das ist dann der Fall, falls du den Energiesparmodus/Eco-Modus der FB Cable nutzt.

    #40073
    Anonym
    Inaktiv

    Hi,

    is there any reason why it doesn’t connect to Fritz!Box 06.06 (Fritz!Box 7340) ?

    [ INFO – 29/Oct/2015:17:34:23 +0000 – JAM-SWT/JFaceUI-Thread-(non-deamon) – de.janrufmonitor.fritzbox.firmware.FritzOS559Firmware.createSessionID() – Detected FRITZ!Box challenge code: 0282d4c1 ]

    [ INFO – 29/Oct/2015:17:34:23 +0000 – JAM-SWT/JFaceUI-Thread-(non-deamon) – de.janrufmonitor.fritzbox.firmware.FritzOS559Firmware.createSessionID() – Calculated FRITZ!Box response code: 0282d4c1-2129194e8752cd2121755f0310ca269a ]

    [ INFO – 29/Oct/2015:17:34:24 +0000 – JAM-SWT/JFaceUI-Thread-(non-deamon) – de.janrufmonitor.fritzbox.firmware.FritzOS559Firmware.createSessionID() – Detected FritzBox SID: 0d2773b051bd6e57 ]

     

    #40074
    Thilo Brandt
    Keymaster

    Hi fone9,

    latest version 5.0.60 supports FRITZ!OS up to 6.30. Your log extract looks like login IS working. Why do you assume login not to work?

    Best regards,
    Thilo

    #40078
    Anonym
    Inaktiv

    [ INFO – 29/Oct/2015:21:36:07 +0000 – JAM-SWT/JFaceUI-Thread-(non-deamon) – de.janrufmonitor.fritzbox.firmware.FirmwareManager.createFirmwareInstance() – No Unitymedia Firmware detected. ]

    [ INFO – 29/Oct/2015:21:36:07 +0000 – JAM-SWT/JFaceUI-Thread-(non-deamon) – de.janrufmonitor.fritzbox.firmware.FirmwareManager.createFirmwareInstance() – No FritzBox standard Firmware detected. ]

    [ INFO – 29/Oct/2015:21:36:07 +0000 – Thread-120 – de.janrufmonitor.ui.swt.DisplayManager.getDefaultDisplay() – Invoking thread name for DisplayManager.getDefaultDisplay(): Thread-120 ]

    [ WARNING – 29/Oct/2015:21:36:07 +0000 – JAM-SWT/JFaceUI-Thread-(non-deamon) – de.janrufmonitor.ui.jface.application.dialer.DialerDialog.okPressed() – de.janrufmonitor.fritzbox.firmware.exception.FritzBoxLoginException: FritzBox initializing failed: Unable to detect FritzBox firmware. ]

    [ INFO – 29/Oct/2015:21:36:07 +0000 – JAM-null#JAM-SWT/JFaceUI-Thread-(non-deamon)-Thread-(non-deamon) – de.janrufmonitor.ui.swt.DisplayManager.getDefaultDisplay() – Invoking thread name for DisplayManager.getDefaultDisplay(): JAM-null#JAM-SWT/JFaceUI-Thread-(non-deamon)-Thread-(non-deamon) ]

    [ INFO – 29/Oct/2015:21:36:07 +0000 – Thread-122 – de.janrufmonitor.ui.swt.DisplayManager.getDefaultDisplay() – Invoking thread name for DisplayManager.getDefaultDisplay(): Thread-122 ]

    [ INFO – 29/Oct/2015:21:36:07 +0000 – JAM-null#JAM-SWT/JFaceUI-Thread-(non-deamon)-Thread-(non-deamon) – de.janrufmonitor.ui.swt.DisplayManager.getDefaultDisplay() – Invoking thread name for DisplayManager.getDefaultDisplay(): JAM-null#JAM-SWT/JFaceUI-Thread-(non-deamon)-Thread-(non-deamon) ]

    [ INFO – 29/Oct/2015:21:36:07 +0000 – JAM-SWT/JFaceUI-Thread-(non-deamon) – de.janrufmonitor.ui.swt.DisplayManager.getDefaultDisplay() – Invoking thread name for DisplayManager.getDefaultDisplay(): JAM-SWT/JFaceUI-Thread-(non-deamon) ]

    [ SEVERE – 29/Oct/2015:21:36:07 +0000 – JAM-SWT/JFaceUI-Thread-(non-deamon) – de.janrufmonitor.ui.jface.dialogs.DialogPropagator$1$1.run() – loginfailed ]

    de.janrufmonitor.fritzbox.firmware.exception.InvalidSessionIDException: FritzBox initializing failed: Unable to detect FritzBox firmware.

    at de.janrufmonitor.fritzbox.firmware.FirmwareManager.createFirmwareInstance(FirmwareManager.java:384)

    at de.janrufmonitor.fritzbox.firmware.FirmwareManager.login(FirmwareManager.java:65)

    at de.janrufmonitor.ui.jface.application.dialer.DialerDialog.okPressed(DialerDialog.java:211)

    at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:464)

    at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616)

    at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)

    at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)

    at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)

    at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)

    at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)

    at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)

    at org.eclipse.jface.window.Window.open(Window.java:796)

    at de.janrufmonitor.ui.jface.application.dialer.DialerCommand.asyncExecute(DialerCommand.java:48)

    at de.janrufmonitor.ui.jface.application.AbstractAsyncDisplayCommand$1$1.run(AbstractAsyncDisplayCommand.java:21)

    at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source)

    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source)

    at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source)

    at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)

    at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)

    at org.eclipse.jface.window.Window.open(Window.java:796)

    at de.janrufmonitor.ui.jface.application.journal.Journal.open(Journal.java:377)

    at de.janrufmonitor.ui.jface.application.journal.JournalCommand.asyncExecute(JournalCommand.java:49)

    at de.janrufmonitor.ui.jface.application.AbstractAsyncDisplayCommand$1$1.run(AbstractAsyncDisplayCommand.java:21)

    at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source)

    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source)

    at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source)

    at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)

    at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)

    at org.eclipse.jface.window.Window.open(Window.java:796)

    at de.janrufmonitor.ui.jface.application.editor.EditorCommand.asyncExecute(EditorCommand.java:47)

    at de.janrufmonitor.ui.jface.application.AbstractAsyncDisplayCommand$1$1.run(AbstractAsyncDisplayCommand.java:21)

    at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source)

    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source)

    at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source)

    at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)

    at de.janrufmonitor.ui.swt.DisplayManager$1.run(DisplayManager.java:102)

     

    [ INFO – 29/Oct/2015:21:36:07 +0000 – JAM-SWT/JFaceUI-Thread-(non-deamon) – de.janrufmonitor.ui.swt.DisplayManager.getDefaultDisplay() – Invoking thread name for DisplayManager.getDefaultDisplay(): JAM-SWT/JFaceUI-Thread-(non-deamon) ]

    [ INFO – 29/Oct/2015:21:36:07 +0000 – JAM-null#JAM-SWT/JFaceUI-Thread-(non-deamon)-Thread-(non-deamon) – de.janrufmonitor.ui.swt.DisplayManager.getDefaultDisplay() – Invoking thread name for DisplayManager.getDefaultDisplay(): JAM-null#JAM-SWT/JFaceUI-Thread-(non-deamon)-Thread-(non-deamon) ]

    [ INFO – 29/Oct/2015:21:36:08 +0000 – JAM-SWT/JFaceUI-Thread-(non-deamon) – de.janrufmonitor.ui.swt.DisplayManager.getDefaultDisplay() – Invoking thread name for DisplayManager.getDefaultDisplay(): JAM-SWT/JFaceUI-Thread-(non-deamon) ]

    [ INFO – 29/Oct/2015:21:36:08 +0000 – JAM-SWT/JFaceUI-Thread-(non-deamon) – de.janrufmonitor.ui.swt.DisplayManager.getDefaultDisplay() – Invoking thread name for DisplayManager.getDefaultDisplay(): JAM-SWT/JFaceUI-Thread-(non-deamon) ]

    [ INFO – 29/Oct/2015:21:36:08 +0000 – JAM-SWT/JFaceUI-Thread-(non-deamon) – de.janrufmonitor.ui.swt.DisplayManager.getDefaultDisplay() – Invoking thread name for DisplayManager.getDefaultDisplay(): JAM-SWT/JFaceUI-Thread-(non-deamon) ]

    [ INFO – 29/Oct/2015:21:36:28 +0000 – JAM-DatabaseI18nManagerConnectionObserver-Thread-(deamon) – de.janrufmonitor.repository.db.AbstractDatabaseHandler.disconnect() – DatabaseHandler successfully disconnected. ]

    [ INFO – 29/Oct/2015:21:36:30 +0000 – JAM-HibernateDetect-Thread-(deamon) – de.janrufmonitor.service.hibernate.HibernateDetect$1.run() – Delta hibernate detection time (ms): 60002 ]

    [ INFO – 29/Oct/2015:21:37:30 +0000 – JAM-HibernateDetect-Thread-(deamon) – de.janrufmonitor.service.hibernate.HibernateDetect$1.run() – Delta hibernate detection time (ms): 60001 ]

     

    #40080
    Thilo Brandt
    Keymaster

    Hi fone9,

    ok, the firmware gets not detected. Is it an original AVM firmware version or a reseller modified one?

    Best regards,
    Thilo

    #40083
    Anonym
    Inaktiv

    It is  the native Fritz!Box 7340 manufacturer firmware though the 7340 is not very popular (besides Netherlands) hence maybe your software doesn’t have it allowed/listed?

    Lastly it was updated February 2014 via online update.

    #40084
    Thilo Brandt
    Keymaster

    Hi fone9,

    ok, that could be the reason. Maybe there is some difference in this FB variant, which might cause the detection mechanism not to work. You could maybe increase the tracing of the that application (see http://www.janrufmonitor.de/logging) to get more insights. Please sent me the jan-0.log after you have restarted the application with detailed tracing option.

    Thilo

    #40085
    Anonym
    Inaktiv

    [ FINE – 30/Oct/2015:09:19:48 +0000 – ModalContext – de.janrufmonitor.fritzbox.firmware.FritzOSFirmware.executeURL() – Data received from FritzBox: ]

    [ FINE – 30/Oct/2015:09:19:48 +0000 – ModalContext – de.janrufmonitor.fritzbox.firmware.FritzOSFirmware.executeURL() – <?xml version=“1.0″ encoding=“utf-8″?><SessionInfo><SID>0000000000000000</SID><Challenge>70168413</Challenge><BlockTime>0</BlockTime><Rights></Rights></SessionInfo>

    ]

    [ INFO – 30/Oct/2015:09:19:48 +0000 – ModalContext – de.janrufmonitor.fritzbox.firmware.FritzOSFirmware.createSessionID() – Detected FritzBox challenge code: 70168413 ]

    [ INFO – 30/Oct/2015:09:19:48 +0000 – ModalContext – de.janrufmonitor.fritzbox.firmware.FritzOSFirmware.createSessionID() – Calculated FritzBox response code: 70168413-0bdce3996de6993d7fb34d6ca40e11ba ]

    [ FINE – 30/Oct/2015:09:19:48 +0000 – ModalContext – de.janrufmonitor.fritzbox.firmware.FritzOSFirmware.executeURL() – Data received from FritzBox: ]

    [ FINE – 30/Oct/2015:09:19:48 +0000 – ModalContext – de.janrufmonitor.fritzbox.firmware.FritzOSFirmware.executeURL() – <?xml version=“1.0″ encoding=“utf-8″?><SessionInfo><SID>9e6449a2161b6496</SID><Challenge>f3bb4a4e</Challenge><BlockTime>0</BlockTime><Rights><Name>Dial</Name><Access>2</Access><Name>HomeAuto</Name><Access>2</Access><Name>BoxAdmin</Name><Access>2</Access><Name>Phone</Name><Access>2</Access><Name>NAS</Name><Access>2</Access></Rights></SessionInfo>

    ]

    [ INFO – 30/Oct/2015:09:19:48 +0000 – ModalContext – de.janrufmonitor.fritzbox.firmware.FritzOSFirmware.createSessionID() – Detected FritzBox SID: 9e6449a2161b6496 ]

    [ FINE – 30/Oct/2015:09:19:48 +0000 – ModalContext – de.janrufmonitor.fritzbox.firmware.FritzOSFirmware.executeURL() – Data received from FritzBox: ]

    [ FINE – 30/Oct/2015:09:19:48 +0000 – ModalContext – de.janrufmonitor.fritzbox.firmware.FritzOSFirmware.executeURL() – <!DOCTYPE html>

    <html>

    <head>

    <meta http-equiv=content-type content=“text/html; charset=utf-8″>

    <meta http-equiv=“X-UA-Compatible“ content=“IE=edge“>

    <title>About FRITZ!OS</title>

    <link rel=“stylesheet“ type=“text/css“ href=“/css/default/main.css“/>

    <link rel=“stylesheet“ type=“text/css“ href=“/css/default/print.css“ media=“print“/>

    <!–[if lte IE 7]>

    <link rel=“stylesheet“ type=“text/css“ href=“/css/default/ie_fix.css“/>

    <![endif]–>

    <!–[if IE]>

    <style type=“text/css“>

    .hide_ftp_link {display: none;}

    </style>

    <![endif]–>

    <script type=“text/javascript“ src=“/js/jxl.js“></script>

    <script type=“text/javascript“ src=“/js/ready.js“></script>

    <script type=“text/javascript“ src=“/js/help.js“></script>

    <script type=“text/javascript“ src=“/js/popup.js?lang=en“></script>

    <script type=“text/javascript“ src=“/js/zebra.js“></script>

    <!–[if lt IE 8]>

    <script type=“text/javascript“ src=“/js/imgbuttonfixer.js“></script>

    <![endif]–>

    <script type=“text/javascript“>

    //Click Waitcourser anzeigen

    //ready.onReady(globalOnClick.init);

    if (window.location.search.indexOf(„&popupwnd=1″)!=-1) {

    ready.onReady(popup.prepareHeader);

    }

    ready.onReady(help.show);

    ready.onReady(zebra);

    </script>

     

    </head>

    <body>

    <!– pagename:/home/pp_fbos.lua–>

    <div class=“popup_button_row popuphead“>

    <button id=“btn_print“ onclick=“window.print()“>

    Print Page</button>

    <button id=“btn_close“ onclick=“window.close()“>

    Close Window</button>

     

    </div>

    <div id=“main_popup_page_all“>

    <div id=“nil“>

    <div class=“blue_bar_left_edge“></div>

    <div class=“blue_bar_right_edge“></div>

    <div id=“contentTitle“ class=“blue_bar_back“>

    <h2>About FRITZ!OS</h2>

    </div>

    <div id=“page_content“ class=“page_content“>

     

    <form method=“POST“ action=“/home/pp_fbos.lua?sid=9e6449a2161b6496″ id=“uiMainForm“>

     

    <div>

    <p>FRITZ!Box Fon WLAN 7340, fritzbox

    </p>

    <p>FRITZ!OS 06.06

    </p>

    </div>

     

    <hr>

    <div>

    <iframe seamless src=“http://help.avm.de/fritzbox.php?hardware=171&oem=avme&language=en&country=&version=99.06.06&subversion=&set=012&action=feature&#8220; style=“height:330px;“>

    </iframe>

    </div>

    </form>

    </div>

    <div class=“clear_float“></div>

    <div class=“page_bottom_container“>

    <div class=“page_left_bottom“></div>

    <div class=“page_right_bottom“></div>

    <div class=“page_back_bottom“ style=““>

    <div id=“MainPagebottom“>

    </div>

    </div>

    </div>

    </div>

    </div>

     

     

     

    <div id=“logqueries“ style=“clear:both; display:none;“>

    
    script = /home/pp_fbos.lua
    
    GET = {
    
    }
    
    POST = {
    
    }
    
    QUERIES = {
    
    ["box:settings/hostname"] = "fritzbox",
    
    ["boxusers:settings/compatibility_mode"] = "0",
    
    ["boxusers:settings/last_homenetwork_username"] = "",
    
    ["boxusers:settings/skip_auth_from_homenetwork"] = "0",
    
    ["logic:status/nspver"] = "99.06.06",
    
    ["rights:status/BoxAdmin"] = "2",
    
    ["rights:status/boxuser_UID"] = "boxuser97",
    
    ["rights:status/userid"] = "97",
    
    ["rights:status/username"] = ""
    
    }
    
    MQUERIES = {
    
    }
    
    CONFIG = {
    
    ["BETA_RELEASE"] = 0,
    
    ["GUI_IS_POWERLINE"] = false,
    
    ["GUI_IS_REPEATER"] = false,
    
    ["GUI_LAN_GUEST"] = false,
    
    ["GUI_NEW_FAX"] = true,
    
    ["GUI_SIP_READ_ONLY"] = true,
    
    ["GUI_WLAN_DOUBLEMONITOR"] = false,
    
    ["LABOR_ID_NAME"] = false,
    
    ["ONLINEHELP_URL"] = "http://help.avm.de/fritzbox.php?hardware=171&oem=avme&language=en&country=&version=99.06.06&subversion=",
    
    ["PRODUKT_NAME"] = "FRITZ!Box Fon WLAN 7340",
    
    ["RELEASE"] = 1,
    
    ["SESSIONID"] = true,
    
    ["WEBCM_INTERPRETER"] = true,
    
    ["country"] = "99",
    
    ["gu_type"] = "release",
    
    ["isDebug"] = false,
    
    ["is_6360"] = false,
    
    ["isp_mac_needed"] = true,
    
    ["language"] = "en",
    
    ["language_is_de"] = false,
    
    ["need_reboot"] = false,
    
    ["no_ir_pc_rss_samples"] = true,
    
    ["no_number_area"] = true,
    
    ["oem"] = "avme",
    
    ["sip_packetsize"] = true,
    
    ["sip_provider_international"] = true,
    
    ["timezone"] = true,
    
    ["use_nat"] = true
    
    }
    
    

    </div>

    </body>

    </html>

     

    ]

    [ INFO – 30/Oct/2015:09:19:48 +0000 – ModalContext – de.janrufmonitor.fritzbox.firmware.FirmwareManager.createFirmwareInstance() – No Fritz!OS 05.50+ Firmware detected. ]

    #40086
    Anonym
    Inaktiv

    Also I requested preparing the newest firmware 99.06.30 as other models got it recently.

Ansicht von 15 Beiträgen - 46 bis 60 (von insgesamt 64)
  • Du musst angemeldet sein, um auf dieses Thema antworten zu können.