Telewest + Linux + MAC(?) oddness
Has anyone used a Telewest modem and had problems having it play nicely with Linux? The situation is that a Windows 2000 box with its MAC address registered on blueyonder's site works fine when directly plugged into the Telewest cable modem, but a linux box whose external NIC's MAC address is similarly registered, and plugged directly in doesn't work. Even configuring it with the same IP/network config leased by the Windows box provides no joy. I'm wondering if the modem is rejected the MAC of the linux box while the Windows's box's lease is still in effect or something bizarre like that. Anyone got a clue here? Thanks, Paul -- Paul Makepeace ... http://paulm.com/ "If I knew what you were talking about, then we should discuss only Greek Mythologyand me!" -- http://paulm.com/toys/surrealism/
Re: Telewest + Linux + MAC(?) oddness
Paul Makepeace wrote: > I'm wondering if the modem is rejected the MAC of the linux box while > the Windows's box's lease is still in effect or something bizarre like > that. Yes. Or the DHCP server at the ISP. With NTL I had to switch off the cable modem for a few hours until the DHCP lease expired. Then all was good. A
RE: Telewest + Linux + MAC(?) oddness
> Has anyone used a Telewest modem and had problems having it > play nicely with Linux? Nope. It should JustWork(tm) (although s/Linux/FreeBSD/ in my case). > The situation is that a Windows 2000 box with its MAC address > registered on blueyonder's site works fine when directly plugged into > the Telewest cable modem, but a linux box whose external NIC's MAC > address is similarly registered, and plugged directly in doesn't work. > Even configuring it with the same IP/network config leased by the > Windows box provides no joy. > > I'm wondering if the modem is rejected the MAC of the linux box while > the Windows's box's lease is still in effect or something bizarre like > that. > > Anyone got a clue here? How long have you waited after getting the new MAC address added? These things can take up to 24 hours, IIRC. You might have some success by powering off the cable modem (physically unplugging it from both the wall, *and* unscrewing the cable connection), waiting 5-10 minutes, and then trying again[1]. If you're desperate you could always just switch NICs to make sure things work. I assume you've already checked all the obvious stuff (cables, duplex settings, routing tables, and so on...)? N [1] Ugh. I sound like BY support. -- 11 2 3 4 5 6 77 0 0 0 0 0 0 05 -- The 75 column-ometer Global Messaging, A: Top posting 120 Cheapside, x83331 Q: What's the most annoying e-mail habit?
Re: Telewest + Linux + MAC(?) oddness
Quoting Andy Wardley ([EMAIL PROTECTED]): > Paul Makepeace wrote: > > I'm wondering if the modem is rejected the MAC of the linux box while > > the Windows's box's lease is still in effect or something bizarre like > > that. > > Yes. Or the DHCP server at the ISP. > > With NTL I had to switch off the cable modem for a few hours until the > DHCP lease expired. Then all was good. > [ this if for Telenet, a Belgian cable modem ISP ] With Telenet I even noticed that I can't get an IP adress for the same MAC addres when booting linux (dual boot). - boot machine windows 2000: gets IP address via DHCP - reboot machine to Linux : DHCP does not give IP address - reboot machine to Windows: gets IP address Waiting the DHCP expiry time solves the problem (as did adding a FW/router machine :) ). Kris,
Re: Telewest + Linux + MAC(?) oddness
On Tue, 24 Jun 2003, Paul Makepeace wrote: > Ha`s anyone used a Telewest modem and had problems having it play nicely > with Linux? Yes and No. My Smoothwall runs just fine. > I'm wondering if the modem is rejected the MAC of the linux box while > the Windows's box's lease is still in effect or something bizarre like > that. > > Anyone got a clue here? You're pretty much correct. I've found that switching the modem off, then swapping the machine and powering up with the new nic in place does the trick. Their hinder^Whelp pages suggest releasing the dhcp lease before doing that but I've never found it necessary. 'ipconfig /release' on a win2k box. You know that you can register MACs directly via the webshite ? Check with the working machine and have a look at http://selfcare.blueyonder.co.uk/PInfranetServlet?page=p_list_mac_addrs&loadBean=yes You'll need the username and password that they sent you when you signed up. It's *much* quicker than talking to the helldesk ! Simon. -- "Oh no, not again."
Re: Telewest + Linux + MAC(?) oddness
Simon Wilcox wrote: You're pretty much correct. I've found that switching the modem off, then swapping the machine and powering up with the new nic in place does the trick. Their hinder^Whelp pages suggest releasing the dhcp lease before doing that but I've never found it necessary. 'ipconfig /release' on a win2k box. You know that you can register MACs directly via the webshite ? Check with the working machine and have a look at http://selfcare.blueyonder.co.uk/PInfranetServlet?page=p_list_mac_addrs&loadBean=yes You'll need the username and password that they sent you when you signed up. It's *much* quicker than talking to the helldesk ! i've found the following site about Telewest and NTL cable modems very useful: http://homepage.ntlworld.com/robin.d.h.walker/cmtips/index.html (http://homepage.ntlworld.com/robin.d.h.walker/cmtips/swap.html#swap concerns the DHCP release/MAC address issue) Michael.
Re: Telewest + Linux + MAC(?) oddness
Thanks everyone (incl. Paul Hammond who answered offlist)! In the end I powered down the Windows box Tuesday, came in Wednesday and switched off the cable modem for a few minutes and then rebooted the linux box with the modem back on. It grabbed an IP and is working fine. Which of those did it I'm not sure but it's working finally. Paul PS DynDNS++ (http://www.dyndns.org + apt-get install ddclient) -- Paul Makepeace ... http://paulm.com/ "What is bait? The moon rising over the mountain." -- http://paulm.com/toys/surrealism/