Still IPv6 Gateway Setting Problem

Reiner030 · May 5, 2013, 8:00 PM

Hello,

when I tried to setup in our firewalls a different Monitor IP for an IPv6 gateway then the changes are not saved / I got still same monitor IP == gateway IP.

2.1-BETA1 (amd64)
built on Mon Apr 22 07:12:26 EDT 2013
FreeBSD 8.3-RELEASE-p7

and I don't see any changes in repository since then which can fix that behavior.

Thanks

jimp · May 6, 2013, 3:15 PM

It works for me on a current snapshot, but I tested it against a static gateway.

Is the IPv6 gateway you're having a problem with dynamic or static?

Reiner030 · May 7, 2013, 2:49 PM

@jimp:

It works for me on a current snapshot, but I tested it against a static gateway.

Is the IPv6 gateway you're having a problem with dynamic or static?

ISP at BCIX-a –- my gw1/2 office 1 <-> my fw1/2 office 1
WLAN brigde: AS X X WLAN Brigde internal transfer
ISP at BCIX-b --- my gw1/2 office 2 <-> my fw1/2 office 2

So I want check from my firewalls the gw office1/2 but use monitoring from ISP-a/b IP because my GWs should be online even ISP connection is down …

Ah... I see one of my gws is monitoring IP set... other once rejects my requests... I had this 2-3 month ago, too... now it still ignores my changes...

mmh, what't that... he completely switch config in diff output... WebGUI looks same as before:

Configuration diff from 5/6/13 23:46:06 to 5/7/13 15:55:11
--- /conf/backup/config-1367876766.xml 2013-05-07 15:55:10.000000000 +0200
+++ /conf/backup/config-1367934911.xml 2013-05-07 15:58:27.000000000 +0200
@@ -7981,7 +7981,8 @@
<sequence>system_information-container:col1:show,captive_portal_status-container:col1:close,cpu_graphs-container:col1:close,gateways-container:col1:show,services_status-container:col1:show,gmirror_status-container:col1:close,installed_packages-container:col1:close,openvpn-container:col1:show,interface_statistics-container:col1:close,interfaces-container:col2:show,carp_status-container:col2:show,ipsec-container:col2:close,load_balancer_status-container:col2:close,log-container:col2:close,picture-container:col2:close,rss-container:col2:close,traffic_graphs-container:col2:show,smart_status-container:col2:none,wake_on_lan-container:col2:none,dyn_dns_status-container:col2:none,thermal_sensors-container:col2:none</sequence>

 <revision>- <time>1367876766</time>
+ <time>1367934911</time>
+ 
<username>reiner.keller@192.168.45.16</username></revision> 
 <l7shaper>@@ -8164,12 +8165,13 @@

 <gateway_item><interface>opt14</interface>
- <gateway>2a01:xxxx:0:ffff::1</gateway>
- <name>PAV_ZWS8_GW_ASxxxxxx_V6</name>
+ <gateway>2a01:xxxx::1</gateway>
+ <name>PAV_JWS1_GW_ASxxxxxx_V6</name>
<weight>1</weight>
<ipprotocol>inet6</ipprotocol>
 <interval>- 
+ 
+ <monitor>2A02:xxx::2:c:1</monitor></interval></gateway_item> 
 <gateway_item><interface>opt14</interface></gateway_item></l7shaper>

