2009/9/2 Rémi Denis-Courmont <r...@remlab.net>: >> personally I don't care who finally sets the IP for the interface. It >> really just makes no difference. What problem do you see if oFono would >> set the IP address on that newly created interface that is up and >> running now? > > Then the application cannot influence the way it's done. That's the whole > point. Maybe I want to migrate the interface in a new namespace. For that, > it must (1) create the interface, (2) migrate it, (3) configure it, in that > order. So Ofono cannot do (3) if it cannot do (2), and it certainly should > not do (2) by itself. So it has to stick to (1).
And this generally applies to services that operators have decided to run behind a dedicated APN, such as WAP, MMS, Push over Cellular (PoC) and others. For example, Elisa in Finland seems to be running their MMSC behind an "mms" APN, with public IP address space, but firewalled from the rest of the Internet. oFono should isolate such an access from the rest of the system, since only the MMS client would know how to work with it properly. Cheers, Aki _______________________________________________ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
