Hi,
I have some problems with this modem.
But step by step.
First of all, I don't know if it works this way at all, because windows (xp)
doesn't use the mbim-mode. The device is there, but the dialer from d-link
uses only the serial port.
The first problem is the initialisation. Despite
On Wed, Apr 20, 2016 at 10:10 AM, Aleksander Morgado
wrote:
> On Wed, Apr 20, 2016 at 7:06 PM, Joshua Deare wrote:
>> Thanks for the clarification there. I don't use NetworkManager, I've
>> had bad experiences in the past so I just use netctl for all my
On Wed, Apr 20, 2016 at 7:06 PM, Joshua Deare wrote:
> Thanks for the clarification there. I don't use NetworkManager, I've
> had bad experiences in the past so I just use netctl for all my
> things. But I found my issue. I was falling back to use the /24 net
> prefix I'm used to
On Wed, 2016-04-20 at 17:13 +0200, Andreas Fett wrote:
> Hi,
>
> any news on this one?
>
> On 03/12/15 17:54, Dan Williams wrote:
> >
> > For IPv6 MM should report "DHCP" if there is *any* information
> > missing
> > (DNS or Gateway) because that may have to be acquired via SLAAC or
> > DHCPv6.
Hi,
any news on this one?
On 03/12/15 17:54, Dan Williams wrote:
> For IPv6 MM should report "DHCP" if there is *any* information missing
> (DNS or Gateway) because that may have to be acquired via SLAAC or
> DHCPv6. MM should also fill in any information it already has, even if
> it sets DHCP
On Fri, Mar 11, 2016 at 04:10:24PM -0600, Dan Williams wrote:
> On Fri, 2016-03-11 at 19:17 +0100, Marcin Szewczyk wrote:
> > [...] I am working on a phone-like device that could make a voice
> > call and sometimes send some data over the internet. I am confused,
> > probably because most of
On Wed, Apr 20, 2016 at 6:14 AM, Joshua Deare wrote:
>
> At this point I would think everything would be okay. But when I do this:
> $ ip addr show wwp0s20f0u3i12
> 2: wwp0s20f0u3i12: mtu 1500 qdisc noop
> state DOWN group default qlen 1000
>