You have two options to connect the printer to the Raspberry, via LAN or USB. Either should work, you don't need to install drivers if you generate the print jobs elsewhere.

There are many options to make the printer available.

• Samba and CUPS is one option, but it might be overkill for a single printer. With Samba, you can also install Windows drivers on the Raspberry and have Windows clients download them automatically.
• You can use just CUPS. CUPS can accept jobs with LPD, you configure the client to transfer the jobs to the CUPS LPD server that will send them to the printer.
• You can just have a process listen on port 9100 and send the data to the printer, without queuing.
• You can set up the Raspberry as a bridge between LAN and WLAN.
• If you already have a WLAN router or WLAN access point with LAN you can connect your printer to that LAN, the router or access point will act as a bridge between LAN and WLAN.

You have two options to connect the printer to the Raspberry, via LAN or USB. Either should work, you don't need to install drivers if you generate the print jobs elsewhere.

There are many options to make the printer available.

• Samba and CUPS is one option, but it might be overkill for a single printer. With Samba, you can also install Windows drivers on the Raspberry and have Windows clients download them automatically.

• You can use just CUPS. CUPS can accept jobs with LPD, you configure the client to transfer the jobs to the CUPS LPD server that will send them to the printer.

• You can just have a process listen on port 9100 and send the data to the printer, without queuing.

• You can set up the Raspberry as a bridge between LAN and WLAN.

• If you already have a WLAN router or WLAN access point with LAN you can connect your printer to that LAN, the router or access point will act as a bridge between LAN and WLAN.

• Use NAT to forward the printer connection from the Raspberry to the printer.

    iptables -t nat -A PREROUTING -i wlan0 -p tcp --dport 9100 -j DNAT --to-destination printer
  

You have two options to connect the printer to the Raspberry, via LAN or USB. Either should work, you don't need to install drivers if you generate the print jobs elsewhere.

There are many options to make the printer available.

• Samba and CUPS is one option, but it might be overkill for a single printer. With Samba, you can also install Windows drivers on the Raspberry and have Windows clients download them automatically.
• You can use just CUPS. CUPS can accept jobs with LPD, you configure the client to transfer the jobs to the CUPS LPD server that will send them to the printer.
• The simple option is to just have a process listen on port 9100 and send the data to the printer, without queuing.

You have two options to connect the printer to the Raspberry, via LAN or USB. Either should work, you don't need to install drivers if you generate the print jobs elsewhere.

There are many options to make the printer available.

• Samba and CUPS is one option, but it might be overkill for a single printer. With Samba, you can also install Windows drivers on the Raspberry and have Windows clients download them automatically.
• You can use just CUPS. CUPS can accept jobs with LPD, you configure the client to transfer the jobs to the CUPS LPD server that will send them to the printer.
• You can just have a process listen on port 9100 and send the data to the printer, without queuing.
• You can set up the Raspberry as a bridge between LAN and WLAN.
• If you already have a WLAN router or WLAN access point with LAN you can connect your printer to that LAN, the router or access point will act as a bridge between LAN and WLAN.