Re: lan network mapping...

[Samuel Sieb]

Rob Healey wrote:
> I have a wireless print server in my lan, and it has a specific ip
> address, something like 192.168.0.10, 192.168.1.10, 172.16.0.10 ...
>
[...]
>
> Is there any software out there that can scan my lan, and report what ip
> address and device name that is on the network?
>

You can scan subnets with nmap using "nmap -sP 192.168.0.0/24".  That will do a 
ping test.  Better is if you know there's a specific open TCP port on the 
device.  For example if port 80 is open, then you can do "nmap -sT -p 80 
192.168.0.0/24" and look for ones that are listed as open.

It's not clear from your email if the address is one that is in your current 
subnet, so you may need to do "ifconfig eth0:0 192.168.0.2/24" first 
(substitute 
your interface name if not eth0).  You can use wider subnets to scan faster.

If you know it ends in .10 then you could use a bash script to find it even 
quicker.

Broadcast pings don't work so well as only some devices respond to those.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: lan network mapping...

[Genes MailLists]

On 07/15/2011 10:59 PM, Clyde E. Kunkel wrote:
> On 07/15/2011 08:50 PM, Rob Healey wrote:
>> Greetings:
>>
>> I would like to explain what I am trying to do, and then see if there is a
>> solution to my issue?
>>
>> I have a wireless print server in my lan, and it has a specific ip address,
>> something like 192.168.0.10, 192.168.1.10, 172.16.0.10 ...
>>
>> I know that I changed it once before, and didn't need it for a long time,
>> and now I do again!  I do not remember what it's software set ip address
>> was...
>>
>> I know my username, and password is to the printer server, but I can access
>> and change the ip address until I can find what it is?
>>
>> Is there any software out there that can scan my lan, and report what ip
>> address and device name that is on the network?
>>
>> I know that this is kind of a loaded problem, but I need to be able to use
>> my print server once again?
>>
>>

  next time put the IP in your dns :-)

  I'd try using nmap to see what it can discover for you  ...
  the IP's that are alive on your local net you can get by something like

   nmap -sP 192.168.1.1-254

  Then you can use nmap on the ip's to see what info it can garner about
the device.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: lan network mapping...

[Clyde E. Kunkel]

On 07/15/2011 08:50 PM, Rob Healey wrote:
> Greetings:
>
> I would like to explain what I am trying to do, and then see if there is a
> solution to my issue?
>
> I have a wireless print server in my lan, and it has a specific ip address,
> something like 192.168.0.10, 192.168.1.10, 172.16.0.10 ...
>
> I know that I changed it once before, and didn't need it for a long time,
> and now I do again!  I do not remember what it's software set ip address
> was...
>
> I know my username, and password is to the printer server, but I can access
> and change the ip address until I can find what it is?
>
> Is there any software out there that can scan my lan, and report what ip
> address and device name that is on the network?
>
> I know that this is kind of a loaded problem, but I need to be able to use
> my print server once again?
>
>
>
>

If you use a stand alone router you should be able to access the router 
via browser at 192.168.0.1 or .1.1 (usually) and look for an entry for 
attached devices.

-- 
Regards,
OldFart

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: lan network mapping...

[Richard Ryniker]

Try a broadcast ping, and see who responds.  One of the responses from an
address you do not recognize as something else may be your print server.

Example:

# ping -b -I eth0 192.168.100.255
WARNING: pinging broadcast address
PING 192.168.100.255 (192.168.100.255) from 192.168.100.32 eth0: 56(84) bytes 
of data.
64 bytes from 192.168.100.29: icmp_req=1 ttl=64 time=0.597 ms
64 bytes from 192.168.100.18: icmp_req=1 ttl=64 time=1.39 ms (DUP!)
64 bytes from 192.168.100.41: icmp_req=1 ttl=64 time=9.20 ms (DUP!)

Ping to a broadcast address usually requires root privilege.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

lan network mapping...

[Rob Healey]

Greetings:

I would like to explain what I am trying to do, and then see if there is a
solution to my issue?

I have a wireless print server in my lan, and it has a specific ip address,
something like 192.168.0.10, 192.168.1.10, 172.16.0.10 ...

I know that I changed it once before, and didn't need it for a long time,
and now I do again!  I do not remember what it's software set ip address
was...

I know my username, and password is to the printer server, but I can access
and change the ip address until I can find what it is?

Is there any software out there that can scan my lan, and report what ip
address and device name that is on the network?

