Re: Access to Time Warner cable network
On 1 Apr 2012 at 10:21, Erich Dollansky wrote: Hi, On Sunday 01 April 2012 08:57:00 Da Rock wrote: Did they come to your location and run a test to their equipment? My neighbor had a recent cable outage of an existing cable on our block that was too low and a moving van hit it. Apparently the Windows system works, so I'd assume all that side is ok- just FBSD box is the issue. so, there is some difference. The questions are there to find out what the difference might be. Erich fbsd8 How do you connect to your TW ISP? Just a Cable modem of some sort, or is there a Router involved somewhere? It makes a whole world of difference I.e. How Physically do you hook together, in each instance, for the XP box, and F'BSD box. Regards. Dave B. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On 1 Apr 2012 at 19:05, Jerry wrote: On Mon, 02 Apr 2012 08:50:42 +1000 Da Rock articulated: Given that the other tech in question asked me to help him, and he is a Winblows nut like yourself, I think this premise can be dismissed out of hand. I won't even bother to qualify the rest, I wouldn't want to ruin your delusion. No delusion here. You have confirmed what I suspected. A classic case of The blind leading the blind. If one idiot can screw something up, just think what two idiots can accomplish? -- Jerry Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ In the world of the blind, the one eyed bloke is promoted to near god like status! Dave B. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On Mon, 02 Apr 2012 15:18:19 +0100 Dave wrote: fbsd8 How do you connect to your TW ISP? Just a Cable modem of some sort, or is there a Router involved somewhere? It makes a whole world of difference If you read the rest of the thread you'll see that that the problem was solved yesterday. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On Apr 2, 2012, at 7:32 AM, Dave d...@g8kbv.demon.co.uk wrote: On 1 Apr 2012 at 19:05, Jerry wrote: On Mon, 02 Apr 2012 08:50:42 +1000 Da Rock articulated: Given that the other tech in question asked me to help him, and he is a Winblows nut like yourself, I think this premise can be dismissed out of hand. I won't even bother to qualify the rest, I wouldn't want to ruin your delusion. No delusion here. You have confirmed what I suspected. A classic case of The blind leading the blind. If one idiot can screw something up, just think what two idiots can accomplish? -- Jerry Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ In the world of the blind, the one eyed bloke is promoted to near god like status! Dave Does all this smugness actually seem useful to all of you, or is one factor behind the precipitous drop in FreeBSD community size how much y'all love the sound of your own voices?!___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On 04/01/12 14:06, Outback Dingo wrote: On Sat, Mar 31, 2012 at 11:21 PM, Erich Dollansky erichfreebsdl...@ovitrap.com wrote: Hi, On Sunday 01 April 2012 08:57:00 Da Rock wrote: Did they come to your location and run a test to their equipment? My neighbor had a recent cable outage of an existing cable on our block that was too low and a moving van hit it. Apparently the Windows system works, so I'd assume all that side is ok- just FBSD box is the issue. so, there is some difference. The questions are there to find out what the difference might be. Erich to me it sounds like a link negotiation problem between the network interfaces, and auto-sensing not being able to sync you might need to set the interface on the bsd box manually to see if you can even establish link, once link is up dhcp should function Exactly. But right now we can only speculate the connection type without ifconfig- it may provide some clues as to what it is supposed to be connecting to, and what settings may actually help. rc settings may enlighten further as well. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
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 DHCP 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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On Sun, 1 Apr 2012 14:35:41 +0100 RW wrote: The difference here is that the DHCP server is in a different address block to the DHCP server, That should be: the temporary address is in a different address block to the DHCP server ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On Sun, Apr 1, 2012 at 9:35 AM, RW rwmailli...@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 DHCP 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-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On 01/04/2012 14:35, RW wrote: I had a modem that did something similar, it issued a temporary private ip address and the replaced it with a routable address. It's fairly sad that they don't use the officially mandated[*] 169.254.0.0/16 netblock which is what DHCP clients/servers are supposed to use when they need to temporarily grab an 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 DHCP traffic with the interface its operating on irrespective of normal routing. Huh? One of those servers should be a client perhaps? Yes. Contacting a DHCP server is done using Ethernet protocols (at least initially.[+]) Not using IP. That means DHCP client and server have to be on the same ethernet segment, or there should be a DHCP-relay on any routers between the client and server. If that fails, then the client can assign itself a link-local address and try that, but it is pretty uncommon in the wild. While you can run multiple different IP networks over the same physical ethernet segment, and so have DHCP servers that dish out addresses on networks distinct from any they have configured on their own interfaces, you're more likely to run into this sort of scenario if there are some DHCP relays in the picture. Cheers, Matthew [*] RFC 5735 [+] Well, also except for IPv6 -- DHCP6 just uses the auto link-local addresses which are pretty much always configured on any IPv6 capable interface. -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Access to Time Warner cable network
On Sun, 01 Apr 2012 15:35:02 +0100 Matthew Seaman articulated: On 01/04/2012 14:35, RW wrote: I had a modem that did something similar, it issued a temporary private ip address and the replaced it with a routable address. It's fairly sad that they don't use the officially mandated[*] 169.254.0.0/16 netblock which is what DHCP clients/servers are supposed to use when they need to temporarily grab an 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 DHCP traffic with the interface its operating on irrespective of normal routing. Huh? One of those servers should be a client perhaps? Yes. Contacting a DHCP server is done using Ethernet protocols (at least initially.[+]) Not using IP. That means DHCP client and server have to be on the same ethernet segment, or there should be a DHCP-relay on any routers between the client and server. If that fails, then the client can assign itself a link-local address and try that, but it is pretty uncommon in the wild. While you can run multiple different IP networks over the same physical ethernet segment, and so have DHCP servers that dish out addresses on networks distinct from any they have configured on their own interfaces, you're more likely to run into this sort of scenario if there are some DHCP relays in the picture. Cheers, Matthew [*] RFC 5735 [+] Well, also except for IPv6 -- DHCP6 just uses the auto link-local addresses which are pretty much always configured on any IPv6 capable interface. Mathew, I don't know if it is as cut and dry as that. The OP claimed 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 ATT. 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. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On 04/02/12 00:59, Jerry wrote: On Sun, 01 Apr 2012 15:35:02 +0100 Matthew Seaman articulated: On 01/04/2012 14:35, RW wrote: I had a modem that did something similar, it issued a temporary private ip address and the replaced it with a routable address. It's fairly sad that they don't use the officially mandated[*] 169.254.0.0/16 netblock which is what DHCP clients/servers are supposed to use when they need to temporarily grab an 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 DHCP traffic with the interface its operating on irrespective of normal routing. Huh? One of those servers should be a client perhaps? Yes. Contacting a DHCP server is done using Ethernet protocols (at least initially.[+]) Not using IP. That means DHCP client and server have to be on the same ethernet segment, or there should be a DHCP-relay on any routers between the client and server. If that fails, then the client can assign itself a link-local address and try that, but it is pretty uncommon in the wild. While you can run multiple different IP networks over the same physical ethernet segment, and so have DHCP servers that dish out addresses on networks distinct from any they have configured on their own interfaces, you're more likely to run into this sort of scenario if there are some DHCP relays in the picture. Cheers, Matthew [*] RFC 5735 [+] Well, also except for IPv6 -- DHCP6 just uses the auto link-local addresses which are pretty much always configured on any IPv6 capable interface. Mathew, I don't know if it is as cut and dry as that. The OP claimed 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 ATT. 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. Until it loses that configuration and you're expected to delete it and re-enter the connection details... Explain why it would be so hard to configure various functions as file sharing and some of the more 'new' features for networking on Windows then? A fellow IT colleague and I could not figure it out for the life of us on the newer versions while it worked perfectly on the old '95, '98, NT, 2k, XP systems. So no, Windows does not make networking easier- in fact it has just about completely taken the guts out of networking to abstract it from the user, making it nearly impossible for a networking expert to configure. I digress. In this case we're all only speculating as the OP hasn't provided more detail, but it could be as simple as an unplugged cable :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
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 ATT. 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 -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Access to Time Warner cable network
On Mon, 02 Apr 2012 01:27:36 +1000 Da Rock articulated: Until it loses that configuration and you're expected to delete it and re-enter the connection details... Or until elephants fly, or whatever. Explain why it would be so hard to configure various functions as file sharing and some of the more 'new' features for networking on Windows then? A fellow IT colleague and I could not figure it out for the life of us on the newer versions while it worked perfectly on the old '95, '98, NT, 2k, XP systems. So no, Windows does not make networking easier- in fact it has just about completely taken the guts out of networking to abstract it from the user, making it nearly impossible for a networking expert to configure. Just because an individual has a PHD does not make him an expert, in fact it could stand for Pin Headed Dope. Everyone is an expert in something, just ask them. The fact that you were not smart enough to complete the task means nothing. If we were to use your reasoning, then if a single person could not configure networking in FreeBSD then FreeBSD networking sucks. That is just using your rational. I digress. In this case we're all only speculating as the OP hasn't provided more detail, but it could be as simple as an unplugged cable :) I am willing to bet that this will come down to a simple PEBKAC scenario. I am assuming that the user has his cable connection enter his home, and then connecting to a company Router/Modem. I would like to know if the OP had checked out what IP's were being assigned to his boxes by that unit. I recently ran into a case where a user had a static IP assigned to a wireless printer. When he changed printers he could not get it to print because it was not being assigned the same IP as the old unit because he had failed to enter the new MAC address for the newer printer. A simple problem that took a few hours before it dawned on him what the problem was. Actually, Windows did find the printer, CUPS couldn't. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Pryor's Observation: How long you live has nothing to do with how long you are going to be dead. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
Well here is the results of my attempts to connect to Time Warner cable network. After 4 calls to their call center which was in the Philippines where all the people just read a scripted answer FAQ and only had the ability to remotely reset the modem. I finally requested to talk to the top support level in the USA. Finally got a tech support person who knew something about how their network was configured. Their modems at power up time run a script that is really a private LAN using 192.168.x.x to auto verify the cable modem mac address against a table of authorized accounts. At the conclusion the 10.2.0.1 dhcp server issues a real routable ip address along with the routable 2 dns ip address. Now this long duration hand shake takes about 40 seconds and on a windows system, windows keeps looping through the ip and dns acquire code until it succeeds. Now on freebsd the ifconfig_fxp0=DHCP seems to only cycle a single time and results in a no carrier status in the boot up msg log. After the Freebsd 8.2 boot process completed and I saw no carrier status i issued /etc/rc.d/netif restart command which resulted in the same status. This is when I posted to the questions list for help. It was after the post that I had my conversation with the level 3 tech support guy and learned about the long hand shake process. I next tried issuing (ifconfig fxp0 up) after the freebsd boot process completed and to my surprise I had a public routable ip address. So I have to find a way during the boot process to give the ifconfig_fxp0=DHCP statement in the /etc/rc.conf some delay time. But I think Freebsd 9.0 has an built in up process in its boot up process that may solve this problem. Another thing I learned from the level 3 support guy is that the cable modem has to be reset by unplugging it's power if I want to move the output cable to a different device, such as from the window box to the freebsd box or to a router. The bottom line is I have things working now and there was nothing wrong with either my window box or my freebsd box. Its just the Time Warner cable modem box and the non-standard way it's configured. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On Sun, 01 Apr 2012 14:10:52 -0400 Fbsd8 articulated: Well here is the results of my attempts to connect to Time Warner cable network. After 4 calls to their call center which was in the Philippines where all the people just read a scripted answer FAQ and only had the ability to remotely reset the modem. I finally requested to talk to the top support level in the USA. Finally got a tech support person who knew something about how their network was configured. Their modems at power up time run a script that is really a private LAN using 192.168.x.x to auto verify the cable modem mac address against a table of authorized accounts. At the conclusion the 10.2.0.1 dhcp server issues a real routable ip address along with the routable 2 dns ip address. Now this long duration hand shake takes about 40 seconds and on a windows system, windows keeps looping through the ip and dns acquire code until it succeeds. Now on freebsd the ifconfig_fxp0=DHCP seems to only cycle a single time and results in a no carrier status in the boot up msg log. After the Freebsd 8.2 boot process completed and I saw no carrier status i issued /etc/rc.d/netif restart command which resulted in the same status. This is when I posted to the questions list for help. It was after the post that I had my conversation with the level 3 tech support guy and learned about the long hand shake process. I next tried issuing (ifconfig fxp0 up) after the freebsd boot process completed and to my surprise I had a public routable ip address. So I have to find a way during the boot process to give the ifconfig_fxp0=DHCP statement in the /etc/rc.conf some delay time. But I think Freebsd 9.0 has an built in up process in its boot up process that may solve this problem. Another thing I learned from the level 3 support guy is that the cable modem has to be reset by unplugging it's power if I want to move the output cable to a different device, such as from the window box to the freebsd box or to a router. The bottom line is I have things working now and there was nothing wrong with either my window box or my freebsd box. Its just the Time Warner cable modem box and the non-standard way it's configured. I have TW with an ARRIS model: TM602G/115 cable modem. I assume you have a battery backup in your unit. If so, you have to remove the battery before resetting the unit to insure it is actually cleared. Have your tried accessing your modem via http? Usually 192.168.1.0 or 192.168.1.1 will work. Give your stations static addresses and see if that makes life easier. By the way, while I don't know what modem you have, mine can accommodate multiple units simultaneously. I don't know why you have to reset it to use a different device. Are you connected via Ethernet or wireless. Even Ethernet should allow a minimum of four unique connections. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On 04/02/12 02:29, Jerry wrote: On Mon, 02 Apr 2012 01:27:36 +1000 Da Rock articulated: Until it loses that configuration and you're expected to delete it and re-enter the connection details... Or until elephants fly, or whatever. No. This is the common mantra for any Windows net technician. Explain why it would be so hard to configure various functions as file sharing and some of the more 'new' features for networking on Windows then? A fellow IT colleague and I could not figure it out for the life of us on the newer versions while it worked perfectly on the old '95, '98, NT, 2k, XP systems. So no, Windows does not make networking easier- in fact it has just about completely taken the guts out of networking to abstract it from the user, making it nearly impossible for a networking expert to configure. Just because an individual has a PHD does not make him an expert, in fact it could stand for Pin Headed Dope. Everyone is an expert in something, just ask them. The fact that you were not smart enough to complete the task means nothing. If we were to use your reasoning, then if a single person could not configure networking in FreeBSD then FreeBSD networking sucks. That is just using your rational. Both networking in FreeBSD _and_ Winblows can be difficult at times. My point is that Winblows is not some magical fairy that can make everything better. It doesn't. It quite often gets it wrong, and when it does its a b**ch to fix- especially now with the newer versions; it just just gets harder and harder to fix. And (forget your phd) considering both myself and the other tech have _Microsoft_ certs and I topped in networking in that same certification thats saying something, do you think? I digress. In this case we're all only speculating as the OP hasn't provided more detail, but it could be as simple as an unplugged cable :) [...] I recently ran into a case where a user had a static IP assigned to a wireless printer. When he changed printers he could not get it to print because it was not being assigned the same IP as the old unit because he had failed to enter the new MAC address for the newer printer. A simple problem that took a few hours before it dawned on him what the problem was. Actually, Windows did find the printer, CUPS couldn't. Again with the magical fairy? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On 04/02/12 04:10, Fbsd8 wrote: Well here is the results of my attempts to connect to Time Warner cable network. After 4 calls to their call center which was in the Philippines where all the people just read a scripted answer FAQ and only had the ability to remotely reset the modem. I finally requested to talk to the top support level in the USA. Finally got a tech support person who knew something about how their network was configured. Their modems at power up time run a script that is really a private LAN using 192.168.x.x to auto verify the cable modem mac address against a table of authorized accounts. At the conclusion the 10.2.0.1 dhcp server issues a real routable ip address along with the routable 2 dns ip address. Now this long duration hand shake takes about 40 seconds and on a windows system, windows keeps looping through the ip and dns acquire code until it succeeds. Now on freebsd the ifconfig_fxp0=DHCP seems to only cycle a single time and results in a no carrier status in the boot up msg log. After the Freebsd 8.2 boot process completed and I saw no carrier status i issued /etc/rc.d/netif restart command which resulted in the same status. This is when I posted to the questions list for help. It was after the post that I had my conversation with the level 3 tech support guy and learned about the long hand shake process. I next tried issuing (ifconfig fxp0 up) after the freebsd boot process completed and to my surprise I had a public routable ip address. So I have to find a way during the boot process to give the ifconfig_fxp0=DHCP statement in the /etc/rc.conf some delay time. But I think Freebsd 9.0 has an built in up process in its boot up process that may solve this problem. Another thing I learned from the level 3 support guy is that the cable modem has to be reset by unplugging it's power if I want to move the output cable to a different device, such as from the window box to the freebsd box or to a router. The bottom line is I have things working now and there was nothing wrong with either my window box or my freebsd box. Its just the Time Warner cable modem box and the non-standard way it's configured. I had my suspicions, but I had no way to actually know. Cable modems work the same here: they become 'attached' to a given mac address and have to be reset when moved to a new device. Best to use a router to save that one. Simply unplugging and plugging in the cable should have told FBSD to reconfigure that network. Providing more complete information to the list for help may have given you the solution sooner. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On Mon, 02 Apr 2012 08:20:02 +1000 Da Rock articulated: Both networking in FreeBSD _and_ Winblows can be difficult at times. My point is that Winblows is not some magical fairy that can make everything better. It doesn't. It quite often gets it wrong, and when it does its a b**ch to fix- especially now with the newer versions; it just just gets harder and harder to fix. And (forget your phd) considering both myself and the other tech have _Microsoft_ certs and I topped in networking in that same certification thats saying something, do you think? A degree != practical knowledge. The only thing you are telling me is that you are a failure with no practical knowledge of what you are doing. You display an obvious disdain for the OS, so how can you even pretend to be objective? That is like me going on a jury with a predisposed hated of the defendant. Guess how that is going to turn out. It is like me putting together model planes. I hate model planes and end up destroying them and conversely blaming the destruction on the planes. It is exactly what you are doing. You obviously are a failure at networking in a Microsoft environment, so go back to whatever it is that you are semi capable of doing, which will also save your employer monies spent on time wasted. Unless of course this happens to be your own unit, in which case run down the block and find a 12 year old and have him/her fix it for you. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On 04/02/12 08:41, Jerry wrote: On Mon, 02 Apr 2012 08:20:02 +1000 Da Rock articulated: Both networking in FreeBSD _and_ Winblows can be difficult at times. My point is that Winblows is not some magical fairy that can make everything better. It doesn't. It quite often gets it wrong, and when it does its a b**ch to fix- especially now with the newer versions; it just just gets harder and harder to fix. And (forget your phd) considering both myself and the other tech have _Microsoft_ certs and I topped in networking in that same certification thats saying something, do you think? A degree != practical knowledge. The only thing you are telling me is that you are a failure with no practical knowledge of what you are doing. You display an obvious disdain for the OS, so how can you even pretend to be objective? That is like me going on a jury with a predisposed hated of the defendant. Guess how that is going to turn out. It is like me putting together model planes. I hate model planes and end up destroying them and conversely blaming the destruction on the planes. It is exactly what you are doing. You obviously are a failure at networking in a Microsoft environment, so go back to whatever it is that you are semi capable of doing, which will also save your employer monies spent on time wasted. Unless of course this happens to be your own unit, in which case run down the block and find a 12 year old and have him/her fix it for you. Given that the other tech in question asked me to help him, and he is a Winblows nut like yourself, I think this premise can be dismissed out of hand. I won't even bother to qualify the rest, I wouldn't want to ruin your delusion. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On Mon, 02 Apr 2012 08:50:42 +1000 Da Rock articulated: Given that the other tech in question asked me to help him, and he is a Winblows nut like yourself, I think this premise can be dismissed out of hand. I won't even bother to qualify the rest, I wouldn't want to ruin your delusion. No delusion here. You have confirmed what I suspected. A classic case of The blind leading the blind. If one idiot can screw something up, just think what two idiots can accomplish? -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Access to Time Warner cable network
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. Does any one have any suggestions on how to get Freebsd 8.2 working under TW? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
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. Does any one have any suggestions on how to get Freebsd 8.2 working under TW? Have you got a firewall or something else blocking dhcp from communicating? What does ifconfig say? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
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. Does any one have any suggestions on how to get Freebsd 8.2 working under TW? 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On 04/01/12 10:52, 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. Does any one have any suggestions on how to get Freebsd 8.2 working under TW? 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 Actually I asked what the output of ifconfig was, but it looks like your cable is not connected (or wifi- hard to tell without output. It preempts many questions). Try `ifconfig NIC up`, check the cable, etc. FreeBSD should be responding just like Winblows here, but your network isn't connected for whatever reason that will probably be clearer when we know what ifconfig looks like. Hence dhcp will not work in these circumstances, at least until you connect your network... :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
Da Rock wrote: On 04/01/12 10:52, 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. Does any one have any suggestions on how to get Freebsd 8.2 working under TW? 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 Actually I asked what the output of ifconfig was, but it looks like your cable is not connected (or wifi- hard to tell without output. It preempts many questions). Try `ifconfig NIC up`, check the cable, etc. FreeBSD should be responding just like Winblows here, but your network isn't connected for whatever reason that will probably be clearer when we know what ifconfig looks like. Hence dhcp will not work in these circumstances, at least until you connect your network... :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Aloha, Make sure your connection to Road Runner or TW is set for DHCP. And make sure you can ping your NIC card and like Da Rock says see whats up with iconfig. If there is a switch on the line make sure it is plugged in. I have one customer I work for that lost his signal from TW Roadrunner and they had to come out to replace some link to a failed splitter on the house connection. Here in Hawaii we have a bad corrosion problem from the salt air. TW also needs the electric service to work here as well. Did they come to your location and run a test to their equipment? My neighbor had a recent cable outage of an existing cable on our block that was too low and a moving van hit it. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + email: n...@hdk5.net All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On 04/01/12 11:22, Al Plant wrote: Da Rock wrote: On 04/01/12 10:52, 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. Does any one have any suggestions on how to get Freebsd 8.2 working under TW? 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 Actually I asked what the output of ifconfig was, but it looks like your cable is not connected (or wifi- hard to tell without output. It preempts many questions). Try `ifconfig NIC up`, check the cable, etc. FreeBSD should be responding just like Winblows here, but your network isn't connected for whatever reason that will probably be clearer when we know what ifconfig looks like. Hence dhcp will not work in these circumstances, at least until you connect your network... :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Aloha, Make sure your connection to Road Runner or TW is set for DHCP. And make sure you can ping your NIC card and like Da Rock says see whats up with iconfig. If there is a switch on the line make sure it is plugged in. I have one customer I work for that lost his signal from TW Roadrunner and they had to come out to replace some link to a failed splitter on the house connection. Here in Hawaii we have a bad corrosion problem from the salt air. TW also needs the electric service to work here as well. Did they come to your location and run a test to their equipment? My neighbor had a recent cable outage of an existing cable on our block that was too low and a moving van hit it. Apparently the Windows system works, so I'd assume all that side is ok- just FBSD box is the issue. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
Hi, On Sunday 01 April 2012 06:52:48 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. this seems to work like my ISP. I have at the end a private IP address in the range 10.x.y.z. They do the translation when needed for me. Of course, my machine is not accessible from outside. What confuses me is that your XP machine gets a 192.168 address between. How can it access the DHCP then? Can you try to limit the address range to 10.x.y.z during the negotiation phase? How do you connect to the cable? Is there some kind of a 'modem'? Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
Hi, On Sunday 01 April 2012 08:57:00 Da Rock wrote: Did they come to your location and run a test to their equipment? My neighbor had a recent cable outage of an existing cable on our block that was too low and a moving van hit it. Apparently the Windows system works, so I'd assume all that side is ok- just FBSD box is the issue. so, there is some difference. The questions are there to find out what the difference might be. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Access to Time Warner cable network
On Sat, Mar 31, 2012 at 11:21 PM, Erich Dollansky erichfreebsdl...@ovitrap.com wrote: Hi, On Sunday 01 April 2012 08:57:00 Da Rock wrote: Did they come to your location and run a test to their equipment? My neighbor had a recent cable outage of an existing cable on our block that was too low and a moving van hit it. Apparently the Windows system works, so I'd assume all that side is ok- just FBSD box is the issue. so, there is some difference. The questions are there to find out what the difference might be. Erich to me it sounds like a link negotiation problem between the network interfaces, and auto-sensing not being able to sync you might need to set the interface on the bsd box manually to see if you can even establish link, once link is up dhcp should function ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
