Project

General

Profile

Actions
Copy link

Bug #9264

closed

Disabling "IPv6 over IPv4 Tunneling" breaks config

Added by Chris Collins almost 6 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
Web Interface
Target version:
2.4.4-p3
Start date:
01/09/2019
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.4_1
Affected Architecture:
amd64

Description

Steps that may possibly reproduce.

1 - enable "IPv6 over IPv4 Tunneling" and set an ip address in the "ipv4 address of tunnel peer field"
2 - save and apply
3 - disable "IPv6 over IPv4 Tunneling" and empty the "ipv4 address of tunnel peer field"

This error pops up.

"Fatal error: Uncaught Error: Cannot unset string offsets in /usr/local/www/system_advanced_network.php:112 Stack trace: #0 {main} thrown in /usr/local/www/system_advanced_network.php on line 112 PHP ERROR: Type: 1, File: /usr/local/www/system_advanced_network.php, Line: 112, Message: Uncaught Error: Cannot unset string offsets in /usr/local/www/system_advanced_network.php:112 Stack trace: #0 {main} thrown"

If page is reloaded, the box is unticked, there seems to be a value of "1" left as the "ipv4 address of tunnel field" config.

The problem is even if its successfully disabled, now changing "any" setting on that networking page will throw up the php error, so unit is damaged.

I am reporting the bug, but also a request is if there is a way to now manually fix the config. So I am not resorting to setting up the unit from scratch to clear the error.

Actions
Copy link
 #1

Updated by Chris Collins almost 6 years ago

missed step 4 which is hit save and apply again.

Actions
Copy link
 #2

Updated by Chris Collins almost 6 years ago

Raising urgency of bug, as it seems it does actually prevent toggling other settings on the networking page. Until I fix the config my settings on that page are now locked in place, unless I enable the "ip[v6 over ipv4 tunneling again".

Actions
Copy link
 #3

Updated by Chris Collins almost 6 years ago

lower urgency now.

I fixed my local config with viconfig.

The setting that got stick is 'ipvnat'

It looked like this in the config

<ipv6nat>1</ipv6nat>

I removed the 1 and its normal again.

So if you follow the steps provided it should get in that stuck state.

Actions
Copy link
 #4

Updated by Jim Pingle almost 6 years ago

  • Assignee set to Jim Pingle
  • Target version set to 48
Actions
Copy link
 #5

Updated by Jim Pingle almost 6 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #6

Updated by Anonymous almost 6 years ago

On 2.4.5.a.20190111.1435 (stock - factory default), able to reproduce the behavior.

Warning: Illegal string offset 'enable' in /usr/local/www/system_advanced_network.php on line 107 Warning: Illegal string offset 'ipaddr' in /usr/local/www/system_advanced_network.php on line 108
Actions
Copy link
 #7

Updated by Danilo Zrenjanin almost 6 years ago

Reproduced the issue on SG-5100:

2.4.4-RELEASE-p2 (amd64)
built on Wed Dec 12 14:40:29 EST 2018
FreeBSD 11.2-RELEASE-p6

and

2.4.5-DEVELOPMENT (amd64)
built on Fri Jan 11 14:35:41 EST 2019
FreeBSD 11.2-RELEASE-p8

PHP Errors:
[16-Jan-2019 17:11:55 Etc/UTC] PHP Warning:  Illegal string offset ‘enable’ in /usr/local/www/system_advanced_network.php on line 107
Actions
Copy link
 #8

Updated by Jim Pingle almost 6 years ago

  • Status changed from Feedback to Assigned
Actions
Copy link
 #9

Updated by Jim Pingle almost 6 years ago

That's a new error, not the same one. I can't reproduce that here, but I can see how it might happen. Pushed a new fix.

Actions
Copy link
 #10

Updated by Jim Pingle almost 6 years ago

  • Status changed from Assigned to Feedback
Actions
Copy link
 #11

Updated by Danilo Zrenjanin almost 6 years ago

  • Status changed from Feedback to Resolved

Tested on:

2.4.5-DEVELOPMENT (amd64)
built on Wed Feb 13 06:09:38 EST 2019
FreeBSD 11.2-RELEASE-p8

No warnings, no errors. Looks good now.

Actions
Copy link
 #12

Updated by Jim Pingle almost 6 years ago

  • Target version changed from 48 to 2.5.0
Actions
Copy link
 #13

Updated by Jim Pingle over 5 years ago

  • Target version changed from 2.5.0 to 2.4.4-p3
Actions
Copy link
 #14

Updated by Jim Pingle over 5 years ago

  • Status changed from Resolved to Feedback
Actions
Copy link
 #15

Updated by Constantine Kormashev over 5 years ago

Tried on 2.4.4-p3. I do not observe the issue.

0. set IPv6 on LAN
1. enable "IPv6 over IPv4 Tunneling" and set an ip address in the "ipv4 address of tunnel peer field"
2. save (there is not apply only save)
3. empty the "ipv4 address of tunnel peer field" and disable "IPv6 over IPv4 Tunneling" (empty and disable not vice versa, because if disable is performed, then field disappears)
4. save

Config looks fine:

Enabled

<ipv6nat>
    <enable></enable>
    <ipaddr>192.168.128.240</ipaddr>
</ipv6nat>

Disabled

<ipv6nat></ipv6nat>

Actions
Copy link
 #16

Updated by Jim Pingle over 5 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF