first of all here is my server config and client config to diskless boot
server:
2 lan nics (1 connected directly to modem, 1 as static 192.168.0.100, 255.255.255.0, no gateway)
running a virtualized pfsense server (bridge to the 2 nics, lan ip is 192.168.1.1, dhcp off in pfsense)
running opendhcp server (dhcp listens on 192.168.0.100)
running opentftpserver (listens on 192.168.0.100)
running both opendhcp and opentftpserver is just my little preference...
iscsi boot by gpxelinux (bootfile gpxelinux.0)
win7x64
dhcp settings on 192.168.0.100
range-192.168.0.200-192.168.0.250
subnet=255.255.255.0
router=192.168.0.1
nextserver=192.168.0.100
tftpserver=192.168.0.100
bootfilename=gpxelinux.0
(no static leases)
client
iscsi boot from 192.168.0.100
win7x86
my problem is this
although it is ok booting into windows, it does not have internet, because i need to have ip address
from pfsense virtual (192.168.1.x) but my dhcp boot leases ip address 192.168.0.x in order to boot from iscsi
now if i set my pfsense ip to 192.168.0.2 for example, my client wont be able to diskless boot, (on windows logo only)
once i have booted into windows and changing the ip manually to (192.168.1.x, gateway 192.168.1.1) it will
have internet connection, i need to automate this (see question 1)
ive research into the problem and guessing i have to learn relay agent, proxydhcp (which is i think is missing
from my setup) now here are my questions
1) how to configure dhcpserver to get bootp info from 192.168.0.x range (initial ip lease, router ip, from 192.168.0.x, BUT on normal ip lease gets ip from pfsense ip range (192.168.1.x)
2) do i need a relay agent? to route dhcp from 192.169.0.x and 192.168.1.x and vice versa?
3) do i need proxydhcp (no idea what it is, is it the same as the relay agent)?
4) do i need to have 2 dhcp running? (one from 192.168.0.1) and the other from pfsense virtualized?
please help...
Edited by tinoy69, 10 June 2016 - 09:50 AM.