IP Address Problems
hentaidan at gmail.com
Tue Jan 10 16:59:04 UTC 2006
Another phone call.... something about my computer trying to boot from
the network? PIXIE boot or something?
They have a record of it starting 26th November, then the 18th of
December then the 31st of December. (I was away 19th - 30th December.)
On 10/01/06, dan <hentaidan at gmail.com> wrote:
> On 10/01/06, Andrew Jorgensen <andrew.jorgensen at gmail.com> wrote:
> > You say you have written your own script to spoof the MAC address?
> > This is very likely the source of your troubles. When does this
> > script run? (What other script triggers it?) What exactly does your
> > script do?
> The script (below) was run by me, after I had logged in (only on the
> spoofed machine)
> sudo /etc/init.d/networking stop
> sudo ifconfig eth0 hw ether AA:BB:CC:DD:EE:FF
> sudo /etc/init.d/networking start
> But the problems occur on the *real* NIC as well.
> I am using the method suggested by Michael (above) to spoof the MAC
> address now (in /etc/network/interfaces) and the problems still exist,
> unless I activate the network after I have logged in via the GUI.
> On 10/01/06, Michael J. Lynch <mlynch at gcom.com> wrote:
> > dan wrote:
> > > And auth eth0 has been added to the end of /etc/network/interfaces on
> > > the laptop as well.
> > >
> > Are you sure it's "auth" and not
> > "auto". Even so, nothing should be writing to the file at boot time.
> Apologies, it is "auto".
> > Try removing the appended line from your interfaces file, change the
> > mode of the file to read only (sudo chmod a-w /etc/network/interfaces),
> > then reboot and see what happens. If this works, then the problem is
> > definitely something prior to network initialization. If the problem
> > happens again, check mode and content of the interfaces file to see if
> > either have changed. If so, something is replacing the file.
> I worked out what was adding "auto eth0", it's the GUI network-admin
> tool after I deactivate/activate the network interface (which gives me
> my "correct" IP) and clicked OK.
> > I just had another thought. Your DHCP client may be at fault too. Take
> > a look at /etc/dhcp3/dhclient.conf. See if there is a section starting
> > that looks like:
> > <snip>
> > If so, comment it out, especially if there is a keywork "fixed-address"
> > in that section.
> There is but it appears to be commented out. The only thing not
> commented out is:
> request subnet-mask, broadcast-address, time-offset, routers,
> domain-name, domain-name-servers, host-name,
> netbios-name-servers, netbios-scope;
More information about the ubuntu-users