On 11/27/06, <b class="gmail_sendername">Marcus Williams</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 27/11/2006 15:48, Carlos Rodrigues wrote:<br>> This happens bacause the rules you have above are being applied to<br>> eth0 and not eth0:1. eth0 never sees traffic for that address and<br>> eth0:1 gets the default rules (which block everything).
<br><br>Hmmmm - I set up a alias on one of my NICs and it seemed to inherit all<br>of eth0 settings. I've got eth0:0 set up as a different IP but it lets<br>me ssh in and blocks web just like eth0. I havnt added a rule for eth0:0
<br>though.</blockquote><div><br><br>You're right.<br><br>Then, in his case, the eth0 interface must have a dst rule that includes the alias address, or no dst rule at all. Then, a rule can be added conditionally opening the required ports. Something like this:
<br><br>interface eth0 name dst "$eth0_address $eth0:1_address"<br> ...<br> server someservice accept with dst "$eth0:1_address"<br> ... <br></div><br></div>I guess this should work.<br clear="all">
<br>-- <br>Carlos Rodrigues