Re: [BLUG] how to receive my own posts on this list?

Hey Kevin, this is a gmail "feature" whereby it doesn't show you your
own posts to mailing lists "to save you time and prevent clutter". More
details here:

https://support.google.com/mail/answer/6588?hl=en

This is a common point of confusion with gmail and is a "feature" I sure
wish they would get rid of (or at least make optional).

--Rob

On 08/20/2014 12:44 AM, Kevin Hunter Kesling wrote:
> * I'm not sure if the blug-owner account is actively monitored, so I'm
> now re-sending this email to the list.
>
> Hi BLUG List,
>
> I've noted in the two threads in which I've recently participated that I
> am not receiving my own posts to this list. I prefer to receive my own
> posts because I use that as a check that the list did in fact receive my
> email. I believe I've checked the right bit:
>
> http://www.list.org/mailman-member/node23.html
>
> And, in line with this rather-outdated-but-perhaps-still-relevent
> thread, I do _not_ send include myself in the CC:
>
>
> https://mail.python.org/pipermail/mailman-users/2004-December/041340.html
>
> Does anyone have any clues why I might not be receiving my own posts?
>
> Thanks,
>
> Kevin
> _______________________________________________
> BLUG mailing list
> BLUG@bloomingtonlinux.org
> http://lists.bloomingtonlinux.org/mailman/listinfo/blug
_______________________________________________
BLUG mailing list
BLUG@bloomingtonlinux.org
http://lists.bloomingtonlinux.org/mailman/listinfo/blug

[BLUG] how to receive my own posts on this list?

* I'm not sure if the blug-owner account is actively monitored, so I'm
now re-sending this email to the list.

Hi BLUG List,

I've noted in the two threads in which I've recently participated that I
am not receiving my own posts to this list. I prefer to receive my own
posts because I use that as a check that the list did in fact receive my
email. I believe I've checked the right bit:

http://www.list.org/mailman-member/node23.html

And, in line with this rather-outdated-but-perhaps-still-relevent
thread, I do _not_ send include myself in the CC:


https://mail.python.org/pipermail/mailman-users/2004-December/041340.html

Does anyone have any clues why I might not be receiving my own posts?

Thanks,

Kevin
_______________________________________________
BLUG mailing list
BLUG@bloomingtonlinux.org
http://lists.bloomingtonlinux.org/mailman/listinfo/blug

Re: [BLUG] Xfinity, Ubuntu woes

At 1:55pm -0400 Wed, 13 Aug 2014, Lawrence Bottorff wrote:
> AFA "did something," it was the Comcast tech who "did something" on his
> end. No Comcaster has seen or touched my machine.

Then this answers the first question to within a 95% confidence level
(for me anyway): the issue is entirely with the Xfinity. Good luck
convincing the tech of that, however.

> At this point I've noticed it simply seems to be a function of time:
> I wait, say, 15 minutes . . . and it suddenly works. All the while,
> though, the connection icon is lit, saying I'm good to go. But yeah,
> wait ten, fifteen and it works. Disconnect, reconnect, works
> immediately.

As someone else suggested, this sounds like a timeout; either a process
giving up, or a process finally being started. I'm reminded of the SySV
init sequence, where each process comes up one-by-one. If there was a
network hiccup, the boot sequence could hang for 5 minutes while the
script slept waiting for issue to (never) resolve.

> Could someone suggest a wifi router that would be compatible with an
> Xfinity XB3? I tried my old Quest PK5000, but it's a DSL modem.

I suggest that almost any wireless router you pick will work as the
issue is with the Xfinity wifi, not it's ethernet. The standard setup
would be this:

Internet <--> Xfinity <--> WifiRouter <--> your machine

where the Xfinity modem and WifiRouter should talk over an ethernet cable.

If you're looking for a wireless router that's less than crap, I'd pick
one that you could flash later. You don't have to flash it, but at
least you'll have the option to. OpenWRT maintains a list that may be
helpful to you:

https://openwrt.org/
-> http://wiki.openwrt.org/toh/start

Like Mark, I'm a (proud?) owner of a WNDR3800. It works, and I don't
have to inspect it (but I generally cover my bases) to know that some
network issue is further up the line. It was ~$100 when I bought it;
not the cheapest, but a good middle-of-the-road option.

Good luck,

Kevin
_______________________________________________
BLUG mailing list
BLUG@bloomingtonlinux.org
http://lists.bloomingtonlinux.org/mailman/listinfo/blug

Re: [BLUG] Xfinity, Ubuntu woes

