strscrm.iohttps://strscrm.io/2018-07-31T00:00:00-05:00Quiet a Dell R5102018-07-31T00:00:00-05:00Jhydatag:strscrm.io,2018-07-31:quiet-a-dell-r510.html<h1>Dell R510 - Get Quiet!</h1>
<p>Thanks to reddit, I was finally able to exact some measure of control over the usually obnoxiously loud fans in my R510. It’s pretty simple:</p>
<div class="highlight"><pre><span></span>ipmitool -I lanplus -H <ip of drac> -U <root or admin user> -P <password for root or admin user> raw 0x30 0x30 0x01 0x00
</pre></div>
<p>That enables sending commands to control the fans.</p>
<div class="highlight"><pre><span></span>ipmitool -I lanplus -H <ip of drac> -U <root or admin user> -P <password for root or admin user> raw 0x30 0x30 0x02 0xff 0x04
</pre></div>
<p>Replace the 0x04 on the end with another number. Higher for faster fans, lower for slower fans. I use 0x04 since it keeps everything cool enough while being nearly silent. On my system the second command throws an error but it does in fact seem to work fine.</p>
<p>I also made a systemd unit file to apply on boot since the settings do not stick:</p>
<div class="highlight"><pre><span></span><span class="k">[Unit]</span>
<span class="na">Description</span><span class="o">=</span><span class="s">Set fan speed to something reasonable.</span>
<span class="k">[Service]</span>
<span class="na">Type</span><span class="o">=</span><span class="s">oneshot</span>
<span class="na">RemainAfterExit</span><span class="o">=</span><span class="s">True</span>
<span class="na">ExecStartPre</span><span class="o">=</span><span class="s">-/usr/sbin/ipmitool -I lanplus -H <drac ip> -U <username> -P <password> raw 0x30 0x30 0x01 0x00</span>
<span class="na">ExecStart</span><span class="o">=</span><span class="s">-/usr/sbin/ipmitool -I lanplus -H <drac ip> -U <username> -P <password> raw 0x30 0x30 0x02 0xff 0x04</span>
<span class="k">[Install]</span>
<span class="na">WantedBy</span><span class="o">=</span><span class="s">multi-user.target</span>
</pre></div>
<p>Edit as appropriate for your setup.</p>Network Lockout on required firmware update2016-04-13T19:00:00-05:00Jhydatag:strscrm.io,2016-04-13:network-lockout-on-required-firmware-update.html<h1><span class="caps">AT</span>&T Gigapower</h1>
<p>A quick update. After about a month of smooth sailing, I was finally punted off the network last night. It appears that a required firmware update for the Pace modem was rolled out. After undoing the bridging setup and allowing the modem to communicate freely with <span class="caps">AT</span>&T’s infrastructure for about 30 minutes, it had updated. I was able to put the bypass back in place afterwards. I’m still working on a way to keep the pace on the network but inject my packets on the bridge.</p>Bypassing Gigapower’s Provided “Modem”2016-03-02T16:00:00-06:00Jhydatag:strscrm.io,2016-03-02:bypassing-gigapowers-provided-modem.html<h1><span class="caps">AT</span>&T Gigapower</h1>
<p>I recently managed to get <span class="caps">AT</span>&T Gigapower. Google Fiber is coming to my city which suddenly means the fiber that’s been buried 200 feet from my house since 2002 became worthwhile to activate. The <span class="caps">AT</span>&T techs (yes two) were both great guys and had everything installed in a few hours. They set me up with a <a href="https://www.arris.com/products/pace-5268ac-vdsl-gateway">Pace <span class="caps">5268AC</span> Gateway</a>. Normally that wouldn’t be terrible but there’s a few problems with this thing:</p>
<ul>
<li>No bridge mode</li>
<li><span class="caps">DMZ</span>-Plus still has a firewall in front of it with a rather small nat table</li>
<li>Couldn’t use my public ip block with my own router to avoid #1 and #2</li>
</ul>
<p>I like my bits raw off the wire. Don’t touch them please. I’ll bang them myself.</p>
<p>After googling I ran across <a href="https://www.dslreports.com/forum/r26523065-Success-bypassing-the-3800HGV-B-with-a-3rd-party-VDSL2-modem">this forum posting</a> and this <a href="http://blog.0xpebbles.org/Bypassing-At-t-U-verse-hardware-NAT-table-limits">blog posting</a> describing a few methods to get around having to use a U-Verse modem. Those postings are for the <span class="caps">DSL</span> U-Verse offering but the same theory applies. I also found a post on reddit which I can’t google again where a user there had also bypassed his modem. I got a bit more information from him. Anyways enough rambling.</p>
<h1>Bypassing the modem</h1>
<p>For this you’ll need:</p>
<ul>
<li>Your favorite linux distro</li>
<li>A machine with 3 NICs in it. One for the <span class="caps">ONT</span>, one for the modem, one for your <span class="caps">LAN</span></li>
<li>The mac address of your modem. You can find this in the web interface for it.</li>
</ul>
<p>Install arch linux on the machine. Wire up your <span class="caps">ONT</span>, modem, and <span class="caps">LAN</span> interfaces. If you have a machine with a dual port intel nic and an onboard realtek or otherwise (like I have) I suggest using the realtek nic as the interface for the modem. It won’t be passing anything near gigabit speed through it.</p>
<p>I used netctl to do the configuration of the networks. Here are my configs:</p>
<p>/etc/netctl/internal-profile:</p>
<div class="highlight"><pre><span></span>Description='Private Interface'
Interface=internal
Connection=ethernet
IP='static'
Address=('192.168.1.254/24')
</pre></div>
<p>/etc/netctl/modem-profile:</p>
<div class="highlight"><pre><span></span>Description='ATT Modem Interface'
Interface=modem
Connection=ethernet
IP=NO
</pre></div>
<p>/etc/netctl/ont-profile:</p>
<div class="highlight"><pre><span></span>Description='ONT Interface'
Interface=ont
Connection=ethernet
IP=NO
</pre></div>
<p>You’ll also need to bridge the <span class="caps">ONT</span>-modem networks:</p>
<p>/etc/netctl/bridge:</p>
<div class="highlight"><pre><span></span>Description="Bridge ONT to Modem"
Interface=br-att
Connection=bridge
BindsToInterfaces=(ont modem)
IP=no
SkipForwardingDelay=yes
</pre></div>
<p>Since the modem uses 802.1x to authenticate with <span class="caps">AT</span>&T’s network the bridge needs to be tweaked to allow 802.1x traffic to pass:</p>
<div class="highlight"><pre><span></span>echo 8 > /sys/class/net/br-att/bridge/group_fwd_mask
</pre></div>
<p>Once that’s done, reboot the modem. I’d suggest doing</p>
<div class="highlight"><pre><span></span>tcpdump -vvv -ei br-att
</pre></div>
<p>This will allow you to see what <span class="caps">VLAN</span> the modem negotiates which we need in the next part. Though I’m pretty sure it’s always 0 for Gigapower customers.</p>
<p>Once that’s done we need to set up a <span class="caps">VLAN</span> on the <span class="caps">ONT</span> interface, copy the ip address from the modem and copy the modem’s mac address:</p>
<div class="highlight"><pre><span></span>ip link add link ont name ont.0 type vlan id 0
macchanger -m xx:xx:xx:xx:xx:xx ont.0
ifconfig ont.0 x.x.x.x netmask x.x.x.0
ip route add default via xx.xx.x.1
</pre></div>
<p>With that you should have internet access. I’ve been told to drop ipv4 and ipv6 traffic from crossing the bridge:</p>
<div class="highlight"><pre><span></span>ebtables -t broute -A BROUTING -i br-att -p ipv4 -j redirect --redirect-target DROP
ebtables -t broute -A BROUTING -i br-att -p ipv6 -j redirect --redirect-target DROP
ebtables -t broute -A BROUTING -i br-att -p arp -j redirect --redirect-target DROP
</pre></div>
<p>I don’t have this automated. If someone else can come up with a way to do that. That’d be great.</p>