**** BEGIN LOGGING AT Tue Dec 15 02:59:57 2009
Dec 15 05:44:16 <zhenhua> denkenz: according to V250, 5.4.4 Parameter commands, the parameter could be read-only or read-write.
Dec 15 05:45:12 <denkenz> yeah but most of them are easy to support
Dec 15 05:45:23 <denkenz> And for echo we need to have it both ways
Dec 15 05:46:00 <zhenhua> In some cases (specified in the description of the individual parameter),
Dec 15 05:46:00 <zhenhua> the DCE may ignore attempts to set the value of such parameters rather than respond with an
Dec 15 05:46:00 <zhenhua> ERROR result code,
Dec 15 05:46:46 <denkenz> Look at Table 1 of 27.007
Dec 15 05:46:51 <denkenz> It specifies which are mandatory
Dec 15 05:47:30 <zhenhua> yes. i saw it. so first we do the mand part.
Dec 15 05:47:40 <denkenz> yep
Dec 15 06:51:27 <martin_lab> denkenz, holtmann I always can not get netmask from Settings on my f3607 card.
Dec 15 06:52:15 <martin_lab> denkenz, holtmann other entries of settings  are ok. 
Dec 15 07:29:53 <holtmann> martin_lab: The f36xx cards don't return the netmask.
Dec 15 07:30:11 <holtmann> You get IP address, gateway and two DNS servers.
Dec 15 07:30:19 <holtmann> Netmask will be 255.255.255.252 if I am not mistaken.
Dec 15 07:30:22 <martin_lab> holtmann, yes
Dec 15 07:30:42 <holtmann> Even the gateway is actually a fake.
Dec 15 07:31:42 <holtmann> You will not get a netmask for the HSO card either. However these network interfaces are actually P-t-P.
Dec 15 07:32:48 <martin_lab> holtmann, But we need to set mask at ConnMan side even it is faked. So how to decide the value if oFono does not send out?
Dec 15 07:33:22 <martin_lab> holtmann, I think even it is faked, oFono should send it out. And ConnMan should not care about it. 
Dec 15 07:33:55 <martin_lab> holtmann, From DHCP we always can get netmask value. 
Dec 15 07:36:14 <holtmann> martin_lab: I agree. In this case the atom should make one up.
Dec 15 07:36:35 <holtmann> Can you double check with running DHCP and which value we get from there.
Dec 15 07:36:46 <martin_lab> holtmann,  I am doing that
Dec 15 07:37:07 <holtmann> Since for MBM it should be always the same, we can just add it.
Dec 15 07:37:32 <holtmann> We even mention the Netmask key for Settings in the documentation.
Dec 15 07:37:50 <martin_lab> holtmann, yup
Dec 15 07:38:28 <martin_lab> 255.255.255.248
Dec 15 07:38:58 <martin_lab> I will go to try f3507
Dec 15 07:39:03 <holtmann> So just use that value.
Dec 15 07:39:29 <holtmann> The gateway address is always with an offset of 4 or so.
Dec 15 07:39:54 <martin_lab> holtmann, offset 3 ;-)
Dec 15 07:40:53 <martin_lab> holtmann, you sure it is faked and not related with the 3G service network?
Dec 15 07:41:05 <holtmann> No. It is fake.
Dec 15 07:41:14 <holtmann> 3G is point to point.
Dec 15 07:41:28 <holtmann> That MBM has a real Ethernet emulation is their problem.
Dec 15 07:41:39 <martin_lab> holtmann,  ok, I will added it to oFono.
Dec 15 07:42:03 <holtmann> Does f35xx give you the same netmask?
Dec 15 07:42:40 <martin_lab> holtmann, 5 minutes, I need to get back my card. ;-)
Dec 15 08:05:20 <martin_lab> holtmann,  f3507 give the same netmask 248, and the gateway is localhost, so that can prove netmask and gateway are all faked. ;-)
Dec 15 08:06:20 <holtmann> What do you mean with gateway is localhost. You mean 127.0.0.1
Dec 15 08:07:29 <martin_lab> holtmann, route conman  just shows the gate way is "localhost"
Dec 15 08:07:56 <holtmann> Show me netstat -nr
Dec 15 08:08:34 <holtmann> Run dhclient manually and check what it sets as gateway.
Dec 15 08:11:05 <martin_lab> ok
Dec 15 08:19:10 <martin_lab> the signal is not stable here, need try several times. ;-)
Dec 15 08:37:38 <martin_lab> holtmann, I will go out of the building to try. 
Dec 15 09:14:16 <martin_lab> holtmann, I connected in the end. 
Dec 15 09:14:42 <martin_lab> holtmann, this time, the configure is totally different. 
Dec 15 09:15:04 <martin_lab> holtmann, netmask is 255.255.255.0
Dec 15 09:19:10 <martin_lab> ip is 172.16.129.128
Dec 15 09:19:15 <martin_lab> route table is
Dec 15 09:19:46 <martin_lab> 172.16.129.130      *    255.255.255.255
Dec 15 09:20:09 <martin_lab> 172.16.129.0      * 255.255.255.0
Dec 15 09:20:49 <martin_lab> default      172.16.129.130  0.0.0.0
Dec 15 09:23:54 <martin_lab> wait for a while. it now changed to 
Dec 15 09:24:30 <martin_lab> localhost      *    255.255.255.255
Dec 15 09:24:30 <martin_lab> <martin_lab> 172.16.129.0      * 255.255.255.0
Dec 15 09:24:30 <martin_lab> <martin_lab> default      localhost  0.0.0.0
Dec 15 09:25:07 <martin_lab> resent for clear reading. ..
Dec 15 09:25:18 <martin_lab> localhost      *    255.255.255.255
Dec 15 09:25:27 <martin_lab> 172.16.129.0      * 255.255.255.0
Dec 15 09:25:37 <martin_lab> default      localhost  0.0.0.0
Dec 15 09:26:04 <martin_lab> holtmann, and still can access internet smoothly. 
Dec 15 09:28:22 <martin_lab> holtmann, read from dhclient_filter() gateway should be 172.16.129.130
Dec 15 09:29:19 <martin_lab> holtmann, now change back to right configure again. 
Dec 15 09:35:44 <martin_lab> holtmann, I reconnect again. 
Dec 15 09:36:39 <martin_lab> this time, ip is 172.16.55.226, gateway is 172.16.55.192, netmask is 255.255.255.192
Dec 15 09:37:26 <martin_lab> still may changes between localhost and real gateway ip in route table. 
Dec 15 09:39:18 <martin_lab> weird behavior. 
Dec 15 09:45:17 <martin_lab> holtmann, I will go back home and try again.  
**** BEGIN LOGGING AT Tue Dec 15 17:03:09 2009
Dec 15 17:35:25 <denkenz> holtmann: So I'm thinking of removing all the registered/lac/ci/tech stuff from DCM
Dec 15 17:35:48 <denkenz> holtmann: I've never seen it be different from netreg
Dec 15 17:35:52 <holtmann> Tech, too?
Dec 15 17:36:02 <denkenz> yeah
Dec 15 17:36:11 <denkenz> No modem reports tech on the netreg in creg
Dec 15 17:36:20 <holtmann> Can't you in theory make a GSM voice call and use UMTS for data connection?
Dec 15 17:36:39 <holtmann> Personally I am fine with removing it btw.
Dec 15 17:36:54 <holtmann> Just have them use netreg.
Dec 15 17:37:02 <denkenz> Maybe, but reporting tech for voice calls is a bit silly
Dec 15 17:37:17 <denkenz> Only something like Pulse might care
Dec 15 17:37:34 <holtmann> No. Pulse just cares about the codec.
Dec 15 17:38:28 <denkenz> codec is determined by technology
Dec 15 17:38:34 <denkenz> But it might not be 1:1 mapping
Dec 15 17:43:54 <denkenz> heh, the DoS must still be going on
Dec 16 02:01:15 <holtmann> martin_lab: Where is your patch for sending Netmask with MBM hardware?
Dec 16 02:29:07 <martin_office> holtmann, I will send it right away.      
Dec 16 02:29:14 <martin_office> I tried netmask last night through dhcp. f3607 always set 255.255.255.248,  f3507 is variable. We always use dhcp on f3507, so I think that is not a issue. 
Dec 16 02:29:53 <holtmann> Sounds fine. Just include the 255.255.255.248 in case of static IP.
Dec 16 02:30:23 <martin_office> but what puzzled is the localhost stuff. it seems kernel changed it. DHCP server always send correct gateway ip.  
Dec 16 02:30:56 <martin_office> The interesting things is that even it is set as localhost as gw. network still works fine. 
Dec 16 02:31:40 <martin_office> holtmann, any idea?
Dec 16 02:31:58 <holtmann> As I mentioned show me netstat -nr and what dhclient really returns.
**** ENDING LOGGING AT Wed Dec 16 02:59:57 2009