I second this. I have a similar model and couldn't be happier with it. Definitely a great value

> On Aug 14, 2014, at 12:30, Mark Warner <mhwarner@gmail.com> wrote:
>
>> On 08/13/2014 01:55 PM, Lawrence Bottorff wrote:
>> Could someone suggest a wifi router that would be compatible with an Xfinity XB3? I tried my old Quest PK5000, but it's a DSL modem.
>
> I recently replaced both my modem and router. Modem is a Motorola SURFboard eXtreme mdl SB6121, and the router is a Netgear WNDR3400. Both have worked very very well. Total for both was about $150.
>
> --
> Mark Warner
> MEPIS Linux
> Registered Linux User #415318
>
>
>
> _______________________________________________
> BLUG mailing list
> BLUG@bloomingtonlinux.org
> http://lists.bloomingtonlinux.org/mailman/listinfo/blug
_______________________________________________
BLUG mailing list
BLUG@bloomingtonlinux.org
http://lists.bloomingtonlinux.org/mailman/listinfo/blug

Re: [BLUG] Xfinity, Ubuntu woes

On 08/13/2014 01:55 PM, Lawrence Bottorff wrote:
>
> Could someone suggest a wifi router that would be compatible with an
> Xfinity XB3? I tried my old Quest PK5000, but it's a DSL modem.

I recently replaced both my modem and router. Modem is a Motorola
SURFboard eXtreme mdl SB6121, and the router is a Netgear WNDR3400. Both
have worked very very well. Total for both was about $150.

--
Mark Warner
MEPIS Linux
Registered Linux User #415318



_______________________________________________
BLUG mailing list
BLUG@bloomingtonlinux.org
http://lists.bloomingtonlinux.org/mailman/listinfo/blug

Re: [BLUG] Xfinity, Ubuntu woes

Yeah, I'm aware. What's the acronym... mdi-x? Medium dependent interface?

Though it's pretty much a standard feature, I've also run across devices since that was implemented which either don't manage it properly or still just don't have it. Not everything (seems like it's usually the consumer stuff) uses the internal switching, so I still keep a couple x-overs I've made just in case.

I suggest a crossover cable in this case because it should work with one whether the device automatically switches the contacts on the port or not. Hunter's right though, there's no real reason not to try it with a regular old ethernet cable.

On Aug 13, 2014 5:06 PM, Kevin Hunter Kesling <hunteke@gmail.com> wrote:

At 2:47pm -0400 Wed, 13 Aug 2014, Ryan Lee Kiser wrote:
> I presume you can connect to one of the Ethernet ports with a
> crossover cable into a wireless router and just use it as a modem.

As a friendly FYI: 10+ years ago, the term crossover cable meant that
the ethernet cable in question had the relevant input and output wires
switched from a normal ethernet cable, so that the output of port A
talked to the input of port B and vice versa.

This was necessary/convenient if you wanted to have two machines
communicate and you did not have a hub or switch available (and a second
ethernet cable).

Since ~2005, however, no special crossover cable is needed as all (to my
knowledge, anyway) ethernet cards have built-in hardware logic to
auto-negotiate which wires are input and output upon connection.  So,
when he says "crossover cable", you can translate that in your mind to
just "cable".  (Unless of course you're working with hardware older than
2005!)

Cheers,

Kevin
_______________________________________________
BLUG mailing list
BLUG@bloomingtonlinux.org
http://lists.bloomingtonlinux.org/mailman/listinfo/blug

Re: [BLUG] Xfinity, Ubuntu woes

At 2:47pm -0400 Wed, 13 Aug 2014, Ryan Lee Kiser wrote:
> I presume you can connect to one of the Ethernet ports with a
> crossover cable into a wireless router and just use it as a modem.

As a friendly FYI: 10+ years ago, the term crossover cable meant that
the ethernet cable in question had the relevant input and output wires
switched from a normal ethernet cable, so that the output of port A
talked to the input of port B and vice versa.

This was necessary/convenient if you wanted to have two machines
communicate and you did not have a hub or switch available (and a second
ethernet cable).

Since ~2005, however, no special crossover cable is needed as all (to my
knowledge, anyway) ethernet cards have built-in hardware logic to
auto-negotiate which wires are input and output upon connection. So,
when he says "crossover cable", you can translate that in your mind to
just "cable". (Unless of course you're working with hardware older than
2005!)

Cheers,

Kevin
_______________________________________________
BLUG mailing list
BLUG@bloomingtonlinux.org
http://lists.bloomingtonlinux.org/mailman/listinfo/blug