DrayTek Vigor 167 No promt detected #10
Comments
|
Does the connection work and provide usable data, if you change |
|
Just tested the binary, but this would solve the issue on my opinion. The telnet commands are the same as before |
|
Changing the expected prompt would probably make the initial connection work, but it may still fail later when loading data. The output of the If you test it and it actually works, I'm of course happy to add support for this different prompt. Please send me a copy of the Instructions for building from source are available in the documentation. If you need any further help, please ask! |
|
I have a Draytek Vigor 167 set as modem. My goal was or is to use the wonderful project https://github.com/Dentrax/xdsl-exporter which utilizes go-dsl. I can confirm that the prompt issue is fixed when changing However as @janh mentioned, the adsl command might interfere here as potentially not available?! raw.txt from macOS: Not sure if this is of interest but i can confirm that the modem is actually outputting data on telnet: |
|
@woorszt: So the device actually has a completely different command line interface as expected. However it looks like adding support for it should be possible. I need some additional information for that:
|
|
Hey Jan, sorry for the delay. Been on the road the last days. Here's more: SSH is supported but i cannot add any command or username. It always asks me for Username and Password regardless of the below attempts: So SSH is supported as well but gives the same behavior as telnet. I'm not an SSH expert. Maybe there is another way i can try? Cheers |
|
Thank you! This means that SSH support would require additional work, so I sticking with Telnet will be easier. Can you try if something like Shoudln't really be an issue if none of that works, but it would make the implementation a bit easier / more robust. |
|
Seems not to work: |
|
Could you try the "draytek-v5" branch to check if it works? If it does, please attach an unmodified copy of the "raw.txt" as a reference. (The vendor ID fields only specify the vendor and a version number.) |
|
Seems there is an issue passing the command: 
|
|
Thank you for testing! As far as I can see, the command that fails is exactly the same as the one that works via regular Telnet connection. Can you do a packet capture and compare it to find out what's going wrong here? If you want to share packet capture data: In Wireshark, follow the TCP stream, then choose "Hex Dump" as display format. The resulting text is enough (just remove the password or change it beforehand). |
|
sure: Maybe adding a sleep 1 may be worth trying between the sequences? Just realized it may also be sent twice. Get the same error when doing the following: I have limited experience interpreting hex dumps |
|
Thabk you. I assume this capture is from a manual connection via telnet command? Can you also do a capture when using the tool, to find out what exactly is going wrong there? Also, it is hard to see which side sends which data in this dump. I don't know which tool you used for the capture, but with Wireshark the "Hex Dump" format uses indentation to show it: https://www.wireshark.org/docs/wsug_html_chunked/ChAdvFollowStreamSection.html Does the "exit" command go back to the main menu? Because from your last test, it looks like this will be necessary between fetching general/tone data. However, that doesn't explain the current issue, because it seems to happen already with the first command. |
|
I startet Wireshark to capture my wifi interface, set a filter to Red is Macbook -> Modem Yes, Exit is needed to switch from General to Tone and vice versa: |
That error actually makes sense given the packet capture. I think my Telnet client just gets a bit confused because the device sends redundant carriage returns ("0d0d0a" after the command). Like, it's not wrong, just unnecessary. But that should be possible to fix. What really confuses me, is the error in your previous screenshot (where you used the GUI). I don't understand why the device would return "Unknown command" for the first command already. I assume that a new Telnet connection always begins at the root prompt (i.e. just "vigor>" and not some submenu). I'm going to add some changes and write another message once it is ready to test. |
|
I updated the Telnet client and added the "exit" command after "show all". Can you try if it works now? |
|
One step further. This is the output from the General request 
Appears to me that the Telnet client needs to manually push for MORE. As the output of the Tone request is even more data, i think this might also be considered here multiple times. This is at least what i have to do in my terminal (iTerm). Thanks Jan. |
|
OK, that is bad, because supporting this would require more significant changes to the Telnet client. And I don't really want to implement that. Is there any way to make the device return the entire data at once? Otherwise, it might make more sense to look at the web interface instead. From the simulator on the DrayTek website it looks like the exact same data is also available that way. The question is just how difficult it is to implement without direct access to the device (but that is also an issue for the Telnet approach). |
|
Thanks for your efforts, Jan. I'll try to get in contact with Draytek to see if there is another way.. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
the Draytek Vigor 167 Fimware 5.2 promt is "Username:" instead of "Account:" so no promt detected error is thrown.
Thanks!
baba
The text was updated successfully, but these errors were encountered: