<div dir="ltr">Ken,<div><br></div><div>Attached are the outputs of that command you requested that I run. I&#39;m not sure why IPv6 suddenly started failing either as I verified IPv6 connectivity. Also:</div><div><br></div><div>Linux phong 3.16.0-49-generic #65~14.04.1-Ubuntu SMP Wed Sep 9 10:03:23 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux<br></div><div><div><br></div><div>root@phong:/proc/sys/net/ipv4/conf/eth0# cat rp_filter </div><div>0</div></div><div><br></div><div><div>root@phong:/proc/sys/net/ipv4/conf/all# cat rp_filter </div><div>0</div></div><div><br></div><div><br></div><div>-Zach</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 15, 2015 at 3:00 PM, Ken Keys <span dir="ltr">&lt;<a href="mailto:kkeys@caida.org" target="_blank">kkeys@caida.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    Zach,<br>
    <br>
    Could you repeat the run with the &quot;-vvv&quot; option, capture the output,
    and send it to us?<br>
    E.g.:  <tt>sudo ./spoofer -vvv &gt;spoofer.log 2&gt;&amp;1</tt><br>
    That will give us more information to help figure out what&#39;s wrong.<div><div class="h5"><br>
    <br>
    <div>On 2015-09-14 19:51, Matthew Luckie
      wrote:<br>
    </div>
    <blockquote type="cite">
      <pre>Hi Zach,

Thanks for your report.

Can you provide us the URL for your report?  Also, what operating system
and what version of spoofer were you using?

Matthew

On 09/15/15 14:17, Zach Norris wrote:
</pre>
      <blockquote type="cite">
        <pre>I&#39;m attempting to test if my ISP allows for IP spoofing. Unfortunately
I&#39;m seeing this error in the generated report, &quot;The spoofer was unable
to send spoofed headers due to an operating system restriction.&quot; 

Here is a snippet from my most recent run of spoofer:

</pre>
        <blockquote type="cite">
          <blockquote type="cite">
            <pre>Test scenario with 52 probes

Sourcing non-spoofed IPv4 validation probes: 1..2..3..4..5..6..7..
Sourcing spoofed IPv4 probes (please wait): 1..(L3)*** Warn: Unable
</pre>
          </blockquote>
        </blockquote>
        <pre>to spoof with raw ip.
(L2)*** Warn: 130.206.158.142 <a href="http://130.206.158.142" target="_blank">&lt;http://130.206.158.142&gt;</a>: No route to host
2..*** Warn: 130.206.158.142 <a href="http://130.206.158.142" target="_blank">&lt;http://130.206.158.142&gt;</a>: No route to host
3..*** Warn: 130.206.158.142 <a href="http://130.206.158.142" target="_blank">&lt;http://130.206.158.142&gt;</a>: No route to host
4..*** Warn: 130.217.77.6 <a href="http://130.217.77.6" target="_blank">&lt;http://130.217.77.6&gt;</a>: No route to host
5..*** Warn: 130.217.77.6 <a href="http://130.217.77.6" target="_blank">&lt;http://130.217.77.6&gt;</a>: No route to host
6..*** Warn: 130.217.77.6 <a href="http://130.217.77.6" target="_blank">&lt;http://130.217.77.6&gt;</a>: No route to host
7..*** Warn: 139.91.90.6 <a href="http://139.91.90.6" target="_blank">&lt;http://139.91.90.6&gt;</a>: No route to host
8..*** Warn: 139.91.90.6 <a href="http://139.91.90.6" target="_blank">&lt;http://139.91.90.6&gt;</a>: No route to host
9..*** Warn: 139.91.90.6 <a href="http://139.91.90.6" target="_blank">&lt;http://139.91.90.6&gt;</a>: No route to host
10..*** Warn: 78.41.116.2 <a href="http://78.41.116.2" target="_blank">&lt;http://78.41.116.2&gt;</a>: No route to host

...

</pre>
        <blockquote type="cite">
          <blockquote type="cite">
            <pre>Performing tracefilter [TTL: 1..*** Warn: 192.172.226.240
</pre>
          </blockquote>
        </blockquote>
        <pre><a href="http://192.172.226.240" target="_blank">&lt;http://192.172.226.240&gt;</a>: No route to host
2..*** Warn: 192.172.226.240 <a href="http://192.172.226.240" target="_blank">&lt;http://192.172.226.240&gt;</a>: No route to host
3..*** Warn: 192.172.226.240 <a href="http://192.172.226.240" target="_blank">&lt;http://192.172.226.240&gt;</a>: No route to host
4..*** Warn: 192.172.226.240 <a href="http://192.172.226.240" target="_blank">&lt;http://192.172.226.240&gt;</a>: No route to host
5..*** Warn: 192.172.226.240 <a href="http://192.172.226.240" target="_blank">&lt;http://192.172.226.240&gt;</a>: No route to host

...

I verified that I do have reverse path filter disabled on all ipv4
interfaces. I&#39;ve also disabled any source IP filtering at my router and
no longer see any dropped packets because of this. I would think that
packets should be making it, at least, to the first ISP router.

Does anyone have any suggestions? I feel as though I&#39;m not testing properly.

Thank you,
Zach


_______________________________________________
spoofer-info mailing list
<a href="mailto:spoofer-info@caida.org" target="_blank">spoofer-info@caida.org</a>
<a href="https://rommie.caida.org/mailman/listinfo/spoofer-info" target="_blank">https://rommie.caida.org/mailman/listinfo/spoofer-info</a>

</pre>
      </blockquote>
      <pre></pre>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
spoofer-info mailing list
<a href="mailto:spoofer-info@caida.org" target="_blank">spoofer-info@caida.org</a>
<a href="https://rommie.caida.org/mailman/listinfo/spoofer-info" target="_blank">https://rommie.caida.org/mailman/listinfo/spoofer-info</a>
</pre>
    </blockquote>
    <br>
    </div></div><span class="HOEnZb"><font color="#888888"><pre cols="72">-- 
Ken Keys
<a href="mailto:kkeys@caida.org" target="_blank">kkeys@caida.org</a></pre>
  </font></span></div>

</blockquote></div><br></div>