[opensuse-autoinstall] rules.xml and CIDR networks
Greetings, we have a lot of CIDR networks. For our /16 and /24 networks, we have no problem at all with <network> or <hostadress> matches, but how does that work for CIDR addresses? We have tried both of the following options, without success: ---------- 8< ---------- <rule> <network> <match>10.11.12.128/27</match> <!-- or <match>10.11.12.128/255.255.255.224</match> --> <match_type>exact</match_type> </network> <result> <profile>base.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> ---------- >8 ----------
From the server logs, I assume matching does not work (ie. the client is not discovered to be in that network): ---------- 8< ---------- "GET /ay/11.3/rules/rules.xml HTTP/1.1" 200 4200 "GET /ay/11.3/DEADBEEF HTTP/1.1" 404 293 "GET /ay/11.3/DEADBEE HTTP/1.1" 404 292 "GET /ay/11.3/DEADBE HTTP/1.1" 404 291 "GET /ay/11.3/DEADB HTTP/1.1" 404 290 "GET /ay/11.3/DEAD HTTP/1.1" 404 289 "GET /ay/11.3/DEA HTTP/1.1" 404 288 "GET /ay/11.3/DE HTTP/1.1" 404 287 "GET /ay/11.3/D HTTP/1.1" 404 286 "GET /ay/11.3/hexip-uppercase HTTP/1.1" 404 297 "GET /ay/11.3/hexip-lowercase HTTP/1.1" 404 297 "GET /ay/11.3/default HTTP/1.1" 404 292 ---------- >8 ----------
Is this supposed to work? Any help would be greatly appreciated. tty, 686f6c6d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Friday 01 October 2010 686f6c6d wrote:
Is this supposed to work? Any help would be greatly appreciated.
the hostaddress is simply read from the file /etc/install.inf So you can take a look what you have there but I'm afraid you have to write a custom rule for that. -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Mon, Oct 4, 2010 at 10:27, Uwe Gansert <ug@suse.de> wrote:
the hostaddress is simply read from the file /etc/install.inf
That sounds reasonable for a <hostadress> match. But how does the network match work? The file /etc/install.inf correctly contains Network: 10.11.12.128 Netmask: 255.255.255.224 so I assume the <network> matching is doing the wrong thing? Or if this is supposed not to work (because only non-CIDR networks are supported), that should at least be in the docs.
So you can take a look what you have there but I'm afraid you have to write a custom rule for that.
Will do, thank you for the pointer. (: tty, 686f6c6d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Wednesday 06 October 2010 686f6c6d wrote:
the hostaddress is simply read from the file /etc/install.inf
That sounds reasonable for a <hostadress> match. But how does the network match work?
sorry, I wanted to write network is read from the install.inf (but it's true for the hostaddress too) :)
The file /etc/install.inf correctly contains Network: 10.11.12.128 Netmask: 255.255.255.224 so I assume the <network> matching is doing the wrong thing?
You can switch to the console and check that by: /usr/lib/YaST2/bin/y2base ayast_probe ncurses during the installation -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Wed, Oct 6, 2010 at 18:19, Uwe Gansert <ug@suse.de> wrote:
on Wednesday 06 October 2010 686f6c6d wrote:
The file /etc/install.inf correctly contains Network: 10.11.12.128 Netmask: 255.255.255.224 so I assume the <network> matching is doing the wrong thing?
You can switch to the console and check that by: /usr/lib/YaST2/bin/y2base ayast_probe ncurses during the installation
Ah, thanks. Another item for my toolchain. Actually, that command only tells me about network (among other things), but not the netmask. (Which makes sense, if only the former is checked anyway.) However, with that info I could confirm that it works as follows. (This does not solve all our problems - as I cannot tell if some client from a.b.c.0 is /24, /27 or whatever -, but then at least I only have to solve the netmask issues as custom rules can this do this one with plain autoyast.) ---------- 8< ---------- <rule> <network> <!-- does not work: <match>10.11.12.128/27</match> --> <!-- does not work: <match>10.11.12.128/255.255.255.224</match> --> <match>10.11.12.128</match> <match_type>exact</match_type> </network> <result> <profile>base.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> ---------- >8 ---------- The colleague discovering the problem told me he also tried that before, but I guess a different error snuck in with that. Thanks for the quick and helpful replies! tty, 686f6c6d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Thursday 07 October 2010 686f6c6d wrote:
You can switch to the console and check that by: /usr/lib/YaST2/bin/y2base ayast_probe ncurses during the installation
Ah, thanks. Another item for my toolchain.
hint! http://ugansert.blogspot.com/2010/04/autoyast-and-its-tools.html ;) -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (2)
-
686f6c6d -
Uwe Gansert