Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Subject: broadcast IP

Original Message
Name: hing_hk
Date: December 5, 2007 at 21:09:09 Pacific
Subject: broadcast IP
OS: Network
CPU/Ram: Not specified
Model/Manufacturer: Cisco
Comment:
I believe if the R1 receive a packet with destination address 192.168.1.255, it will broadcast it to every host, Host 1 and Web Server 2 , since the last octet is all '1' ->255. Yet, my friend believe the R1 will drop the packet. Could anyone please advise on this and give as much elaboration as possible. Thank you.

Thank you, conscientious student


Report Offensive Message For Removal

Response Number 1
Name: hing_hk
Date: December 5, 2007 at 21:21:20 Pacific
Subject: broadcast IP
Reply: (edit)
O I have attached a graph, it seems not working. Let me attach it again.

Thank you, conscientious student


Report Offensive Follow Up For Removal

Response Number 2
Name: hing_hk
Date: December 5, 2007 at 21:33:29 Pacific
Subject: broadcast IP
Reply: (edit)
!? I still can not attach the picture. Let me try again

Okay, I have tried three times already but still doesn't work. Please refer to this link = <http://www.esnips.com/imageable/medium/1a5432c0-e727-44f8-95a0-e17d8f0f3ee6/?du=64d2f284-9087-102a-8e73-0017a4493db2&uu=284abeaa-3da8-4a3c-bcd0-9ee281419707&dt=1196910726000&fu=85ebc89a-1252-41c3-9cbd-6db2aab45728>


Report Offensive Follow Up For Removal

Response Number 3
Name: wanderer
Date: December 6, 2007 at 08:19:41 Pacific
Subject: broadcast IP
Reply: (edit)
If R1 is a router your friend is correct. Unless configured to pass thru, a router will drop the broadcast. A router will not rebroadcast the broadcast on a lan.

Are you ready for where Microsoft wants you to go today?


Report Offensive Follow Up For Removal

Response Number 4
Name: hing_hk
Date: December 7, 2007 at 22:51:13 Pacific
Subject: broadcast IP
Reply: (edit)
Could you please explain what do you mean by rebroadcast?

I assume that if I send a packet to the R1 with an IP address 192.168.1.255, the R1 should broadcast the message to every host on the LAN.


Report Offensive Follow Up For Removal

Response Number 5
Name: wanderer
Date: December 9, 2007 at 20:42:26 Pacific
Subject: broadcast IP
Reply: (edit)
why do you think a router would rebroadcast ANY broadcast?

Ask yourself these questions:

1. does a router NAT/Route a broadcast? If that isn't obvious then how can a broadcast be routed?

2. why would a router drop a broadcast? Hint: bandwidth saturation

Now don't confuse broadcasts with multicast. Two different animals.

http://www.inetdaemon.com/tutorials...

Are you ready for where Microsoft wants you to go today?


Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: broadcast IP

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software



Version Tracker Pro
Keep your software current and secure, effortlessly

Click Here for a Free Scan

Driver Agent
Automatically find the latest drivers for your computer.
Click Here for a Free Scan



The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC