FOG and workstations in different subnetworks.



  • Hi ;) We have:
    [LIST]
    []Fog in x.x.1.0 network
    [
    ]Department 1 in x.x.2.0 network
    []Department 2 in x.x.3.0 network
    [
    ]Department 3 in x.x.4.0 network
    [/LIST]
    I know that this is one of most asked questions, but how can we make it works?
    Perfectly works with dhcp 066/067 options, but (as you know) WOL function doesnt work out of L2.
    P.S. I read your WIKI/Guide page and saw some sort of WOL Broadcast Plugin, but didn’t find it in final(?) list of plugins in FOG 1.2.0.


  • Senior Developer

    You would need udp broadcast enabled on your network, but directing it would remove the need for this plugin entirely.

    I don’t know why you need an arp entry in firewall. WOL is layer 2. If you’re able to ping to all the “Subnet’s” you should be able to specify the broadcast address of that particular subnet.



  • Buuuuuut it doesn’t work :(
    Doe’s this plugin requires some kind of network configuration?
    For example, create and ARP entry for address (ex.192.168.5.254) or firewall entry for 9 port.
    Or maybe i do something wrong on installation step?
    [CODE]
    Installation Type: Normal Server
    Server IP Address: 192.168.70.10
    DHCP router Address: 192.168.70.1
    DHCP DNS Address: 192.168.70.1
    Interface: eth0
    Using FOG DHCP: 0
    [/CODE]

    I think i need to configure ip directed broadcast.



  • [quote=“Tom Elliott, post: 39444, member: 7271”]Yes it really can solve this issue.
    It’s really pretty simple. I hope this helps explain it.
    /quote]
    [/quote]
    Thx for explanation c:


  • Senior Developer

    [quote=“BrHubbard, post: 39438, member: 27298”]
    So, the WOL Plugin really can solve this problem?
    How it works?! Please, tell me in a few words?
    Really interesting c:[/quote]

    Yes it really can solve this issue.

    It works by Sending a WOL packet for the machine across all of the broadcast addresses you set in the page.

    You only need to specify two items. The name (for your own sanity) you want it to show up as, and the Broadcast address of the ip-range you’re trying to get WOL to work on.

    So, let’s say you have 7 VLAN’s.

    10.9.X.X
    10.8.X.X
    10.7.X.X
    10.6.X.X

    You’ve set them up to a class b network (255.255.0.0)

    Your broadcast address for all involved networks would be:
    10.9.255.255
    10.8.255.255
    10.7.255.255
    10.6.255.255

    If your FOG Server lives 10.6.X.X, you don’t need to make an entry for 10.6.255.255, you’d only need to make one on the other three, though it shouldn’t hurt to have all four just in case.

    WOL Will first send to broad cast 255.255.255.255 (it’s own network’s broadcast).

    Then it will send the packet to the broadcast addresses specified by you effectively sending the packets to the proper network directly.

    So the order of how WOL now works:

    for each broadcast address and it’s own, send the packet.

    It’s really pretty simple. I hope this helps explain it.

    In further terms. If you’ve setup all four broadcast addresses. FOG Will send packet to each of the broadcast addresses starting with it’s own. So it will send to:

    255.255.255.255 Sent here first
    10.9.255.255 sent in order of how it’s entered
    10.8.255.255 sent in order of how it’s entered
    10.7.255.255 sent in order of how it’s entered
    10.6.255.255 sent in order of how it’s entered



  • [quote=“VincentJ, post: 39425, member: 8935”]Are you just asking about the WOL or are you having problems with imaging as well>[/quote]
    [SIZE=13px][FONT=Tahoma][COLOR=#141414] [/COLOR][/FONT][/SIZE]
    Only with WOL.
    Imaging works great if i run PC by myself (of course, because PXE works with L3).

    [quote=“Tom Elliott, post: 39428, member: 7271”]WOL plugin is part of the svn version of fog and it will likely only work on svn and forward. Mostly because I’ve made a lot of work advancing the power of hooks and plugins which required a lot of internal changes. If you are daring you could try upgrading to svn. While its always recommended to not use svn in production environments, I do work fairly hard to keep production quality operations. If you need this functionality to operate its really your best course of action.[/quote]
    So, the WOL Plugin really can solve this problem?
    How it works?! Please, tell me in a few words?
    Really interesting c:


  • Senior Developer

    WOL plugin is part of the svn version of fog and it will likely only work on svn and forward. Mostly because I’ve made a lot of work advancing the power of hooks and plugins which required a lot of internal changes. If you are daring you could try upgrading to svn. While its always recommended to not use svn in production environments, I do work fairly hard to keep production quality operations. If you need this functionality to operate its really your best course of action.


  • Moderator

    Are you just asking about the WOL or are you having problems with imaging as well>


Log in to reply
 

340
Online

39.3k
Users

11.0k
Topics

104.4k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.