Today I tried reinstalling the GenieACS server in an Ubuntu 15.10 Server and it went perfectly well... All problems disappeared

El 30/09/15 a las 11:02, Sergio Fernández escribió:
Today I tried sending commands to the CPE. The CPE answered me with a 401 Unauthorized. I deactivated the login to the CPE and now I can commit tasks like rebooting it. But the problem still persists, I can't make all the parameters to appear. When I send a getParameterValues on the InternetGatewayDevice option, it shows me that it has invalid arguments. This doesn't happen, for example, if I do it for InternetGatewayDevice.DeviceSummaryInternetGatewayDevice:1.1[](Baseline:1, EthernetLAN:1, USBLAN:1, WiFiLAN:1, ADSLWAN:1, Time:1, IPPing:1, ATMLoopback:1, DSLDiagnostics:1, DeviceAssociation:1).
There are parameters that fault, others that doesn't...

Thank you for your help and dedication.

El 29/09/15 a las 13:02, Sergio Fernández escribió:
Now after doing this, I can see that the CPE still makes an inform every 5 seconds. The CPE wasn't doing this before! but the list of available parameters is still so short.

El 29/09/15 a las 12:59, Sergio Fernández escribió:
I've tried again with another user/pass and the problem still persists, and I've tried deleting the cpe and rebooting the server also, refreshing InternetGatewayDevice tells me "Invalid arguments" under the "Fault" column.

Thank you.

El 29/09/15 a las 10:20, Dariusz Szymański escribió:
You are sure that your connection request username/password match to
auth.js?
If yes then have yyou tried to refresh on the InternetGatewayDevice
paramerer, or try to remove the device?


-----Original Message-----
From: Users [mailto:[email protected]] On Behalf Of Sergio
Fernández
Sent: Tuesday, September 29, 2015 10:16 AM
To: Community support for GenieACS users <[email protected]>
Subject: Re: Parameters doesn't show up

Thank you for answering me.

I've changed the parameter options, cleared them... To see if it helps but
nothing. You can see the parameters of the CPE in the image attached.

I've also put an user/pass in auth.js and the same in the CPE but it's still
the same.

The thing that makes me wonder why is not working is because the CPE sends all his parameters in the pcap file I sent in the email before, but GenieACS seems like not picking it up correctly and making the CPE to disconnect.

Thank you a lot, guys!

El 29/09/15 a las 09:30, Dariusz Szymański escribió:
Hi,

I had the same issue, the problem was that there ware some custom
connection request username and password on the cpe so acs could't
connect to it and get the parameters.

Darek Sz.

-----Original Message-----
From: Users [mailto:[email protected]] On Behalf Of
Sergio Fernández
Sent: Monday, September 28, 2015 12:32 PM
To: Community support for GenieACS users <[email protected]>
Subject: Re: Parameters doesn't show up

Thank you, Zaid

I've mounted again GenieACS and found that I always suffer this error.
Adding the option "COOKIES_PATH" : "/" to config.json didn't help

I also have noticed that when the CPE first contacts with the ACS it
sends the whole XML file (with all the parameters) but maybe the
GenieACS doesn't know how to get them. Then, as you can see on the
pcap file, there's no more connections from the CPE. (In the CPE I
have set to inform every 30 seconds, this worked a month ago, so it
may be not a problem of the CPE, but no clue of what's happening)

Thank you!

Sergio Fernández

El 04/09/15 a las 01:45, Zaid Abdulla escribió:
On Tue, Sep 1, 2015, at 01:46 PM, Sergio Fernández wrote:
Hello!

I've mounted a second server for testing inside a VMware.

I connected a Tenda W300D and some parameters appear but I can't
make the rest of the parameters to be shown.
Here I send you the .dump attached. What I can see is that the
parameters I can see are in this dump but I can't see the other.

In the first machine I installed GenieACS in, I didn't have these
problems with these types of router. I don't know what is happening.
Looks like the common cookies issue. Try adding the following option
to
config.json:

       "COOKIES_PATH" : "/"

If this doesn't help, try to capture the communication using tcpdump
or Wireshark and look for the cookie headers of the CPE request that
comes immediately after the very last ACS request you see in the dump
file you attached.

Zaid
_______________________________________________
Users mailing list
[email protected]
http://lists.genieacs.com/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.genieacs.com/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.genieacs.com/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.genieacs.com/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.genieacs.com/mailman/listinfo/users



_______________________________________________
Users mailing list
[email protected]
http://lists.genieacs.com/mailman/listinfo/users
------------------------------------------------------------------------
_______________________________________________
Users mailing list
[email protected]
http://lists.genieacs.com/mailman/listinfo/users

Reply via email to