Dan Williams <[email protected]> writes: > On Mon, 2016-01-18 at 15:15 -0600, Glenn Washburn wrote: >> Hi All, >> >> I've had a ton of headaches getting my MC7354 on Verizon's M2M data >> network. Using NM+MM I can get the interface to come up with an IP, >> so >> it seems as though I'm connected to verizon's network. However, when >> I >> run "curl -v --interface wwan0 http://www.google.com";, I get connect >> failures. >> >> I've attached a tcpdump on the wwan0 interface, which suggests that >> google is getting the tcp syn and responding with a syn+ack as >> expected. However, the tcp syn get resent, as if somewhere up the >> stack the syn+ack gets lost. I've turned off iptables, so nothing is >> getting filtered there. >> >> Has any one any clues as to what might be going on? >> > > Bjorn, I worked with Glenn for a while on IRC last week and ran out of > ideas. Any thoughts here?
Not really. I took a look at the dump only to see what Glenn describes above. The connection is active and "working", at least from a NM+MM point of view. I cannot see any other way you can possibly receive that synack. But I have no idea why it stops there. Must be a packet filter in place somewhere, I guess. But why? Is there some extra activation step necessary to enable the use of this APN? Is there some other account setting which could make Verizon turn on a filter here? Just some wild guesses... Bjørn _______________________________________________ ModemManager-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
