On Thu, 19 Dec 2019 12:35:06 -0600
John Hasler wrote:
> Celejar writes:
> > ...the problem only occurs when tethering.
>
> I wrote:
> > Which is the only time the cellular encapsulation is being done.
>
> Celejar writes:
> > Understood. I had been responding to your point about the wifi
> >
Celejar writes:
> ...the problem only occurs when tethering.
I wrote:
> Which is the only time the cellular encapsulation is being done.
Celejar writes:
> Understood. I had been responding to your point about the wifi
> encapsulation.
You've eliminated that by demonstrating that the problem
On Wed, 18 Dec 2019 21:46:29 -0600
John Hasler wrote:
> Celejar writes:
> > ...the problem only occurs when tethering.
>
> Which is the only time the cellular encapsulation is being done.
Understood. I had been responding to your point about the wifi
encapsulation.
Celejar
Celejar writes:
> ...the problem only occurs when tethering.
Which is the only time the cellular encapsulation is being done.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
On Wed, 18 Dec 2019 13:58:38 -0600
John Hasler wrote:
> Celejar writes:
> > I assume the phone first just routes them from wifi to cellular. I'm
> > not familiar with how it then transmits them over the cellular link.
>
> It has to encapsulate them in some way for the cellular protocol.
>
> >
Celejar writes:
> I assume the phone first just routes them from wifi to cellular. I'm
> not familiar with how it then transmits them over the cellular link.
It has to encapsulate them in some way for the cellular protocol.
> Yes, but that happens with virtually all this machine's network
>
On Wed, 18 Dec 2019 07:29:08 -0600
John Hasler wrote:
> Celejar writes:
> > I'm not that familiar with the internals, but basically, the phone
> > presents a wifi access point, the computer connects to it as it would
> > to any AP, and the phone apparently routes packets to and from the
> >
On Wed, 18 Dec 2019 07:47:18 -0600
John Hasler wrote:
> Celejar writes:
> > It does work (and to automate it, I'll probably put it in e/n/i with a
> > post-up line) - I'm just looking for the "right" way to do it (and to
> > undo it on connection down, as I discussed in another message in this
>
Celejar writes:
> It does work (and to automate it, I'll probably put it in e/n/i with a
> post-up line) - I'm just looking for the "right" way to do it (and to
> undo it on connection down, as I discussed in another message in this
> thread).
I wouldn't worry about doing it the *right* way.
Celejar writes:
> I'm not that familiar with the internals, but basically, the phone
> presents a wifi access point, the computer connects to it as it would
> to any AP, and the phone apparently routes packets to and from the
> cellular network.
Yes, I know that. However, the packets are being
On Wed, 18 Dec 2019 10:59:11 - (UTC)
Curt wrote:
> On 2019-12-18, Anthony DeRobertis wrote:
> >
> > Another option might be to use Network Manager, I think its connections
> > can set a custom MTU, but I'm not 100% sure as I've never tried it.
>
> I've used tethering successfully with
On Wed, 18 Dec 2019 02:30:01 -0500
Anthony DeRobertis wrote:
> On 12/17/19 11:39 AM, Celejar wrote:
> >
> > Now I just have have to figure out the best place to configure this.
> > I'm using dhcp via /etc/network/interfaces, but the 'dhcp' method
> > doesn't seem to support manual MTU setting. I
On 2019-12-18, Anthony DeRobertis wrote:
>
> Another option might be to use Network Manager, I think its connections
> can set a custom MTU, but I'm not 100% sure as I've never tried it.
I've used tethering successfully with Network Manager but never had
occasion to alter the mtu settings.
Why
On 12/17/19 11:39 AM, Celejar wrote:
Now I just have have to figure out the best place to configure this.
I'm using dhcp via /etc/network/interfaces, but the 'dhcp' method
doesn't seem to support manual MTU setting. I could use a 'supersede
interface-mtu' line in dhclient.conf, but AFAICT,
On Tue, 17 Dec 2019 13:38:59 -0600
John Hasler wrote:
> Celejar writes:
> > ...on my normal network connection, with
> > the MTU left at the normal 1500, I have no problems.
>
> What *kind* of connection?
Verizon Fios residential. But I have used my system with dozens of
different internet
Celejar writes:
> ...on my normal network connection, with
> the MTU left at the normal 1500, I have no problems.
What *kind* of connection?
> It's only while on this particular connection via cell phone tether
> that I see problems.
The problem I experienced had to do with pppoe overhead and
On Tue, 17 Dec 2019 12:53:21 -0600
John Hasler wrote:
> tomas writes:
> > I don't know the error message by heart, but here, it seems
> > the message size is too big for your local MTU...
>
> Celejar writes:
> > Yes, I think this is pretty clear. The local wifi interface has the
> > standard
tomas writes:
> I don't know the error message by heart, but here, it seems
> the message size is too big for your local MTU...
Celejar writes:
> Yes, I think this is pretty clear. The local wifi interface has the
> standard MTU of 1500, so it rejects packets larger than that.
> With =
On Tue, 17 Dec 2019 07:15:21 +0100
wrote:
> On Mon, Dec 16, 2019 at 10:37:12PM -0500, Celejar wrote:
> > Hi,
> >
> > I have a Debian Sid system with generally working networking. Recently,
> > I experienced some strange connectivity problems with a particular
> > network connection [...]
>
>
On Mon, Dec 16, 2019 at 10:37:12PM -0500, Celejar wrote:
> Hi,
>
> I have a Debian Sid system with generally working networking. Recently,
> I experienced some strange connectivity problems with a particular
> network connection [...]
> PING 1.1.1.1 (1.1.1.1) 1492(1520) bytes of data.
> ping:
20 matches
Mail list logo
