Chris's Wiki :: blog/linux/DebianInterfacesLimitation Commentshttps://utcc.utoronto.ca/~cks/space/blog/linux/DebianInterfacesLimitation?atomcommentsDWiki2007-04-16T17:27:22ZRecent comments in Chris's Wiki :: blog/linux/DebianInterfacesLimitation.By Chris Siebenmann on /blog/linux/DebianInterfacesLimitationtag:CSpace:blog/linux/DebianInterfacesLimitation:042e3512e463166d6ee057ae6bbb6face42f550dChris Siebenmann<div class="wikitext"><p>Thanks for the information; it works fine now.</p>
<p>Looking at the manpage in retrospect, this is clearly my failure to read
it completely. I had sort of assumed that <code>up</code> and <code>down</code> were run after
the interface was brought up (or down), partly from the examples in
<code>/etc/network/if-up.d</code>, but since there is both a <code>pre-up</code> and a <code>post-up</code>
option, that's clearly a silly assumption.</p>
<p>(And the description of the <code>manual</code> method even <em>says</em> that the interface
can be configured manually by means of <code>up</code> and <code>down</code>, once I read it
carefully. I think I need a refresher course on Unix manpage reading.)</p>
<p>I still think that Debian makes this harder than it should be, since I
maintain that the meaning of an <code>auto ethN</code> with no <code>iface ethN</code> should
be clear and unambiguous.</p>
</div>2007-04-16T17:27:22ZBy DanielMartin on /blog/linux/DebianInterfacesLimitationtag:CSpace:blog/linux/DebianInterfacesLimitation:86915234c12b8992be7f2b83811eaf872b52be63DanielMartin<div class="wikitext"><p>Sorry I didn't see this before.</p>
<p>Here's how you do it:</p>
<pre>
iface netB inet manual
up /sbin/ifconfig $IFACE up
down /sbin/ifconfig $IFACE down
</pre>
<p><code>manual</code> means "I'm doing <em>everything</em> myself, either later or with the up and down scripts". Everything, including the fundamental low-level bring the interface up step.</p>
</div>2007-04-15T14:51:00ZBy Chris Siebenmann on /blog/linux/DebianInterfacesLimitationtag:CSpace:blog/linux/DebianInterfacesLimitation:16e975cbc778c02cdc527e8709de550a9bd5e2bcChris Siebenmann<div class="wikitext"><p>Disconnecting the TX (especially on a gigabit cable) is somewhat more work
than we're really enthused about right now, and we'd have to remember that
that connection needs a special cable (that otherwise shows as faulty in
cable testers and so on). We might feel differently about an IDS or the
like, but this is just doing traffic accounting so that we can identify
high bandwidth users behind a NAT gateway if outside forces ask us to.</p>
</div>2007-04-12T03:25:39ZFrom 70.49.25.249 on /blog/linux/DebianInterfacesLimitationtag:CSpace:blog/linux/DebianInterfacesLimitation:25da8d92213601c442e75a1b36d1eaac464b99f4From 70.49.25.249<div class="wikitext"><p>While granting that it's stupid that Debian and derivatives don't want interfaces without IPs (I expect that's also due to their idea that if you install a server, you must want to immediately start it up), you should probably also disconnect the TX on that interface's ethernet cable. Take off and nuke the site from orbit sort of stuff. - MikeP</p>
</div>2007-04-12T02:00:42Z