P910nd is a simple network print server. You can use it instead of CUPS or Samba to share an attached printer with both Linux and Windows clients. Install the PET attached below. There are 32bit and 64bit versions. The PETs include a control panel applet for managing the P910nd print server. Find it in the System menu.

Check out the auto-start script /root/Startup/910nd-start. It contains the line

Code:

p910nd -f /dev/usb/lp0 0

This starts the print server daemon. It listens on Port 9100 for incoming print jobs and sends them directly to the USB printer connected at /dev/usb/lp0.

Initially, the startup script is disabled. To start the print server, run the P910nd Control Panel from the System menu.

As usual, the Puppy firewall may interfere with the operation of P910nd.

--------------------------------------------

Setting up a Client Printer under Linux

Hint: On a client machine, run PeasyPort and check that Port 9100 is open on the server.

1. Open the CUPS web interface.
2. Select Add Printer.
3. Under Device, select AppSocket/JetDirect (P910nd printers are NOT auto-detected by CUPS)
4. Under Connection, enter the following URI, using the IP address of the server:

Code:

socket://aaa.bbb.cc.dd:9100

5. Select the printer Make and Model as usual. If a driver package like hplip_print is needed, you must first install it on the client machine.

---------------------------------------------

Setting up a Client Printer under Windows XP

1. Start the Add Printer Wizard
2. Select Local Printer (even though it's not)
3 Select New Port > standard TCP/IP
4. Enter the IP address of the server and change the port name to something descriptive.
5. There will now be a pause while Windows tries to find the printer, but cannot.
6. Select Custom > Settings
7. Select Raw and enter the port number 9100.
8. Install the printer driver
9. Check the printer's properties and verify the port configuration.

---------------------------------------------

Be aware that if the server's IP address changes, clients will lose their connection to the shared printer. There are two solutions:

1. Assign the server a fixed IP address. (If you have Windows clients, this may be your best choice.)

2. Add an entry to the client's /etc/hosts file containing the server's current IP address and a descriptive name, like

Code:

192.168.2.15 Deskjet-F4280-Bedroom

Then create the printer in CUPS as

Code:

socket://Deskjet-F4280-Bedroom:9100

If the server's IP address changes, you need only update the client's host file. For a quick way to do this, check out the IP4CUPS tool.

--------------------

The Control Panel has two sections. Use the Server section on the computer that has the attached printer and is running the P910nd server.

You can optionally install the P910nd package on other computers. Use the Client section to manage a computer's own CUPS printers, either attached or remote.

I am new in Linux. There is only file udev.conf , but not directory (if this is a directory) rules.d in /etc/udev.

My question is probably stupid - is it possible to create this directory and copy there text file containing rules (p910nd.rules)? Is it possible in Oleg firmware I am using?

Or I have to flash firmware with OpenWRT, which is real Linux for embedded devices? I am afraid that this step will be difficult for me, since there are required very good knowledges of Linux.

I found this script, see http://wl500g.info/showthread.php?t=14959 - (description is in Cyrillic, best viewed using encoding Cyrillic (Windows-1251)). But I would like use (if possible in Oleg on Asus WL 500G Premium) rules made by member rcrsn51.

Regarding to first question. Yes, I know WL 500gP has already built-in printserver. I am searching for solving my problem - that is how to operate two printers at the same time (the first one is ancient parallel printer-photocopier Minolta DiAlta Di152 connected using parallel-to-USB adapter, the second one is Samsung SCX 4725 FN with damaged network card) a few months. Almost everywhere is stated usage p910nd:

If you cannot get it working using udev, there may be another way. By looking at the system logs, you can tell which printer connected first. Then you could launch p910nd in the correct order. I will look at this.

[Edit] Here is a little script you can put in usr/local/sbin/post-boot. It looks at the system messages and determines which device node was assigned to each printer. It then runs the appropriate p910nd command.

I have thoroughly checked system. There is no directory rules.d even in /usr/local/etc/udev/rules.d. And sorry, in /etc/udev is file usb.switchingmode.conf not the udev.conf as I wrote above.

I copied your script with my product IDs to usr/local/sbin/post-boot, saved using flasffs save && flashfs commit && flashfs enable and then reboot. But this resulted in printing only on the second printer on 9101 port. I tried to change everything, in Windows printers settings (all client PCs are powered by Windows XP), also tried make your script in post-boot as executable using chmod +x /usr/local/sbin/post-boot (but I think it´s not good, or yes?).

In the attachment System Log of the router. I tried to print on first printer (port 9100, pid 2305), printedout on the second. And now sorry, when tried on the second one (port 9101, pid 341F), no print, no items in the System Log.

There is a mess with lp0 and lp1. I will get you all info about system, if you need.

If you don't run your post-boot script and plug in one printer, does the router automatically start it? If so, we are causing a conflict by trying to start it a second time. Maybe you need to stop the first printer before running the script. Add this line at the start

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum