What's new

VLAN1 address....

  • 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!

Who_Me

Occasional Visitor
Having the VLAN1 issue with my RT-AC87 router.
I have searched the forums here along with searching the web.
So far nothing has helped me find the root cause of these messages.
This has been going on regardless of what firmware I use, Merlin or Asus.
Merlin F/W tried: .48_beta 1 and .47; ASUS: the 2 most recent builds.

I have double checked all my wired & wireless devices IP addresses.
Every thing is assigned a static IP address except 2 cell phones that are assigned a address by the router's DHCP function.
For the phones I used the 'manually assigned IP around the DHCP list'.
Turned off all unnecessary functions on our Lexmark X466de printer.
Same for our HP office jet pro 8100.
Checked the Netgear GS108T switch, NAS etc. etc.....
In the IPTV tab I have set the 'use DHCP routes' to disabled.

Doing a site scan I saw nothing that looks like a repeater.
Most listings are along the lines of ATTxxx, where xxx is a number.
I took those listings to be a router on someones DSL line.

Does VLAN1 include the wi-fi connections?
I saw on the sysinfo page that VLAN2 is the WAN port.

The funny thing is when this does happen it is mostly at the same time.
On the most recent log entry's list it is happening at 12 minutes past the hour.
And happens at hourly intervals, some times skipping a hour and up to 3 hours.

Partial log listing below>
Oct 22 05:12:45 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 05:12:46 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 05:12:47 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 05:12:48 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 05:12:49 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 06:12:44 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 06:12:45 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 06:12:46 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 06:12:47 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 06:12:48 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 06:12:49 kernel: br0: received packet on vlan1 with own address as source address
 
I'm seeing the same and no idea what is causing it. So far my LAN is working ok with PCs, Phones, Tablets, printers and TVs all connected and working over wired and wireless connections. I'm running .48 beta2 currently on a AC87U. I have not done and exhaustive review of duplicate mac addresses so that could be my problem but I doubt it.
 
Having the VLAN1 issue with my RT-AC87 router.
I have searched the forums here along with searching the web.
So far nothing has helped me find the root cause of these messages.
This has been going on regardless of what firmware I use, Merlin or Asus.
Merlin F/W tried: .48_beta 1 and .47; ASUS: the 2 most recent builds.

I have double checked all my wired & wireless devices IP addresses.
Every thing is assigned a static IP address except 2 cell phones that are assigned a address by the router's DHCP function.
For the phones I used the 'manually assigned IP around the DHCP list'.
Turned off all unnecessary functions on our Lexmark X466de printer.
Same for our HP office jet pro 8100.
Checked the Netgear GS108T switch, NAS etc. etc.....
In the IPTV tab I have set the 'use DHCP routes' to disabled.

Doing a site scan I saw nothing that looks like a repeater.
Most listings are along the lines of ATTxxx, where xxx is a number.
I took those listings to be a router on someones DSL line.

Does VLAN1 include the wi-fi connections?
I saw on the sysinfo page that VLAN2 is the WAN port.

The funny thing is when this does happen it is mostly at the same time.
On the most recent log entry's list it is happening at 12 minutes past the hour.
And happens at hourly intervals, some times skipping a hour and up to 3 hours.

Partial log listing below>
Oct 22 05:12:45 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 05:12:46 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 05:12:47 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 05:12:48 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 05:12:49 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 06:12:44 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 06:12:45 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 06:12:46 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 06:12:47 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 06:12:48 kernel: br0: received packet on vlan1 with own address as source address
Oct 22 06:12:49 kernel: br0: received packet on vlan1 with own address as source address

I found this when i did a quick search: http://forums.smallnetbuilder.com/showpost.php?p=54549&postcount=368
 
Last edited:
Is there a way to log this error with more detail?
If I knew the ip or mac address creating the error it would go a long ways to finding the problem.
Also, is there a reference guide to commands to use when logged in via telnet?
Other than the usual linux ones, cd, ls, copy etc.
(I know just enough about linux to snoop around the files in the router)
I found out br0: is a bridge connection, I wanted to know what is bridged to what.
 
After getting other errors from the router and seeing as they were not resolved either.
It was the first time these new errors were listed.
Also read on a Comcast forum that the Vlan1 issue could be a problem with Comcast's IPv6.
Although I was getting the error with IPv6 turned off.
So I swapped out the AC87U with my RT-AC66U.
Set it up and no errors so far in 14 hours of up time.
(cross fingers)
BTW- I got the AC87U because the AC66U's 2.4Ghz wi-fi just stopped working and I had to re-boot it to restore wi-fi.
Figured that after many months of use something died or was 'on the edge' of functioning.
Now to decide if I sell the AC87U on Craig's List or wait for stable firmware.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top