Bekijk de volledige versie : WL-500g Deluxe problem
This bug was just submitted to ASUS Support:
Hello,
I recently discover a problem with WL-500g Deluxe used with a VoIP Gateway on NAT, the problem is the modification of port numbers (tsapIdentifier) in the inbound (from public net to private net) H.225 CallProceeding. You should never find a reason to modify internal content of an IP packet coming from public network. By modifying ports you are creating a problem for your customers that are using VoIP equipment behind NAT.
Could some of your engineers give me a call so I can explain in details what are you doing wrong plus traces are available?
Well, frankly, I don't think you're getting that call because the message seems somewhat crude to me. Better kiss their asses and then kindly ask for their support.
:rolleyes:
Crude?
After leaving 3 messages on their support “hotline” and spending all day debugging, I don’t think this is crude. And if don't receive any call from them or the problem is not rectified in the next build their support will start getting more emails and calls an till it’s fixed, but I'm definitely not going to kiss their ass so they can fix problems like this one, I’m not requesting a features from them, I’m asking them to fix their bug.
I am Russian and don’t create fake smiley faces.
I am Russian and don’t create fake smiley faces.
Nice. :) Anyway, if you want for this issue to be fixed - fix it yourself. Most likely you will need yet another iptables nat module to handle this. The problem is that they're lazy as seems, and the only way is to fix this in custom firmware and then add to Known Bugs section (check FAQ), they will then probably include this fix to their builds. But your request looks like "feature request" as current code does not handle H.225 or whatever. So, most likely it would be ignored...
There no need for me to modify their firmware, the gateway firmware was modified to take care of this issue. But other ASUS customers who are using their hardware would not be able to do this and they will be affected. My point is, that ASUS did something they should never do, as to modify incoming internal content of an IP packet, or even if they decided to do that (which is not uncommon – Linksys/Netgear/D-Link does on some of their routers) they should do intelligently.
So, if you ever decide to include this fix in your custom build let me know and I will provide you with more details on what needs to be done.
The other thing is that I don’t have time to mess with their code, but the change should be trivial and easy to do. But I would never consider this as a feature request – this is definitely a BUG the way they implement it.