Project

General

Profile

Actions
Copy link

Bug #2503

closed

Changing monitor IP results in "The IPv6 monitor address <IPv4 IP> can not be used with a IPv4 gateway'."

Added by Chris Buechler over 12 years ago. Updated almost 12 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Gateways
Target version:
2.1
Start date:
06/17/2012
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1
Affected Architecture:

Description

adding a monitor IP to a static IPv4 gateway results in "The IPv6 monitor address <IPv4 IP> can not be used with a IPv4 gateway'." Dynamic gateways not impacted from what I've seen.

Actions
Copy link
 #1

Updated by Chris Buechler over 12 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Seth Mos over 12 years ago

Not able to replicate just yet.

I have a static gateway on my LAN for the Cisco 1811 and I can add a monitor IP just fine on that?

[3] => Array
                (
                    [interface] => lan
                    [gateway] => 192.168.11.248
                    [name] => CISCO4
                    [weight] => 1
                    [ipprotocol] => inet
                    [interval] => 
                    [descr] => Cisco 1811
                    [monitor] => 192.168.14.33
                )

Gitsync from today. Need to look further I guess.

Added a different monitor IP on my WAN gateway entry (DHCP) and it works? Also adds the route for the monitor IP.
Changed the monitor IP on my WAN gateway entry, worked.

Actions
Copy link
 #3

Updated by Seth Mos over 12 years ago

  • Status changed from New to Feedback

Can you give me what specific case this applies too? I can't replicate it with a static IPv4 gateway.

Actions
Copy link
 #4

Updated by Chris Buechler over 12 years ago

edit a static IPv4 gateway, blank out the monitor IP, save. Edit it again, try to put in a monitor IP, and it does this.

Actions
Copy link
 #5

Updated by Seth Mos over 12 years ago

I saw room for improvement regardless, we now have a ipprotocol tag so we don't have to guess the address family. Just checked in a fix that I hope prevents the bogus message.

Actions
Copy link
 #6

Updated by Chris Buechler almost 12 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF