Thick Ethernet/Sun networking problems

From: Douglas Quebbeman <dhquebbeman_at_theestopinalgroup.com>
Date: Fri Nov 2 15:30:35 2001

> On Nov 2, 8:03, Douglas Quebbeman wrote:

[..snip..]

> > If that doesn't work, this next idea will take some time and preparation.
> > Get a Windows 2000 or Windows XP machine. They allow you to change the
> > machine's network address on the fly (can Linux do this?)
>
> MOST systems other than Windows can do this :-)
>
> It's not a good idea if you need to go through all the networks numbers
> (see end of this post for the reason, if you've not realised yet).

Someone else pointed out IFCONFIG; sorry, not a *nix guru.
I tolerate *nix as Multics' poor deformed little brother.
A useful tool, tho, no disputing that, and no Multics in
sight to brag about any more. :(

And as to the other thing you're alluding to, I never have
professed to be an expert on TCP/IP... I was assuming he'd
work with one class of networks at a time, tho...

[..snip..]

> Don't forget to restore the original address with "ifconfig le0 111.0.0.1
> broadcast 111.255.255.255 netmask 255.0.0.0 up" when you've finished :-)

What does 'broadcast' do (other than the obvious)?
 
> It'll take a while to work through the class C range, because ping will
> take a while to time out on each network number :-) Say two seconds per
> network, thats (224-192) * 256 * 256 * 2 seconds, about 4 million seconds,
> or just over 48 days. Oh, and you'll probably want to refine my shell
> script to eliminate the unneccesary lines generated by ping recording
> responses from the Sun itself, and the headers. You don't need 12 million
> extra lines in the output :-)

Yes, I'd say he would benefit from some filtering if he
has to check all the class C range, but I was assuming
this could take a couple of months, worst-case...

-dq
Received on Fri Nov 02 2001 - 15:30:35 GMT