[Ovmsdev] wifi not coming all the way up?
Greg D.
gregd2350 at gmail.com
Mon Mar 19 11:39:14 HKT 2018
For what it's worth, I have the default log level at Info, and have no
trouble getting WiFi to connect (with IP).
That said, my module is currently in a state where both wifi and modem
have IP addresses, but the server can't (or won't) connect. Stopping /
starting the V2 server hangs the module (no prompt returned). Repeated
the test, and the bad state seems to occur just after the modem gets its
IP address. Wifi connected or not, that's the last the module will talk
to anything else.
Greg
Stephen Casner wrote:
> Hmmm, I just did a config change for the default log level from WARN
> to INFO so I could see more of the timing of wifi and MDNS starting,
> etc. Now the wifi does get an address and the status looks good.
> Perhaps some subtle timing sensitivity?
>
> -- Steve
>
> On Mon, 19 Mar 2018, Mark Webb-Johnson wrote:
>
>> Very bizarre. Nothing in auto should affect this.
>>
>> You've tried resetting the module?
>>
>> Can you paste the output of 'wifi scan', so we can see the APs in range?
>>
>> Regards, Mark.
>>
>>> On 19 Mar 2018, at 9:11 AM, Stephen Casner <casner at acm.org> wrote:
>>>
>>> Here's my wifi status:
>>>
>>> OVMS # wifi mode client Revelstoke
>>> Starting WIFI as a client to Revelstoke...
>>> I (316264) wifi: wifi firmware version: ebd3e5d
>>> I (316264) wifi: config NVS flash: enabled
>>> I (316264) wifi: config nano formating: disabled
>>> I (316264) wifi: Init dynamic tx buffer num: 16
>>> I (316264) wifi: Init data frame dynamic rx buffer num: 16
>>> I (316264) wifi: Init management frame dynamic rx buffer num: 16
>>> I (316264) wifi: wifi driver task: 3ffe8390, prio:23, stack:4096
>>> I (316264) wifi: Init static rx buffer num: 4
>>> I (316264) wifi: Init dynamic rx buffer num: 16
>>> I (316264) wifi: wifi power manager task: 0x3ffef838 prio: 21 stack: 2560
>>> I (316274) wifi: mode : sta (30:ae:a4:37:1b:84)
>>> I (318694) wifi: n:1 0, o:1 0, ap:255 255, sta:1 0, prof:1
>>> I (319344) wifi: state: init -> auth (b0)
>>> I (319354) wifi: state: auth -> assoc (0)
>>> I (319364) wifi: state: assoc -> run (10)
>>> I (319394) wifi: connected with Revelstoke, channel 1
>>> I (322364) wifi: pm start, type:0
>>> OVMS # wifi status
>>> WiFi
>>> Power: on
>>> Mode: Client mode
>>>
>>> STA SSID: Revelstoke
>>> MAC: 00:00:00:00:00:00
>>> IP: 0.0.0.0/0.0.0.0
>>> GW: 0.0.0.0
>>> OVMS # net
>>> Interface#0: lo0 (ifup=1 linkup=1)
>>> IPv4: 127.0.0.1/255.0.0.0 gateway 127.0.0.1
>>>
>>> DNS: None
>>>
>>> Default Interface: None
>>> OVMS #
>>>
>>> My laptop is connected to Revelstoke, so I know it is working.
>>>
>>> Is there some aspect of auto-start that I need now to have this work?
>>>
>>> -- Steve
>>>
>>> On Mon, 19 Mar 2018, Mark Webb-Johnson wrote:
>>>
>>>> That is not correct, at all.
>>>>
>>>> For a case where you have a wifi STA connection, but no IP address yet, you should see the 'st' network interface, but without an IP. In fact, the 'st' interface should appear as soon as you start the wifi client. What does 'wifi status' show you?
>>>>
>>>> Trying to catch mine, between STA connected and IP assigned, this is what I get:
>>>>
>>>> OVMS # wifi mode client STA
>>>> Starting WIFI as a client to STA...
>>>> I (27218) phy: phy_version: 383.0, 79a622c, Jan 30 2018, 15:38:06, 0, 0
>>>> I (27108) wifi: wifi firmware version: ebd3e5d
>>>> I (27118) wifi: config NVS flash: enabled
>>>> I (27118) wifi: config nano formating: disabled
>>>> I (27118) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
>>>> I (27128) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
>>>> I (27128) wifi: Init dynamic tx buffer num: 16
>>>> I (27128) wifi: Init data frame dynamic rx buffer num: 16
>>>> I (27138) wifi: Init management frame dynamic rx buffer num: 16
>>>> I (27138) wifi: wifi driver task: 3ffe5f94, prio:23, stack:4096
>>>> I (27138) wifi: Init static rx buffer num: 4
>>>> I (27148) wifi: Init dynamic rx buffer num: 16
>>>> I (27148) wifi: wifi power manager task: 0x3ffea128 prio: 21 stack: 2560
>>>> I (27218) wifi: mode : sta (re:da:ct:ed:da:ta)
>>>>
>>>> OVMS # network
>>>> Interface#1: st1 (ifup=0 linkup=1)
>>>> IPv4: 0.0.0.0/0.0.0.0 gateway 0.0.0.0
>>>>
>>>> Interface#0: lo0 (ifup=1 linkup=1)
>>>> IPv4: 127.0.0.1/255.0.0.0 gateway 127.0.0.1
>>>>
>>>> DNS: None
>>>>
>>>> Default Interface: None
>>>>
>>>> I (30268) wifi: n:11 0, o:1 0, ap:255 255, sta:11 0, prof:1
>>>> I (30938) wifi: state: init -> auth (b0)
>>>> I (30948) wifi: state: auth -> assoc (0)
>>>> I (30958) wifi: state: assoc -> run (10)
>>>> I (30978) wifi: connected with STA, channel 11
>>>>
>>>> OVMS # network
>>>> Interface#1: st1 (ifup=1 linkup=1)
>>>> IPv4: 0.0.0.0/0.0.0.0 gateway 0.0.0.0
>>>>
>>>> Interface#0: lo0 (ifup=1 linkup=1)
>>>> IPv4: 127.0.0.1/255.0.0.0 gateway 127.0.0.1
>>>>
>>>> DNS: None
>>>>
>>>> Default Interface: st1 (0.0.0.0/0.0.0.0 gateway 0.0.0.0)
>>>>
>>>> I (33968) wifi: pm start, type:0
>>>> I (34288) event: sta ip: x.x.x.56, mask: 255.255.255.0, gw: x.x.x.62
>>>> I (34288) netmanager: Set DNS#0 8.8.8.8
>>>> I (34298) netmanager: Set DNS#1 8.8.4.4
>>>> I (34298) netmanager: Interface priority is st1 (x.x.x.56/255.255.255.0 gateway x.x.x.62)
>>>> I (34308) time: Starting SNTP client
>>>> I (34318) ovms-mdns: Starting MDNS service
>>>> I (34318) esp32wifi: WiFi UP with SSID: STUBBY, MAC: re:da:ct:ed:da:ta, IP: x.x.x.56, mask: 255.255.255.0, gw: x.x.x.62
>>>> I (34348) webserver: Launching Web Server
>>>> I (34358) ssh: Launching SSH Server
>>>> OVMS # network
>>>> Interface#1: st1 (ifup=1 linkup=1)
>>>> IPv4: x.x.x.56/255.255.255.0 gateway x.x.x.62
>>>>
>>>> Interface#0: lo0 (ifup=1 linkup=1)
>>>> IPv4: 127.0.0.1/255.0.0.0 gateway 127.0.0.1
>>>>
>>>> DNS: 8.8.8.8 8.8.4.4
>>>>
>>>> Default Interface: st1 (x.x.x.56/255.255.255.0 gateway x.x.x.62)
>>>>
>>>> D (40248) time: ntp (stratum 1 trusted 1) provides time Mon Mar 19 01:03:25 2018 (535294us) UTC
>>>>
>>>> OVMS # wifi status
>>>> WiFi
>>>> Power: on
>>>> Mode: Client mode
>>>>
>>>> STA SSID: STUBBY
>>>> MAC: re:da:ct:ed:da:ta
>>>> IP: x.x.x.56/255.255.255.0
>>>> GW: x.x.x.62
>>>>
>>>> Regards, Mark.
>>>>
>>>>> On 19 Mar 2018, at 8:52 AM, Stephen Casner <casner at acm.org> wrote:
>>>>>
>>>>> When I start wifi client, it looks like it has acquired the link, but
>>>>> not done DHCP to get an address?
>>>>>
>>>>> -- Steve
>>>>>
>>>>> OVMS # wifi mode client Revelstoke
>>>>> Starting WIFI as a client to Revelstoke...
>>>>> I (742914) wifi: wifi firmware version: ebd3e5d
>>>>> I (742914) wifi: config NVS flash: enabled
>>>>> I (742914) wifi: config nano formating: disabled
>>>>> I (742914) wifi: Init dynamic tx buffer num: 16
>>>>> I (742914) wifi: Init data frame dynamic rx buffer num: 16
>>>>> I (742914) wifi: Init management frame dynamic rx buffer num: 16
>>>>> I (742914) wifi: wifi driver task: 3fff1044, prio:23, stack:4096
>>>>> I (742914) wifi: Init static rx buffer num: 4
>>>>> I (742914) wifi: Init dynamic rx buffer num: 16
>>>>> I (742914) wifi: wifi power manager task: 0x3ffe81d8 prio: 21 stack: 2560
>>>>> I (742924) wifi: mode : sta (30:ae:a4:37:1b:84)
>>>>> I (745344) wifi: n:1 0, o:1 0, ap:255 255, sta:1 0, prof:1
>>>>> I (745994) wifi: state: init -> auth (b0)
>>>>> I (746004) wifi: state: auth -> assoc (0)
>>>>> I (746014) wifi: state: assoc -> run (10)
>>>>> I (746054) wifi: connected with Revelstoke, channel 1
>>>>> I (749014) wifi: pm start, type:0
>>>>> OVMS # net
>>>>> Interface#0: lo0 (ifup=1 linkup=1)
>>>>> IPv4: 127.0.0.1/255.0.0.0 gateway 127.0.0.1
>>>>>
>>>>> DNS: None
>>>>>
>>>>> Default Interface: None
>>>>> OVMS #
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at lists.teslaclub.hk
>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>
>>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
More information about the OvmsDev
mailing list