Project

General

Profile

Actions
Copy link

Bug #613

closed

pncSaveHostAP() does not properly identify the interface name or write it's IP based address.

Added by Hammel almost 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Immediate
Assignee:
Hammel
Target version:
PiBox - 1.1.0 - Upgrades
Start date:
20 Mar 2018
Due date:
% Done:

100%

Estimated time:
Severity:
03 - Medium

Description

While testing Ironman pair-mode I found that pncSaveHostAP() is not properly identifying the requested interface for the AP. It also isn't properly building the AP IP from the base address.

Actions
Copy link
 #1

Updated by Hammel over 6 years ago

  • % Done changed from 0 to 30

There were some basic bugs in pncSaveHostAP() that I've fixed. But now I'm up against a new one: the code tries to update an existing interface entry. Problem is, there is no entry for the uap0 interface in /etc/network/interfaces. The fix is to add a new entry if no match is found.

There is some work required to integrate that so I'm making this note so I can do it later.

Actions
Copy link
 #2

Updated by Hammel over 6 years ago

  • Severity changed from 01 - Critical to 03 - Medium
Actions
Copy link
 #3

Updated by Hammel almost 6 years ago

  • Target version changed from 1.0 - Atreides to 1.1.0 - Upgrades
Actions
Copy link
 #4

Updated by Hammel almost 6 years ago

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

It as apparent looking at the associated commits that the last problem - adding an interface if it doesn't exist - has already been implemented. Considering that the problem was uncovered with Ironman and that system has been working well for some time I think it's safe to close this issue.

Closing issue.

Actions
Copy link

Also available in: Atom PDF