On Saturday 07 June 2008, Mike Kershaw wrote: > On Sat, Jun 07, 2008 at 12:37:22PM -0400, John R Puhalski wrote: > > I set up a computer for my son with Kubuntu 8.04. He is in NJ and has > > an internet with Comcast. I told him to do the initial setup with > > comcast using a windows computer (which he did) because they'll tell him > > they dont support linux (which they did). In my experience with opimum > > and verizon i did this initail setup and then was good to go. > > > > He can now connect to the internet with the windows laptop but when > > connecting to linux and opening firefox the ubuntu homepage opens, but > > links on that page or any url's do not work. It says server not found. > > Typically a cable modem will bind to the first MAC (6 byte ethernet > hardware address, unique to every card) it sees and only give that MAC > an IP.
Yeah, this problem is typical and annoying, and is one of the good reasons
to use the "hwaddress ether <MAC>" setting in /etc/network/interfaces.
[See 'man 5 interfaces' on a Debian-based distro (like Ubuntu) for details.]
This setting lets you /set/ the MAC address for an ethernet interface. :-)
Supposedly not all drivers for ethernet devices allow for this, but so far
all of the [wired] devices I've tried it on, it's worked.
The other interesting reason to use the hwaddress setting is to elimitinate
the need to wait for the ARP timeout when switching out a router. i.e. if
you use the same MAC addresses for the new router that the old one used, then
the machines and switches won't need to update their ARP table before packets
will flow again.
> Try:
>
> 1 - turn off the windows machine
> 2 - turn off the cable modem. ie, unplug it.
> 3 - wait 5 minutes (maybe excessive but I've seen their side of the
> network hold on for a while)
When cable modems first came out I think the time that people had to wait
was somewhere near a week. Later that got shortened to 30 minutes. Now it's
(thankfully) typically even shorter than that.
> 4 - connect linux machine
> 5 - power on cable modem, linux, see if it works.
>
> if that doesn't, try this:
>
> 1 - go to windows machine, network settings, ethernet adapter, and get
> the mac address
> -or-
> run->cmd.exe then 'ipconfig /all' and look for the MAC
> 2 - go to linux and do
> ifconfig eth0 down
> ifconfig eth0 hw ether <mac you got from windows>
> and restart networking on linux
Great instructions, Mike.
> Agreed with other comments about it not being an amazing idea to run
> a workstation directly connected. A linksys wrt54gl (note the 'L'), or
> as Chris has been experimenting with, and Alix from pc-engines, would
> make a good firewall. Linksys/Openwrt/Etc can clone the mac address
> from windows, too.
>
> -m
BTW, the Alix2c3 has worked out even better than I had hoped for. I've
been working on a detailed writeup of setting it up; right now I've got a web
page with pictures that explains at least how I load it with Debian Etch,
along with links for other alternative hardware, such as the WRT54GL.
http://www.coredump.us/index.php?n=Main.Alix2c3WithDebianEtch
As long as the above page is, it doesn't yet cover actually setting it up
as a firewall yet, nor setting up QoS rules. I'm currently trying out the
HTB QoS rules on this page, which seem to be working fine so far:
http://lartc.org/howto/lartc.cookbook.ultimate-tc.html#AEN2241
-- Chris
--
Chris Knadle
[EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Jun 4 - Sqeak! and eToys Jul 2 - KVM (Tenative) Aug 6 - Zenos Sep 3 - TBD
