Sorry for the delay. We are looking into the log you provided. At meanwhile
please follow the instruction in the the link below to obtain the latest image
MR4 RC1. Let me know if this solves your issue.
I will get back to you on our investigation asap.
The pppoe authenication your setting up on the SA, have you been successful in getting the device to authenicate with that information on wan 1?
I also seen alot of bonjour error messages, are you using bonjour with the SA? If not, try disabling the feature in the sa and see if that eliminates that portion of error messages.
to Deactivate "Bonjour" I need to disable "Block Multicast Packets" in "Attacks" menu ?
For the first question, 1 time, only 1 time, at my first install, SA have been successfully authenticate on this WAN.
I'm using an old but so good Thomson 510 modem/router for this line.
When router mode is on, Thomson 510 works very well, alone...
But I switched it off making it working with SA520.
To disable Bonjour, go to the network management tab and select bonjour. At this point you can disable it.
With the Thomson 510, is it still in bridge mode, a way to test this: Plug a pc directly into the Thomson 510, if you get an ip address and your able to get online, then it is not in bridge mode. If you don't get an ip address from the Thomson, then verify your authenication, Username/Password. You can use your pc and connect via pppoe and put the authenication information on your pc and see if you can connect.
If that works, then make sure the profile has the same information and reapply it on the optional wan. You can plug into wan1 and test it to see if it is hardware on the optional wan that is not allowing you to connect.
we have exactly the same issue you are describing, pppoeenable failed for optional WAN. You mentioned that you resolved this, does it work now for you? Also, I did not fully understand what you did.. is this what you did?
Sorry to bother you, but I am a bit desparate with this..
Thanks for your response,
I don't understand your question ? i tried protocol bindings to force DNS protocol using first wan port...
Problem is the same...
And I'm using public Google dns for my domain.
But I've got another big problem !!!
I bought a small DLink DSL320B to replace my old Thomson 510 (wich is not ADSL2+ compatible)....
It doesn't works with SA520... I've got kernel errors :
|Fri Sep 30 14:45:00 2011(GMT +0200)||ERROR||Kernel||ip_conntrack_in: Frag of proto 17 (hook=0) |
|Fri Sep 30 15:24:01 2011(GMT +0200)||ERROR||Kernel||*******The above log repeated 41 times ******* |
|Fri Sep 30 15:24:01 2011(GMT +0200)||ERROR||Kernel||ip_conntrack_in: Frag of proto 47 (hook=0) |
Configuration is good (bridge mode) and It works well directly on a PC...
Thanks for all.