Bug #2503

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

Added by Chris Buechler 11 months ago. Updated 6 months ago.

Status:Resolved Start date:06/17/2012
Priority:High Due date:
Assignee:- % Done:

0%
Category:Gateways
Target version:2.1
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.

Associated revisions

Revision 2972b3e7
Added by Seth Mos 11 months ago

Now that we actually have a IP protocol tag in the config.xml we can make this check a lot simpler and do less guessing.
Redmine ticket #2503

History

#1 Updated by Chris Buechler 11 months ago

  • Description updated (diff)

#2 Updated by Seth Mos 11 months 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.

#3 Updated by Seth Mos 11 months 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.

#4 Updated by Chris Buechler 11 months 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.

#5 Updated by Seth Mos 11 months 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.

#6 Updated by Chris Buechler 6 months ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF