At 02:08 PM 2/22/2004, Olaf Hoyer wrote:
On Sun, 22 Feb 2004, Marty Landman wrote:
So the arp cache doesn't have nodes on it which it hasn't had activity from
for a time?
Yes.
I struck out with upgrading nmap to 3.50 as well, and wanting to learn a
little about shell scripting wrote this
At 05:04 PM 2/21/2004, Chuck Swiger wrote:
Marty Landman wrote:
looks like arp is unreliable for a canonical list of plugged in ip's.
Curious about what would work.
nmap -sP 22 192.168.0.0/24 should do it
%nmap -sP 22 192.168.0.0/24
Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
Target host
On Sun, 22 Feb 2004, Marty Landman wrote:
At 05:04 PM 2/21/2004, Chuck Swiger wrote:
Marty Landman wrote:
looks like arp is unreliable for a canonical list of plugged in ip's.
Curious about what would work.
nmap -sP 22 192.168.0.0/24 should do it
%nmap -sP 22 192.168.0.0/24
Starting
On Sun, 22 Feb 2004, Marty Landman wrote:
At 09:42 AM 2/22/2004, Olaf Hoyer wrote:
The syntax to ping a whole /24 segment would be:
Hi Olaf. Could you please explain what is meant by '/24 segment'? I'm new
to networking as you can see!
Hi!
Well, what is formerly called a Class C network
At 12:01 PM 2/22/2004, Olaf Hoyer wrote:
Well, what is formerly called a Class C network is now in the new
CIDR-notation a /24, meaning that there are 256 IP's in that network.
Thanks for explaining Olaf. Little by little the fog is clearing before my
eyes, and things which are just words to me
On Sun, 22 Feb 2004, Marty Landman wrote:
Seems to be a bug with nmap V3.00 I use 3.50, and it works. Solution could
be an upgrade or exclusion of your own box from the scanning range.
Could you explain how I can do either - or preferably both? My experience
with ports btw is strictly
Marty Landman wrote:
At 05:04 PM 2/21/2004, Chuck Swiger wrote:
[ ... ]
% nmap -sP 22 192.168.0.0/24
I don't understand the man page though so assume it's me, not nmap.
Whoops, I switched from recommending using -p 22 (to just scan the ssh port
via TCP), to doing ICMP pinging, but I didn't make
Hi,
On Fri, Feb 20, 2004 at 04:05:54PM -0800, Jim Pazarena wrote:
I have a wireless home network with an 802.11B router which assigns
IPs via DHCP.
what method is appropriate to access one fbsd box from another when
I don't actually know the IP which has been assigned to any given
box.
At 12:21 AM 2/21/2004, Saint Aardvark the Carpeted wrote:
Jim Pazarena disturbed my sleep to write:
May sound rookie, but presently I go to each box and determine it's
IP directly and then I know the IP (at least for this session).
What I end up doing is browing the hosts file on my gateway
I have a wireless home network with an 802.11B router which assigns
IPs via DHCP.
what method is appropriate to access one fbsd box from another when
I don't actually know the IP which has been assigned to any given
box.
May sound rookie, but presently I go to each box and determine it's
IP
Jim Pazarena disturbed my sleep to write:
May sound rookie, but presently I go to each box and determine it's
IP directly and then I know the IP (at least for this session).
There has gotta be a better way.
One thing that *might* work is displaying the arp cache. This is the list
of MAC
Jim Pazarena wrote:
I have a wireless home network with an 802.11B router which assigns
IPs via DHCP.
what method is appropriate to access one fbsd box from another when
I don't actually know the IP which has been assigned to any given
box.
May sound rookie, but presently I go to each box and
12 matches
Mail list logo