mmh… seems that there is buggy config (from February only hopely )... I have this interface 4 times in my config !!!

	 <gateways><gateway_item><interface>opt1</interface>
			<gateway>192.168.4.1</gateway>
			<name>WAN_TDSLGW</name>
			<weight>1</weight>
			<ipprotocol>inet</ipprotocol>
			 <interval><descr><monitor>8.8.4.4</monitor></descr></interval></gateway_item> 
		 <gateway_item><interface>opt14</interface>
			<gateway>2a01:xxxx:0:ffff::1</gateway>
			<name>PAV_ZWS8_GW_ASxxxxxx_V6</name>
			<weight>1</weight>
			<ipprotocol>inet6</ipprotocol>
			 <interval><monitor>2A02:xxxx::2:e:1</monitor></interval></gateway_item> 
		 <gateway_item><interface>opt14</interface>
			<gateway>xx.xx.176.254</gateway>
			<name>PAV_ZWS8_GW_ASxxxxxx</name>
			<weight>1</weight>
			<ipprotocol>inet</ipprotocol>
			 <interval><monitor>xx.xx.9.129</monitor>
			 <defaultgw></defaultgw></interval></gateway_item> 
		 <gateway_item><interface>opt14</interface>
			<gateway>2a01:xxxx::1</gateway>
			<name>PAV_JWS1_GW_ASxxxxxx_V6</name>
			<weight>1</weight>
			<ipprotocol>inet6</ipprotocol>
			 <interval><monitor>2A02:xxxx::2:c:1</monitor></interval></gateway_item> 
		 <gateway_item><interface>opt14</interface>
			<gateway>2a01:xxxx::1</gateway>
			<name>PAV_JWS1_GW_ASxxxxxx_V6</name>
			<weight>1</weight>
			<ipprotocol>inet6</ipprotocol>
			 <interval><monitor>2A02:xxxx::2:e:1</monitor></interval></gateway_item> 
		 <gateway_item><interface>opt14</interface>
			<gateway>2a01:xxxx::1</gateway>
			<name>PAV_JWS1_GW_ASxxxxxx_V6</name>
			<weight>1</weight>
			<ipprotocol>inet6</ipprotocol>
			 <interval><monitor>2A02:xxxx::2:c:1</monitor></interval></gateway_item> 
		 <gateway_item><interface>opt14</interface>
			<gateway>2a01:xxxx::1</gateway>
			<name>PAV_JWS1_GW_ASxxxxxx_V6</name>
			<weight>1</weight>
			<ipprotocol>inet6</ipprotocol>
			 <interval></interval></gateway_item> 
		 <gateway_item><interface>opt14</interface>
			<gateway>xx.xx.176.1</gateway>
			<name>PAV_JWS1_GW_ASxxxxxx</name>
			<weight>1</weight>
			<ipprotocol>inet</ipprotocol>
			 <interval><monitor>xx.xx.9.121</monitor></interval></gateway_item> 
		 <gateway_group><name>Group_DSL_Primary</name>
			WAN_TDSLGW|1|opt1_vip242
			PAV_ZWS8_GW_ASxxxxxx|2|address
			PAV_JWS1_GW_ASxxxxxx|3|address
			<trigger>down</trigger></gateway_group></gateways>

but it can also an "update problem" with saving the saved data, which I got last time and today once …

I would manually edit the config and take care about it in feature...

Reiner030 · May 7, 2013, 6:59 PM

Mmh, I tried several times deleting the wrong additionally 3 IPv6 gateways in /cf/conf/config.xml without success…
Interface show wrong monitoring IP and if I change it again/ they came back :(

Running
2.1-BETA1 (amd64)
built on Mon Apr 22 07:12:26 EDT 2013
FreeBSD 8.3-RELEASE-p7

Make I changes in wrong file ? I think no because this file is every time modified if changes made in WebGUI.?

Bests

Reiner030 · May 8, 2013, 10:22 PM

so… "solved" but with open problem causing this behavior:

its not only an IPv6 problem... i had one IPv4 gateway doubled too... from yesterday.
It must be added after my post when I tried to delete the extra IPv6 entries. and made "save without changes" . :(
I could delete the additional definitions directly in webinterface... it deletes row after row and last entry was then the wanted modified entry.

Reiner030 · May 9, 2013, 2:08 AM

Here just reproduced…

2.1-BETA1 (amd64)
built on Thu May 2 00:35:52 EDT 2013
FreeBSD 8.3-RELEASE-p8

added a new GW in my virtual testing FW
deactivated Monitor IP because forgotten to check the field.

=>

                 <gateway_item><interface>opt31</interface>
                        <gateway>xx.xx.176.1</gateway>
                        <name>GW_AS_JWS1</name>
                        <weight>1</weight>
                        <ipprotocol>inet</ipprotocol>
                         <interval><monitor_disable><defaultgw></defaultgw></monitor_disable></interval></gateway_item>
                 <gateway_item><interface>opt31</interface>
                        <gateway>xx.xx.176.1</gateway>
                        <name>GW_AS_JWS1</name>
                        <weight>1</weight>
                        <ipprotocol>inet</ipprotocol>
                         <interval></interval></gateway_item>

:(

cmb · May 9, 2013, 6:21 AM

where did you add the gateway? Looks like you added one with the same settings as one you already had, which yeah that will make it difficult or impossible to change the monitor IP until you remove the duplicate gateway. That shouldn't be possible to do.

Reiner030 · May 9, 2013, 9:23 PM

thats the problem…

1 duplicated (with changing IP, Interface) one old interface to the new one
i CHANGED the settings of the new interface to "no monitoring" and it's saved again as new interface :(

(btw... in common we have an AS with 2 gateways ... and so 2 gateways on same interface for IPv4 and for IPv6)