I know that this is kind of a loaded problem, but I need to be able to use
my print server once again?

-- 
Sincerely yours,
Rob G. Healey

"Always surround yourself with people that inspire you to
greatness!"
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora QA] #212: Review Fedora on Amazon EC2 Test Day wiki page:

[Fedora QA]

#212: Review Fedora on Amazon EC2 Test Day wiki page:
---+
  Reporter:  athmane   |   Owner:  athmane  
  Type:  task  |  Status:  new  
  Priority:  major |   Milestone:  Fedora 16
 Component:  Test Day  | Version:   
Resolution:|Keywords:   
---+
Comment (by athmane):

 As agreed at the last Cloud SIG meeting, I've copied the page and
 categorized it:

 https://fedoraproject.org/wiki/Test_Day:2011-07-19_Cloud_SIG_Fedora_EC2

-- 
Ticket URL: 
Fedora QA 
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora QA] #222: L10N Test Day

[Fedora QA]

#222: L10N Test Day
---+
  Reporter:  noriko|   Owner:   
  Type:  task  |  Status:  new  
  Priority:  major |   Milestone:  Fedora 16
 Component:  Test Day  | Version:   
Resolution:|Keywords:   
---+
Comment (by igor):

 Replying to [comment:9 rhe]:
 > According to noriko, the specific images will be provided for L10N test
 day, so I guess the installed system is not suitable for test? But it's a
 good idea to do it before i18n desktop day.

 A installed system should be suitable for test as long as it's fully
 updated. I'll keep this in mind and will explicit add this information on
 the test days wiki pages.

 Also as Igor suggested, we still give each test day an exact date but with
 proper announcements. In all the test week could be organized like:
 >
 > * https://fedoraproject.org/wiki/Test_Day:2011-08-22_L10n_Desktop
 (Mon)
 > *
 https://fedoraproject.org/wiki/Test_Day:2011-08-24_L10n_i18n_Installation
 (Wed)
 > * https://fedoraproject.org/wiki/Test_Day:2011-08-26_I18n_Desktop
 (Fri)
 >
 > I've updated the test day schedule to include these. Feel free to
 discuss and modify it in need.

 Sounds pretty good to me. I'll start working on the creation of wiki pages
 next week.

-- 
Ticket URL: 
Fedora QA 
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

2011-07-15 - F16 Alpha blocker bug review #1 - recap

[James Laska]

#fedora-bugzappers: F16-Alpha Blocker Review


Minutes:
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-07-15/f16-alpha-blocker.2011-07-15-17.00.html
Minutes (text): 
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-07-15/f16-alpha-blocker.2011-07-15-17.00.txt
Log:
http://meetbot.fedoraproject.org/fedora-bugzappers/2011-07-15/f16-alpha-blocker.2011-07-15-17.00.log.html

Meeting summary
---
* Roll Call  (jlaska, 17:01:06)

* Why are we here?  (jlaska, 17:04:09)
  * We'll be walking through the proposed, accepted blockers and NTH
bugs listed at
http://fedoraproject.org/wiki/Current_Release_Blockers  (jlaska,
17:04:34)
  * LINK: http://fedoraproject.org/wiki/Fedora_16_Alpha_Release_Criteria
(jlaska, 17:04:46)
  * LINK: http://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(jlaska, 17:05:05)

* All proposed systemd Alpha blockers  (jlaska, 17:06:06)
  * LINK:
http://lists.fedoraproject.org/pipermail/test/2011-July/101332.html
(jlaska, 17:07:04)
  * AGREED: all the sysv-to-systemd conversion bugs should not be
handled by the release blocker review process but the feature
process, so 713562 is rejected as a blocker  (adamw, 17:09:39)

* https://bugzilla.redhat.com/show_bug.cgi?id=714478  (jlaska, 17:14:38)
  * CPU lockup during boot  (jlaska, 17:14:54)
  * The fix has been posted to lkml, but is not yet in Linus' tree.
(jlaska, 17:17:12)
  * AGREED: 714478 - AcceptedBlocker - causes boot failures for i686
kernel  (jlaska, 17:22:23)

* https://bugzilla.redhat.com/show_bug.cgi?id=718722  (jlaska, 17:22:47)
  * Mismatched or corrupt version of stage1/stage2  (jlaska, 17:22:54)
  * LINK: http://fedoraproject.org/wiki/Features/Grub2   (brunowolff,
17:27:57)
  * AGREED: 718722 - leave on the list pending rawhide acceptance
