MAC setting ignored in PPPoE connection

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Configure WAN in PPPoE mode
2. Enter desired MAC address in "MAC Address" field
3. Save and Restart

What is the expected output? What do you see instead?

Router supposed to connect to ISP over PPPoE but it failed. On ISP side there 
were attempts to connect from incorrect MAC.

What version of the product are you using?

RT-N12B1-1.9.2.7-rtn-r3702.trx

Please provide any additional information below.

After ISP removed MAC binding, connection successfully established.

Original issue reported on code.google.com by burning....@gmail.com on 14 Jan 2012 at 12:31

[GoogleCodeExporter]

It works for me.

Sorry, we can't provide end-user support. Ask your ISP for it.

Anyway, you must provide logs & additional info (like ifconfig) for such cases.

Original comment by lly.dev on 14 Jan 2012 at 3:45

• Changed state: Invalid
• Added labels: Type-Support
• Removed labels: Type-Defect

[GoogleCodeExporter]

I don't have logs now, ISP did not provide any logs either. What I know is 
there was another router that connected successfully while RT-N12 failed. I 
entered MAC address of that router and still could not connect. When I 
contacted ISP support, they said connection attepmts were made from a different 
MAC, not the one I configured. When MAC binding was removed on ISP level, 
router successfully connected. I don't see any other explaination of this. 
Unless RT-N12's MAC got cached at ISP somehow, but since MAC address is present 
in every ethernet packet header, it's very unlikely.

Original comment by burning....@gmail.com on 14 Jan 2012 at 3:55

[GoogleCodeExporter]

Probably, you don't know where logs resides. Sorry, we are unable to provide 
training for end users, try to read wl500g.info forum.

Once again - it works for me. Either your ISP has specific issues, or you are 
doing something wrong.

Original comment by lly.dev on 14 Jan 2012 at 4:09

[GoogleCodeExporter]

I know where logs reside, I don't have access to this router right now. I don't 
understand why you are so rude.

Original comment by burning....@gmail.com on 14 Jan 2012 at 4:10

[GoogleCodeExporter]

Anyway, I'm happy it works for you. I hope by this you mean something like "I 
checked the code and did not see any possibility of this". I also hope it was 
some glitch on ISP level. I reported this issue to help improve firmware. There 
was no need for humiliation and rudeness.

Original comment by burning....@gmail.com on 14 Jan 2012 at 4:32

[GoogleCodeExporter]

Unfortunately, it is impossible to improve firmware by such bug reports without 
any detail.

Original comment by lly.dev on 14 Jan 2012 at 5:26

[GoogleCodeExporter]

I wish I could provide more, but this is all I have. And since ISP removed MAC 
binding, it's not even possible to reproduce anymore. I believed it was a bug 
because the other router could connect with no problem, I copied it's MAC into 
RT-N12 but it still could not connect, and ISP support confirmed that MAC was 
incorrect. Router's firmware was freshly installed, defaults loaded using reset 
button, only changes to configuration were made on WAN & LAN page where 
connection type was set to PPPoE, and username, password, and MAC address were 
entered. Problem gone when ISP removed MAC binding, which means there were no 
configuration errors made. It's really hard to do something wrong while 
entering MAC address into "MAC Address" field.

If you need some logs or any other info from this router in it's current state, 
I can provide whatever you need. But I cannot experiment, because a) I can only 
access it remotely, b) it's in production environment.

If you say it's impossible that MAC setting could be ignored, it's fine. Then 
it was something else, whatever it was.

Original comment by burning....@gmail.com on 14 Jan 2012 at 5:47

[GoogleCodeExporter]

could the wrong MAC be the root case?

Original comment by themiron.ru on 15 Jan 2012 at 3:03

[GoogleCodeExporter]

I thought about it. I copied MAC address from working router's WAN status page. 
Also, ISP support guy said that connection attempts were from a different MAC, 
not the one I entered. He could be wrong though.

Original comment by burning....@gmail.com on 15 Jan 2012 at 3:43