On Thu, Dec 08, 2011 at 09:46:06PM +0100, Roger Oberholtzer wrote:
On Thu, 2011-12-08 at 18:30 +0100, Lars Müller wrote:
If the IP address could be accessed, I guess the next step might be to register it with a dynamic DNS service so it can be know to us. Any suggestions on a DNS service?
And then the name of your mobile host gets resolved for example to 10.10.4.6 and you wonder why you can't reach it.
Use openvpn and to make the certificate handling easy use the YaST CA management tool.
This will be used rather seldom. Mainly in times of difficulty or support. I could even consider a stupid solution where the system copies a file to a known IP address that we could look at.
Instead of wasting your time with such a homegrown and very likely non working approach I would use openvpn.
OK. Here could be my chance to finally play with that. But wouldn't the 10.10.x.x. address be a problem anyway?
No. I see this with different mobile network operators. Looks like
IPv4 addresses finally get handled a bit more strict. This might also
be required by the roaming nature of the connection or other technical
reasons.
Here as an example the settings I got while I verified that I'm not
telling you a fairytale.
A call to "ip r s" shows:
default via 10.64.64.64 dev ppp0 proto static
10.64.64.64 dev ppp0 proto kernel scope link src 10.57.75.50
With "ip a s ppp0" brings:
5: ppp0: