LTSP on Vlans Pfsense

doguibnu

Hello! @stephenw10
How are you?

So, I would you like to show you more screenshots.
I Believe that we will win this way network hehehe. Still not works, but there are different results.

Please, see these screen

And here, the client LTSP screenshot. Now appear it seeing the server and try run the image server. But, there is some wrong thing:

This client has old NIC onboard!

Thanks Steve!

Douglas

stephenw10

Ok, so that's mostly working. It is getting the values via DHCP, initiating the PXE boot and is correctly fetching the boot file from the tftp server.
What appears to be wrong is that it's trying to boot the wrong file. Though there is no actual error shown there, I'm just assuming it doesn't boot further than that.

Steve

A Former User

On the lan pfsense the project works great, but with Vlan, not!

First question is why there is another DHCP set up on the server?

In normal you will be setting up it in the following order:

Setting up the VLANs and a IP range inside of the VLANs
pfSesen is routing then the entire VLAN traffic and this also inside one and between all the other VLANs (firewall rules)
pfSense is routing the entire WAN traffic and the LAN switch it self is routing between the VLANs (Switch ACLs)

If so, the vlans owns their own DHCP range and ip net
each for it self. So why the Server is also offering via DHCP?

doguibnu

Hello @Dobby_

@dobby_ said in LTSP on Vlans Pfsense:

On the lan pfsense the project works great, but with Vlan, not!

First question is why there is another DHCP set up on the server? The configuration is:

ltsp dnsmasq --proxy-dhcp=0

that means the ltsp server is not set up dhcp server

Site Installation LTSP

So no, there is not another DHCP set up on the LTSP server,

The last try we have this screenshot:

Pfsense :

And Ltsp Client:

But, after try the boot process, the client boot alone and can not up server image.

Lets go!

Thank you!

In normal you will be setting up it in the following order:

Setting up the VLANs and a IP range inside of the VLANs

pfSesen is routing then the entire VLAN traffic and this also inside one and between all the other VLANs (firewall rules)

pfSense is routing the entire WAN traffic and the LAN switch it self is routing between the VLANs (Switch ACLs)

If so, the vlans owns their own DHCP range and ip net
each for it self. So why the Server is also offering via DHCP?

stephenw10

Is that the last thing you see?

It's pulling the ipxe file and booting it correcetly. Usually ipex will then try to boot something else.

doguibnu

Hello!

@stephenw10 said in LTSP on Vlans Pfsense:

Is that the last thing you see?

Yes, after this, the client reboot alone.

It's pulling the ipxe file and booting it correcetly. Usually ipex will then try to boot something else.

so! I am lost. I am trying to works well a long time. I can not find the right way to fix the issue.
Thanks

stephenw10

I would guess that ipxe is trying to boot something else and failing to find it. You can see it's trying to reach https://ipxe.org/28086011 but what it expects to find there is unclear.
Maybe it needs some additional dhcp parameters to know what to do next.

doguibnu

@stephenw10 said in LTSP on Vlans Pfsense:

I would guess that ipxe is trying to boot something else and failing to find it. You can see it's trying to reach https://ipxe.org/28086011 but what it expects to find there is unclear.

 https://ipxe.org/28086011

this is an issue ipxe after "googling" about, but still not clear for me where go to fix this.

Maybe it needs some additional dhcp parameters to know what to do next.

So, I am trying follow isc dhcp
My ltsp server on proxmox, so add one more NIC to try boot up as the site tell about. But, still not fix it!

stephenw10

Right so it may need all those ipxe parameters configured so that ipxe knows what to do once it boots.

aaronouthier

@doguibnu
I suspect the url mentioned is a place to go for help with the error, not a url being accessed during the boot process.

If memory serves (it’s been many years since I’ve done ltsp), after the bios file is loaded via tftp, the initramfs file is loaded via nfs.

First step here, however, would be to go to the client machine, and load a local os (from the hard drive or a flash drive, etc - not via netboot), and attempt to manually load the file in question via tftp. If it loads, then the file exists on the ltsp server and is accessible.