install results.  Will reevaluate next week  (jlaska, 17:28:10)

* https://bugzilla.redhat.com/show_bug.cgi?id=720034  (jlaska, 17:28:20)
  * unsupported locale setting  (jlaska, 17:28:31)
  * ACTION: jlaska - check-in w/ pjones for grub assistance on 718722
(jlaska, 17:29:22)
  * impacts Alpha criteria - The installer must boot (if appropriate)
and run on all primary architectures from default live image, DVD,
and boot.iso install media  (jlaska, 17:30:52)
  * AGREED: 720034 - AcceptedBlocker - appears to prevent all live
installs  (jlaska, 17:31:20)

* https://bugzilla.redhat.com/show_bug.cgi?id=722466  (jlaska, 17:31:38)
  * creating 32 bit isos fails when there is 2 kernels  (jlaska,
17:31:44)
  * AGREED: 722466 RejectedBlocker - Does not prevent Alpha installs and
can be manually installed after anaconda.  May consider as a
F16Blocker  (jlaska, 17:38:08)

* Open Discussion -   (jlaska, 17:40:57)

* discussion on reducing blocker meeting length  (jlaska, 17:43:37)
  * LINK: https://fedorahosted.org/fedora-qa/ticket/221   (jlaska,
17:43:49)
  * Still searching for ways to reduce blocker meeting length  (jlaska,
17:51:49)

* Open Discussion - last call  (jlaska, 18:02:11)

Meeting ended at 18:03:32 UTC.




Action Items

* jlaska - check-in w/ pjones for grub assistance on 718722




Action Items, by person
---
* jlaska
  * jlaska - check-in w/ pjones for grub assistance on 718722
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* jlaska (157)
* adamw (59)
* tflink (41)
* Viking-Ice (41)
* brunowolff (34)
* j_dulaney (33)
* rbergeron (8)
* buggbot (5)
* zodbot (4)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

2011-07-15 @ 17:00 UTC - F16 Alpha blocker bug review #1 - REMINDER

[James Laska]

- Original Message -
> # F16 Alpha Blocker Review meeting #1
> # Date: 2011-07-15
> # Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
> # Location: #fedora-bugzappers on irc.freenode.net

Just a reminder that the first Fedora 16 Alpha blocker bug review meeting 
starts in under 1 hour.  Come join us in #fedora-bugzappers to expedite 
reviews, or comment in any bugs prior to the meeting.

https://fedoraproject.org/wiki/Current_Release_Blockers

Thanks,
James
 
> Hard to believe, but the "vacation" is over. Fedora 16 Alpha test
> compose is a few weeks away (Jul 26) and the Alpha is about a month
> away
> (Aug 10 for go/no_go meeting).
> 
> In an effort to reduce last minute bug scramble, the blocker review
> meetings will be starting up again [2]. Each Friday, between now and
> the Alpha release, a blocker review will take place in
> #fedora-bugzappers.
> 
> Mark your calendars ... the first Alpha blocker review meeting starts
> at
> 17:00 UTC in #fedora-bugzappers. We'll review proposed and accepted
> F16
> Alpha blocker bugs. An updated list of blocker bugs is available at
> https://fedoraproject.org/wiki/Current_Release_Blockers (also attached
> to this mail). We'll be reviewing the bugs to determine ...
> 1. whether they meet the Alpha release criteria [3] and should stay
> on the list
> 2. are getting the attention they need
> 
> For guidance on Blocker and Nice-to-have (NTH) bugs, refer to
> https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process and
> https://fedoraproject.org/wiki/QA:SOP_nth_bug_process
> 
> == Suggested Meeting Preparation ==
> 
> Maintainers ...
> * If your bug is *not* MODIFIED ... this issue is at risk of
> slipping the F16 Alpha release date
> * If your bug is in MODIFIED ... please make sure a build with the
> fix exists, and is available as a bodhi update.
> 
> Testers ...
> * If you REPORT a bug ... please be responsive to any requests for
> additional information.
> * If a bug is in ON_QA ... please take a moment to apply the
> update, and post karma feedback (doesn't apply to rawhide at the
> moment)
> 
> [1] https://fedoraproject.org/wiki/Infrastructure/UTCHowto
> [2]
> http://rbergero.fedorapeople.org/schedules/f-16/f-16-quality-tasks.html
> [3] https://fedoraproject.org/wiki/Fedora_16_Alpha_Release_Criteria
> 
> Thanks,
> James
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test