Date: Sun, 01 Apr 2012 17:29:09 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: FreeBSD <freebsd-questions@FreeBSD.org> Cc: Jerry <jerry@seibercom.net> Subject: Re: Access to Time Warner cable network Message-ID: <4F788255.9070808@FreeBSD.org> In-Reply-To: <20120401105933.4c6a9d77@scorpio> References: <4F7798D0.7000404@a1poweruser.com> <4F77A360.9080601@herveybayaustralia.com.au> <4F77A6CA.50406@a1poweruser.com> <20120401143541.4d7d186f@gumby.homeunix.com> <4F786796.5010903@FreeBSD.org> <20120401105933.4c6a9d77@scorpio>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig7969E0F52D9684EB7CF4C731
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 01/04/2012 15:59, Jerry wrote:
> Mathew, I don't know if it is as cut and dry as that. The OP claimed
That's Matthew with two t's.
> that his Microsoft PC connected properly but not his FreeBSD machine.
> That, in itself, is certainly not surprising. I have always had better
> luck setting up networks with Microsoft; however, why is it that he is
> apparently the only FreeBSD user who is exhibiting these problems? I
> suppose it is conceivable that he alone uses the northern Ohio Time
> Warner cable system. I find that rather hard, although not impossible
> to believe. Further more, is this one branch of the TW empire the only
> one using this configuration? I kind of doubt that myself. It would
> seem to me that the problem lies in the OP's configuration itself. He
> claimed it worked with "AT&T". Is it possible he has some left over
> remnants of that configuration that are causing this problem. Windows
> would not suffer that problem since it creates a new configuration for
> each new host.
You are correct in the sense that I was making general comments and not
really addressing the OP's specific problems at all. Yes, quite
probably it is user error rather than TW producing a completely
non-sensical setup. (I didn't say TW's setup wouldn't work, only that
it didn't seem to conform to the appropriate standards.)
Not knowing *anything* about how TW's cable network works, nor having
any detailed debugging information, all I can do is reiterate the old
mantra to the OP:
1) Tell us exactly what you did.
2) Tell us exactly what happened.
3) Tell us what you expected to happen.
4) Tell us why you think what happened was inconsistent with your
actions in (1).
And when I say "tell" I mean /cut'n'paste relevant bits of config files/
and /show us what the output on your screen or in your log files was/.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
--------------enig7969E0F52D9684EB7CF4C731
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk94glwACgkQ8Mjk52CukIwvDQCgiqJzJMclobzQp2KkEoZ7B3ZL
2coAnAwtrBwDOveDOx9820CnaArClv3R
=voGv
-----END PGP SIGNATURE-----
--------------enig7969E0F52D9684EB7CF4C731--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F788255.9070808>