Project

General

Profile

Actions
Copy link

Action Item #280

closed

Need a default network config for firstboot

Added by Hammel over 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Hammel
Target version:
PiBox - 0.10.0
Start date:
02 Mar 2014
Due date:
% Done:

100%

Estimated time:
Severity:
04 - Low

Description

The system should have a default network configuration that should be accessible via wired eth. That way the device can be configured remotely via the web interface.

Actions
Copy link
 #1

Updated by Hammel over 10 years ago

  • Target version changed from 1.0 - Atreides to 0.9.0

Targeting for 0.9.0.

Actions
Copy link
 #2

Updated by Hammel over 10 years ago

  • Priority changed from Normal to Urgent
  • Severity changed from 03 - Medium to 04 - Low
Actions
Copy link
 #3

Updated by Hammel over 10 years ago

  • Priority changed from Urgent to Normal
  • Target version changed from 0.9.0 to 0.10.0
Actions
Copy link
 #4

Updated by Hammel about 10 years ago

  • Priority changed from Normal to Immediate
Actions
Copy link
 #5

Updated by Hammel about 10 years ago

  • Severity changed from 04 - Low to 02 - High
Actions
Copy link
 #6

Updated by Hammel about 10 years ago

  • Project changed from PiBox to pibox-network-config
  • Category deleted (04 - Root File System)
  • Status changed from New to In Progress
  • % Done changed from 0 to 10

There doesn't need to be a default setting. All interfaces can be disabled. The Media Server and Media Player offer a UI that allows configuration easily enough.

However, the displayed IP address should be blank if the interface is not enabled. I believe the address displayed is bogus if the interface is not enabled. The address is shown in the bottom left of the bui-network-config UI.

Actions
Copy link
 #7

Updated by Hammel about 10 years ago

  • Priority changed from Immediate to Urgent
  • % Done changed from 10 to 70
  • Severity changed from 02 - High to 04 - Low

Updates were added to showIPInStatusBar() to (hopefully) better identify if the selected interface is available and running before attempting to get its IP address. Also added more calls to showIPInStatusBar() so when changes are initiated by the program the IP is correctly updated to reflect the changes.

This may not be completely correct but its better than it was.

Pushing back to the end of the 0.10 cycle to give me time to test it more.

Actions
Copy link
 #8

Updated by Hammel almost 10 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 70 to 100

This appears to be working fine now. The correct IP address is shown for enabled interfaces and nothing is shown for disabled interfaces.

Closing issue.

Actions
Copy link

Also available in: Atom PDF