Solved

WOL - why do i need .255 broadcast address in the vlan of the sccm 2012 server

Posted on 2014-01-06
6
1,606 Views
Last Modified: 2014-01-22
Hi - I'm having trouble setting up WOL for scccm 2012.

It was suggested I require ip-helpers to in the VLAN config on the VLAN that the sccm server is in (sender) -  1 for each vlan broadcast address to) to the .255 broadcast address.

Can someone please explain why i need these (see example config below with ip-helpers in  quotes "") My understanding of ip-helper is along lines of client (dhcp for eg) finds ip-helper in vlan to allow broadcast to go to dhcp server accross vlan.

interface Vlan20
description 1st Floor Vlan Wake on Lan Client
ip address 192.168.1.0 255.255.255.0
ip directed-broadcast 100

interface Vlan30
description 2nd Floor Vlan Wake on Lan Client
ip address 192.168.2.0 255.255.255.0
ip directed-broadcast 100

interface vlan40
description Wake on Lan Server
ip address 192.168.3.0 255.255.255.0
"ip helper-address 192.168.1.255"
"ip helper-address 192.168.2.255"

WHY DO I NEED THESE LAST 2 LINES? - or do I?

Can someone please give me explanation.
this in 3750 cisco router
0
Comment
Question by:philb19
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
  • 2
6 Comments
 
LVL 57

Expert Comment

by:giltjr
ID: 39761218
A WOL frame is a broadcast frame, as such the sending host puts the IP broadcast address for the subnet the sender is on.

Since you are trying to send the WOL to a host in a different subnet, you use the ip helper command to change the IP broadcast address.

Say your source host is 192.168.3.20 and mask is 255.255.255.0.  The broadcast would be 192.168.3.255.  If you want to send this to a host on 192.168.1.0/24 or 192.168.2.0/24 subnet, it would be ignored by all hosts because 192.168.3.255 is not the broadcast address for those subnets.  The ip helper address will cause the router to send out the WOL frame using the dest IP address of 192.168.1.255 and 192.168.2.255.
0
 

Author Comment

by:philb19
ID: 39761256
ok great thanks clear explanation. I have a Cisco engineer who is saying Its not required - and he has setup  WOL without it. - stating it is is dangerous? - allowing broadcast

I initially put in as suggested config and - as it does not work without it i imagine i was right.

I imagine with each vlan having ip directed-broadcast 101 as an ACL it will only allow broadcast from the sccm server
0
 
LVL 57

Accepted Solution

by:
giltjr earned 500 total points
ID: 39761842
I will double check, I have never had to set this up personally, just helped others do it.  However, I'm not sure how it would work without.

Without that the WOL magic packet will NOT be forwarded to the other VLAN's.

Allowing it can cause problems.  Thinks about it, in your setup L2/L3 broadcast frame on VLAN 40 is now forwarded to both VLAN 30 and VLAN 20 no matter what.  That could be a ton of traffic or next to nothing.

However, as you stated, you can reduce the possibility of problems by creating an ACL to limit the source IP address(es) that will trigger the process.
0
Why Off-Site Backups Are The Only Way To Go

You are probably backing up your data—but how and where? Ransomware is on the rise and there are variants that specifically target backups. Read on to discover why off-site is the way to go.

 
LVL 16

Expert Comment

by:vivigatt
ID: 39765151
If the packets need to be sent to broadcast address, there MUST be some kind of broadcast forwarding or relaying if the computer that sends the magic packets is on another subnet than the computers to be awaken. Broadcasts are not supposed to be transmitted from one subnet to another. I would not forward all broadcasts between 2 subnets, this is not desirable.
You should check what kind of packets are sent by your WOL sender and forward only said packets (for instance UDP port 7 or 9).
Use a network packet capture tool (WireShark or MS Netmon), record a trace when the sender and receiver are on the same subnet and make some assumptions from there that will allow you to set the correct rules so that you don't forward all broadcasts from sender's subnet to receivers' subnets.
Another way around is to use Subnet directed broadcasts or a WOL proxy/Relay such as http://www.mylanviewer.com/wake-on-lan-proxy-server.html .


There are several types of WOL packets:
Magic Packets (described in this article in particular):
http://en.wikipedia.org/wiki/Wake-on-LAN
Pattern Match:
http://technet.microsoft.com/en-us/library/ee617165%28v=ws.10%29.aspx

Some useful links:
http://niksideas.blogspot.fr/2011/12/wake-on-lan-wol.html
0
 

Author Comment

by:philb19
ID: 39765516
thanks to all posts -just to add here it does work with the .255 to all vlans. - I do have
an ACL allowing  only sccm to direct-broadcast - and  sh access-list has hit-count 4 on the udp port 9 - all other ACE's to other ports have hit of 0 - so i will prune the acl I guess
0
 
LVL 16

Expert Comment

by:vivigatt
ID: 39765661
You can run a packet capture tool on one of the receivers subnets to check that you have not more forwarded broadcasts than what you want.
0

Featured Post

Resolve Critical IT Incidents Fast

If your data, services or processes become compromised, your organization can suffer damage in just minutes and how fast you communicate during a major IT incident is everything. Learn how to immediately identify incidents & best practices to resolve them quickly and effectively.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Join Greg Farro and Ethan Banks from Packet Pushers (http://packetpushers.net/podcast/podcasts/pq-show-93-smart-network-monitoring-paessler-sponsored/) and Greg Ross from Paessler (https://www.paessler.com/prtg) for a discussion about smart network …
This article is a collection of issues that people face from time to time and possible solutions to those issues. I hope you enjoy reading it.
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Suggested Courses

729 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question