| Bug: outgoing VASP connection uses wrong source ip address |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through February 20, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| zmi |
The computer the MMSC runs here on has two IP addresses. An outgoing VASP EAIF connection does not use the ip number the MMSC is bound to (as configured on the MMSC tab in the "IP Address" entry) for outgoing connections (checked via network monitor). This is a severe problem here because then the IPSEC tunnel we use for VASP connections is therefore not used (wrong source IP address) and the connections fails. | |||
| Bryce Norwood - NowSMS Support |
Agreed, that is a bug. We're working to get a new beta build together, but in the meantime, there is an updated MMSC.EXE available in the download at http://www.nowsms.com/download/mmscbeta.zip which will address this problem. -bn | |||
| ZMI |
Hi, ok, bug is gone in the service process. It is still there in the configuration interface (which wants to test outgoing VASP connection when you click ok and does not let you proceed if the test does not succeed; I entered the change in the appropriate *.ini file manually and restarted the service process). | |||
| Bryce Norwood - NowSMS Support |
Ok, I really need to put together a new beta install. To address the configuration interface, I needed to send an updated MMSCDLL.DLL. I've put together a single ZIP that contains all post-beta 2 updated files. It is available at http://www.nowsms.com/download/beta2update.zip. Please let me know for certain that it addresses this issue with the configuration interface. -bn | |||
| ZMI |
Could it be that we have the same problem with an outgoing smtp connection? | |||
| ZMI |
The SMTP problem I see is probably not related the source ip problem, but see other topic for a thorough desciption of the problem. | |||
| Bryce Norwood - NowSMS Support |
ZMI, There is indeed a similar problem with the SMTP server. It binds to any address on the PC instead of the address specified for the MMSC. (We just had another support incident reported about this being a problem.) That is unrelated to the problem described in the other thread, but it is a problem that is resolved in the latest upload of the http://www.nowsms.com/download/beta2update.zip file. -bn | |||
| ZMI |
> To address the configuration interface, I needed to send an updated MMSCDLL.DLL. I made sure, that I installed the new MMSCDLL.DLL. However, the config interface still display version b20030728 and seems to still use the wrong source ip port. The config interface seems to be smsgw.exe which is not in the beta2update zip file (although this might only explain the wrong version number). | |||
| ZMI |
Sorry, wrong alarm. I tried it a second time and this time the right source address was used in the config interface. Sorry again. | |||
| Bryce Norwood - NowSMS Support |
ZMI, Glad that this problem appears to be sorted. It is a bit confusing. We haven't had a need to update SMSGW.EXE, and it is the MMSCDLL.DLL file that handles the MMS specific property sheets. | |||
| ZMI |
The same problem (source IP address wrong) seems to be with SMPP connections for both the configuration interface and the server process. | |||
| Bryce Norwood - NowSMS Support |
Technically that setting is only supposed to apply for the MMSC. So it doesn't apply to the SMS components. I could see where the SMS components could use similar settings. And actually, for things like SMPP, it should be configurable per SMSC connection. I don't doubt that this is going to come up as a problem somewhere, but at this point, it looks like we'll most likely address it after this next release. -bn | |||
| ZMI |
Well, you can bind the web service of the SMS part also at an ip address, on the config page where also the SMPP server can be configured, so you could use the setting from there. Individually setting the source ip address for different services would be best, of course. While planning for next release, although it would be a major change, using different ip addresses for incoming mms post and retrieve connection on the one hand and incoming VASP connections on the other hand might also be useful. Regarding the SMPP connection: What logic is used in what source ip address is selected or is this selection currently left to the operating system? | |||
| Bryce Norwood - NowSMS Support |
ZMI, I agree that it would make sense to use the address specified for the SMS web server. I'm just afraid that it might break someone's existing configuration, so that's why we're hesitant to make this change so close to a major new release. Basically, in this case the source IP address is left to the operating system ... which should make an intelligent decision based upon the network interface that has the best route to the destination address. The reason that I'm hesitant to change this at present is that I know we have existing customers with VPN connections to their SMPP provider. And so far this hasn't been an issue ... I guess because the OS realises that it needs to use the VPN for that connection, and automatically picks the source IP associated with the VPN. I suspect the same would apply for an MMSC VASP connection over a VPN, which is why the current approach of binding to the MMSC address concerns me a little. I suspect in the near future we're going to have to make a change ... probably to allow the source IP to be configured for each VASP connection. -bn | |||
| ZMI |
I did some further testing and it seems, that the W2K Server OS just selects the "first" IP address as the source address and employs no further logic. I have managed to swap my IP address around so it works now for me. PS the /TYPE=WAPP feature is cool.... | |||
| Bryce Norwood - NowSMS Support |
Glad to hear you've got a solution for the immediate issue. I think the address selection depends on some other factors as well. Given two (or more IP addresses) with the same routing properties, I would expect the first to be selected. But I think other factors can also come into play. As an (admittedly not so great) example, I tried making an MM7 connection to myself (not recommended) ... and if I connected to 127.0.0.1, I noticed that the source address of the connection was reported as 127.0.0.1. If I connected to the 192.168.1.x address bound to my network card instead, the source address of the connection was reported as 192.168.1.x. I haven't tried any other more complicated tests, but since I've noticed that people with VPNs and the SMPP connections don't seem to have a problem, I assume that the routing table is somehow consulted to determine the best possible address. But given two equally good possible addresses, it makes sense that the system would always choose the first. | |||
