Menu
What's new
By:
Filters Better Search

Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. C

    kernel: br0: received packet on eth1 with own address as source address

    I think this is case of there being crayons along with those toys that the child knocked onto the floor and they are leaving marks. I will try to answer my own questions. Can we locate the device causing the messages? I think still having one of the "own address" messages sneak through the...
  2. C

    kernel: br0: received packet on eth1 with own address as source address

    I keep coming back to this. Are the packets really coming from outside the router, or is Asus inserting them into the input queue? Why?
  3. C

    kernel: br0: received packet on eth1 with own address as source address

    Only one ending with .255 which is a broadcast type like 255.255.255.255 was shown with 2 same packets close in time. By my logic in the post earlier today this would indicate 2 devices that cannot see each other. By now the logging is limiting to one every 5 minutes. so we would not see...
  4. C

    kernel: br0: received packet on eth1 with own address as source address

    Since we can stop the messages with iptable rules, we have to conclude that these are real packets coming back to the router. How can they come back? What is the consequence of this? I can only think of two ways: a network loop A device is sending the packet back. I know that not...
  5. C

    kernel: br0: received packet on eth1 with own address as source address

    I forgot to say you do not need to do the logging for long..If you get 30 logs lines that should be all you need to see if TTL changes. Then you can disable the logs if you want.
  6. C

    kernel: br0: received packet on eth1 with own address as source address

    Here is the new script which gets past manually entering ipv6 addresses. It handles both the ipv4 and ipv6 rules. As it is, it will log the first 24 dropped packets and if they are happening fast, drop to only one every 5 minutes. You need to check the variables InsLoc# to see it they are...
  7. C

    kernel: br0: received packet on eth1 with own address as source address

    We only have two addresses left. Getting them would indicate a configuration problem with a computer I believe. Can you add for ipv4 the rule iptables -I INPUT 3 ! -i lo -s 127.0.0.1 -j DROP and for Ipv6 the rule ip6tables -I INPUT 1 ! -i lo -s ::1 -j DROP These are the IP addresses from the...
  8. C

    kernel: br0: received packet on eth1 with own address as source address

    I expect the fe80 on rule 3 is from the br0 interface. Also are you getting the messages any more? If not, I will generate a script to make the rules. Need to see next 3/4 rules to decide if insert point should be at 2,3 or 4 rule.
  9. C

    kernel: br0: received packet on eth1 with own address as source address

    Normally in a Ipv4 chain the first two rules are: one ending with "state INVALID" which drops packets that are just plain wrong for some reason, could be bad length, bad header, or unexpected sequence. The other ending with "state RELATED,ESTABLISHED" to accept packets continuing an existing...
  10. C

    kernel: br0: received packet on eth1 with own address as source address

    Until we conclude not possible, I think we should pursue this research. If it works, I think John will realize the consequences implied. Anyway, from the output it looks like we suppressed 509 messages with rule #4. Could you manually edit the following script to put your real Ipv6 addresses...
  11. C

    kernel: br0: received packet on eth1 with own address as source address

    First a little story... A child learns to pick up all his toys off the floor and put then away neatly. One day he is playing on the table, and his mother asks him to put his toys away. He pauses, then knocks all the toys off the table, and before mother can say anything starts to pick them up...
  12. C

    kernel: br0: received packet on eth1 with own address as source address

    having had the new rules inplace for a day now, can you give me first few lines the output of the command iptables -nvL INPUT --lin Also the output of command ifconfig Change the public IP to xxx where ever it shows. I am little busy today, will answer your questions when I can. edit: Also...
  13. C

    kernel: br0: received packet on eth1 with own address as source address

    OK, now for a quick lesson on iptables (taking this command apart). The "INPUT" means to process packets coming to the router ( not FORWARD thru the router, or OUTPUT from the router) The split -I xx 3 means to Insert this as rule #3. The ! -i lo means to not include traffic from loopback...
  14. C

    kernel: br0: received packet on eth1 with own address as source address

    Thank you John! My iptables accepts the ! in either place So this script should be #!/bin/sh set -v # set -x # kill packets from my own addresses iptables -I INPUT 3 ! -i lo -s `nvram get lan_ipaddr` -j DROP iptables -I INPUT 3 ! -i lo -s `nvram get wan_ipaddr` -j DROP #
  15. C

    kernel: br0: received packet on eth1 with own address as source address

    I just did a copy /paste of the iptables command from your post to my command line, and it worked just fine. Thinking ....
  16. C

    [Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

    Lets take this conversation over to that thread because the answer applies not only to this fork but all firmwares. If you want my help debugging that script, post your script and the output from the iptables command in step 2 from my post #12 in that thread (Post in that thread, not this...
  17. C

    Block iMessages?

    Please confirm that HW Acceleration is disabled on the tools => sysinfo page. If enabled, existing connections will not be blocked by parental controls. Edit to add: If it is enabled, go to LAN => "Switch Control" and change the "Enable HW Acceleration" to No. (I think it was also called NAT...
  18. C

    [Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

    Did you try using this information to stop the log entries? http://www.snbforums.com/threads/kernel-br0-received-packet-on-eth1-with-own-address-as-source-address.21877/#post-164283 Or did you want something simpler?
  19. C

    [Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

    The bad news is that I tested ipv6 with 6in4 with this fork's version 11 and indeed hardware acceleration is disabled on the RT-N66U, but reason is not provided on the status page. The good news is I may have found a workaround. With Hurricane Electric tunnel broker, I did the following On...
  20. C

    [Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

    What version does "this firmware" refer to in your post? I am running version 11 of this fork with IPV6 on n66u and hardware acceleration shows enabled on the tools page. Edit: Just checked and I do have the following radvd.postconf script but don't think that would affect the hardware...
Top