Date: Sun, 1 Apr 2012 09:54:21 -0400 From: Outback Dingo <outbackdingo@gmail.com> To: RW <rwmaillists@googlemail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Access to Time Warner cable network Message-ID: <CAKYr3zzcmgdNA2AfC5U0crqoNMz3FzK83t3j3%2Bi9VW-xp_MX0g@mail.gmail.com> In-Reply-To: <20120401143541.4d7d186f@gumby.homeunix.com> References: <4F7798D0.7000404@a1poweruser.com> <4F77A360.9080601@herveybayaustralia.com.au> <4F77A6CA.50406@a1poweruser.com> <20120401143541.4d7d186f@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 1, 2012 at 9:35 AM, RW <rwmaillists@googlemail.com> wrote: > On Sat, 31 Mar 2012 20:52:26 -0400 > Fbsd8 wrote: > >> Da Rock wrote: >> > On 04/01/12 09:52, Fbsd8 wrote: >> >> Just purchased an account on the northern Ohio Time Warner cable >> >> system. Having problem connecting to their service. Seems their >> >> dhcp server has an ip address of 10.2.0.1 which is not public >> >> routable. I know my Freebsd 8.2 box functions because it worked >> >> fine under att service which I just left for Time Warner service. >> >> MY xp laptop works fine with time warner. I can see that during >> >> the connection hand shake they first issue ip addresses >> >> 192.168.x.x then end up with real public routable ip address for >> >> dns and my ip address. Just the dhcp ip is 10.2.0.1. XP seems to >> >> handle this connection hand shake ok. > > I had a modem that did something similar, it issued a temporary private > ip address and the replaced it with a routable address. > > The difference here is that the DHCP server is in a different address > block to the DHCP server, but I'm not sure that's a problem. I think > that FreeBSD associates =A0DHCP traffic with the interface its operating > on irrespective of normal routing. > > >> > Have you got a firewall or something else blocking dhcp from >> > communicating? What does ifconfig say? >> > >> No firewall running and NIC status is "no carrier" > > This is what you get when something isn't plugged-in or turned-on. or when autonegotiation fails between to ports due to incompatibilities, ive seen it alot of times on older gear > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKYr3zzcmgdNA2AfC5U0crqoNMz3FzK83t3j3%2Bi9VW-xp_MX0g>