Modify

Opened 9 years ago

Closed 6 years ago

Last modified 6 years ago

#950 closed bug (test_in_newer_version)

Restart when changing from DHCP to fixed IP

Reported by: diaz8@… Owned by:
Priority: normal Milestone:
Component: fon-network Version: 2.3.6.1 (Gari jr.)
Severity: unknown
Cc: Hardware: 2.0n (FON2300)

Description

Hi,

When i connect a 3G modem to the fonera the network setting change from Fixed IP to DHCP. I don't know if it is necessary but don't consider it a problem.

However i have to set a fixed IP to normal use when connected through my ISP router. When i do so, the fonera restart but always remains in an unstable status. Wifi doesn't work and i have to reset the fonera to make it work normally.

After reset the fonera works fine, but i think fonera should work without any manual reset when changing from DHCP to Fix IP.

Regards.

Attachments (0)

Change History (5)

comment:1 Changed 9 years ago by matthijs

  • Status changed from new to infoneeded

The first issue you describe is reported in #405.

Can you be a bit more specific about what the "unstable status" is? Is the wifi SSID not broadcasted at all? Or does connection fail? If you plug in through ethernet on the LAN port, does that work?

comment:2 Changed 9 years ago by diaz8@…

Hi,

I can connect through LAN and Public place, but Myplace doesn't work. Wifi led at the fonera is off. I'm attaching log of my computer trying to connect to My place wifi. Both wifi Public and MyPlace? are shown at Network-Manager (Ubuntu), but i will try to force a refresh to be sure it the SSID is broadcasted or not.

Regards.

Oct 26 03:09:16 cip-laptop NetworkManager?[1107]: <warn> Activation (wlan0/wireless): association took too long. Oct 26 03:09:16 cip-laptop NetworkManager?[1107]: <info> (wlan0): device state change: 5 -> 6 (reason 0) Oct 26 03:09:16 cip-laptop NetworkManager?[1107]: <warn> Activation (wlan0/wireless): asking for new secrets Oct 26 03:09:16 cip-laptop NetworkManager?[1107]: <info> (wlan0): supplicant connection state: scanning -> disconnected Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: <info> (wlan0): device state change: 6 -> 4 (reason 0) Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: <info> (wlan0): device state change: 4 -> 5 (reason 0) Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: <info> Activation (wlan0/wireless): connection 'Auto CipDDG' has security, and secrets exist. No new secrets needed. Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: <info> Config: added 'ssid' value 'CipDDG' Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: <info> Config: added 'scan_ssid' value '1' Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: <info> Config: added 'key_mgmt' value 'WPA-PSK' Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: <info> Config: added 'psk' value '<omitted>' Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: <info> Config: set interface ap_scan to 1 Oct 26 03:09:20 cip-laptop NetworkManager?[1107]: <info> (wlan0): supplicant connection state: disconnected -> scanning Oct 26 03:10:21 cip-laptop NetworkManager?[1107]: <warn> Activation (wlan0/wireless): association took too long.

comment:3 Changed 9 years ago by matthijs

  • Milestone set to Firmware 2.3
  • Status changed from infoneeded to investigate

I'll try to reproduce this when I flash my 2.0n with the stable firmware again (it's running experimental firmware right now).

comment:4 Changed 6 years ago by matthijs

  • Resolution set to test_in_newer_version
  • Status changed from investigate to closed

As part of the upcoming 2.3.7.0 firmware release, we're reviewing old open tickets to see if they are still relevant, which is why you get this response now.

If this issue still occurs with the 2.3.7.0 rc2 firmware, feel free to leave a comment here so we can further investigate.

comment:5 Changed 6 years ago by matthijs

  • Milestone Firmware 2.3 deleted

Add Comment

Modify Ticket

Action
as closed The ticket will remain with no owner.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.