Sponsored Content
Special Forums IP Networking Creating a printer emulator to capture PDL/PCL data coming in on port 9100. Post 302389077 by transistor on Friday 22nd of January 2010 02:32:37 PM
Old 01-22-2010
Thanks, Corona.

I tried using Windump - a port of tcpdump - to see if I could catch anything. I set it to listen for incoming on port 9100 but couldn't see anything. (I could see traffic if I listened for other devices on the LAN.) This caused me to think that the stream might be interactive.

Any other ideas? I'll mess around with tcpdump/Windump between to laptops and see if I can understand how it's supposed to work.

---------- Post updated at 07:32 PM ---------- Previous update was at 06:49 PM ----------

Right. Two XP laptops.

Source: 192.168.3.3, with a generic/text printer driver pointing to 192.168.3.4, port 9100.
Dest: 192.168.3.4 (Hohner) running WinDump. WinDump listening to port 9100.

Here's what I got when I try to print "Hallo World!" from Notepad on source machine ...

Code:
E:\windump>windump -i 2 -A -f -q -t -X port 9100
windump: listening on \Device\NPF_{8071A9D5-8999-472A-85C5-B1E55ABFFC9E}
IP 192.168.3.3.1982 > HOHNER.9100: tcp 0
        0x0000:  4500 0030 6b7d 4000 8006 07f3 c0a8 0303  E..0k}@.........
        0x0010:  c0a8 0304 07be 238c 7ebb 2438 0000 0000  ......#.~.$8....
        0x0020:  7002 ffff 2dee 0000 0204 0550 0101 0402  p...-......P....
IP 192.168.3.3.1983 > HOHNER.9100: tcp 0
        0x0000:  4500 0030 6b83 4000 8006 07ed c0a8 0303  E..0k.@.........
        0x0010:  c0a8 0304 07bf 238c 3334 eff4 0000 0000  ......#.34......
        0x0020:  7002 ffff adb7 0000 0204 0550 0101 0402  p..........P....

It keeps repeating this and the print queue on source machine never clears. It looks like the source is expecting a response from dest.

Any ideas how to spoof a response from the "printer"?
Am I mad?

Last edited by transistor; 01-22-2010 at 03:46 PM.. Reason: Improved clarity - I hope!
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

PCL Font does not download to printer.

OS: HP-UX B.11.11 U Printer: HP 8150. I require a font to be downloaded to the printer and used. As documented the steps are: 1. Tell printer to accept font 2. Send the font to the printer 3. Make the font permanent 4. Select font for use or in PCL 1. <Esc>*c90D 2.... (0 Replies)
Discussion started by: mbb
0 Replies

2. UNIX for Dummies Questions & Answers

Howto capture data from rs232port andpull data into oracle database-9i automatically

Hi, i willbe very much grateful to u if u help me out.. if i simply connect pbx machine to printer by serial port RS232 then we find this view: But i want to capture this data into database automatically when the pbx is running.The table in database will contain similar to this view inthe... (1 Reply)
Discussion started by: boss
1 Replies

3. UNIX for Advanced & Expert Users

Capture output to file and printer

Hi All : I wanted a unix command by which I could be able to print the output to a file and at the same time to a printer. Any help will be greatly appreciated. Regards, Ramamurthy Dasari (1 Reply)
Discussion started by: rdasari
1 Replies

4. SCO

Printer port

I installed an old laser printer using a print server. I can use from windows but not from unix. I set up the printer in unix as a remote printer and can ping the print server from a unix promt. I am thinking that I must open a port to the print server. Any suggestions? (3 Replies)
Discussion started by: owbf
3 Replies

5. Red Hat

Red hat 5. - PCL Printer

I need to setup a HP 4000 PCL printer - it seems out of the box - I can only can use PostScript. Any guidance is appreciated. In the SCO world - I used HPNP with no problems. (2 Replies)
Discussion started by: markb4
2 Replies

6. UNIX for Dummies Questions & Answers

Printing Landscape to PCL 6 Printer

I've looked around and am able to print landscape to a PCL 5 printer with this command: lp -o landscape -o cpi=20 -o page-right=30 -o page-left=30 -d <printer> <file>. Which gives me a nice 200 columns. But, when I send the same output and the same commands to a PCL 6 printer, it comes... (3 Replies)
Discussion started by: tariqjamal
3 Replies

7. Red Hat

Print Spooling using raw port 9100

Hello all, I need to setup a print server that listens on three separate network interfaces, and sends jobs to the corresponding print queue. Example: 192.168.69.100 - printer1 -> Out to 139.177.69.100:9100 192.168.69.101 - printer2 -> Out to 139.177.69.101:9100 192.168.69.102 - printer2 ->... (3 Replies)
Discussion started by: ZekesGarage
3 Replies

8. Solaris

Printer (lpadmin) error - blank pages PS/PCL

Help! I have to solve an urgent problem! I have a Solaris 10 server, where I created a line of printing with the command # /usr/sbin/lpadmin -p IL_Printer -s pv24002 -v /dev/null -m netstandard_foomatic -A write -n /usr/lib/lp/model/ppd/system/foomatic/Canon/cnl66e1.ppd.gz -o... (0 Replies)
Discussion started by: poyato
0 Replies

9. SCO

Printing to a working network printer using PCL

I am trying to get a network printer to work that currently works from my Unix (5.0.7) server when printing text files only. When I try to print post script files like a PDF file I get all of the controls so I am not sure if I have my printer configuration setup properly in Unix The printer... (1 Reply)
Discussion started by: ziggy6
1 Replies

10. Emergency UNIX and Linux Support

Port flow capture

I am trying to get an output using the command tcpdump -w /tmp/syn.pcap 'tcp & (tcp-syn) != 0' But I am getting the error: tcpdump: no suitable device found Is there an alternate command to achieve this? (4 Replies)
Discussion started by: ggayathri
4 Replies
CIDR(3pm)						User Contributed Perl Documentation						 CIDR(3pm)

NAME
Net::CIDR - Manipulate IPv4/IPv6 netblocks in CIDR notation SYNOPSIS
use Net::CIDR; use Net::CIDR ':all'; print join(" ", Net::CIDR::range2cidr("192.68.0.0-192.68.255.255", "10.0.0.0-10.3.255.255")) . " "; # # Output from above: # # 192.68.0.0/16 # 10.0.0.0/14 print join(" ", Net::CIDR::range2cidr( "dead:beef::-dead:beef:ffff:ffff:ffff:ffff:ffff:ffff")) . " "; # # Output from above: # # dead:beef::/32 print join(" ", Net::CIDR::range2cidr("192.68.1.0-192.68.2.255")) . " "; # # Output from above: # # 192.68.1.0/24 # 192.68.2.0/24 print join(" ", Net::CIDR::cidr2range("192.68.0.0/16")) . " "; # # Output from above: # # 192.68.0.0-192.68.255.255 print join(" ", Net::CIDR::cidr2range("dead::beef::/46")) . " "; # # Output from above: # # dead:beef::-dead:beef:3:ffff:ffff:ffff:ffff:ffff @list=("192.68.0.0/24"); @list=Net::CIDR::cidradd("192.68.1.0-192.68.1.255", @list); print join(" ", @list) . " "; # # Output from above: # # 192.68.0.0/23 print join(" ", Net::CIDR::cidr2octets("192.68.0.0/22")) . " "; # # Output from above: # # 192.68.0 # 192.68.1 # 192.68.2 # 192.68.3 print join(" ", Net::CIDR::cidr2octets("dead::beef::/46")) . " "; # # Output from above: # # dead:beef:0000 # dead:beef:0001 # dead:beef:0002 # dead:beef:0003 @list=("192.68.0.0/24"); print Net::CIDR::cidrlookup("192.68.0.12", @list); # # Output from above: # # 1 @list = Net::CIDR::addr2cidr("192.68.0.31"); print join(" ", @list); # # Output from above: # # 192.68.0.31/32 # 192.68.0.30/31 # 192.68.0.28/30 # 192.68.0.24/29 # 192.68.0.16/28 # 192.68.0.0/27 # 192.68.0.0/26 # 192.68.0.0/25 # 192.68.0.0/24 # 192.68.0.0/23 # [and so on] print Net::CIDR::addrandmask2cidr("195.149.50.61", "255.255.255.248")." "; # # Output from above: # # 195.149.50.56/29 DESCRIPTION
The Net::CIDR package contains functions that manipulate lists of IP netblocks expressed in CIDR notation. The Net::CIDR functions handle both IPv4 and IPv6 addresses. @cidr_list=Net::CIDR::range2cidr(@range_list); Each element in the @range_list is a string "start-finish", where "start" is the first IP address and "finish" is the last IP address. range2cidr() converts each range into an equivalent CIDR netblock. It returns a list of netblocks except in the case where it is given only one parameter and is called in scalar context. For example: @a=Net::CIDR::range2cidr("192.68.0.0-192.68.255.255"); The result is a one-element array, with $a[0] being "192.68.0.0/16". range2cidr() processes each "start-finish" element in @range_list separately. But if invoked like so: $a=Net::CIDR::range2cidr("192.68.0.0-192.68.255.255"); The result is a scalar "192.68.0.0/16". Where each element cannot be expressed as a single CIDR netblock range2cidr() will generate as many CIDR netblocks as are necessary to cover the full range of IP addresses. Example: @a=Net::CIDR::range2cidr("192.68.1.0-192.68.2.255"); The result is a two element array: ("192.68.1.0/24","192.68.2.0/24"); @a=Net::CIDR::range2cidr( "d08c:43::-d08c:43:ffff:ffff:ffff:ffff:ffff:ffff"); The result is an one element array: ("d08c:43::/32") that reflects this IPv6 netblock in CIDR notation. range2cidr() does not merge adjacent or overlapping netblocks in @range_list. @range_list=Net::CIDR::cidr2range(@cidr_list); The cidr2range() functions converts a netblock list in CIDR notation to a list of "start-finish" IP address ranges: @a=Net::CIDR::cidr2range("10.0.0.0/14", "192.68.0.0/24"); The result is a two-element array: ("10.0.0.0-10.3.255.255", "192.68.0.0-192.68.0.255"). @a=Net::CIDR::cidr2range("d08c:43::/32"); The result is a one-element array: ("d08c:43::-d08c:43:ffff:ffff:ffff:ffff:ffff:ffff"). cidr2range() does not merge adjacent or overlapping netblocks in @cidr_list. @netblock_list = Net::CIDR::addr2cidr($address); The addr2cidr function takes an IP address and returns a list of all the CIDR netblocks it might belong to: @a=Net::CIDR::addr2cidr('192.68.0.31'); The result is a thirtythree-element array: ('192.68.0.31/32', '192.68.0.30/31', '192.68.0.28/30', '192.68.0.24/29', [and so on]) consisting of all the possible subnets containing this address from 0.0.0.0/0 to address/32. Any addresses supplied to addr2cidr after the first will be ignored. It works similarly for IPv6 addresses, returning a list of one hundred and twenty nine elements. $cidr=Net::CIDR::addrandmask2cidr($address, $netmask); The addrandmask2cidr function takes an IP address and a netmask, and returns the CIDR range whose size fits the netmask and which contains the address. It is an error to supply one parameter in IPv4-ish format and the other in IPv6-ish format, and it is an error to supply a netmask which does not consist solely of 1 bits followed by 0 bits. For example, '255.255.248.192' is an invalid netmask, as is '255.255.255.32' because both contain 0 bits in between 1 bits. Technically speaking both of those *are* valid netmasks, but a) you'd have to be insane to use them, and b) there's no corresponding CIDR range. @octet_list=Net::CIDR::cidr2octets(@cidr_list); cidr2octets() takes @cidr_list and returns a list of leading octets representing those netblocks. Example: @octet_list=Net::CIDR::cidr2octets("10.0.0.0/14", "192.68.0.0/24"); The result is the following five-element array: ("10.0", "10.1", "10.2", "10.3", "192.68.0"). For IPv6 addresses, the hexadecimal words in the resulting list are zero-padded: @octet_list=Net::CIDR::cidr2octets("::dead:beef:0:0/110"); The result is a four-element array: ("0000:0000:0000:0000:dead:beef:0000", "0000:0000:0000:0000:dead:beef:0001", "0000:0000:0000:0000:dead:beef:0002", "0000:0000:0000:0000:dead:beef:0003"). Prefixes of IPv6 CIDR blocks should be even multiples of 16 bits, otherwise they can potentially expand out to a 32,768-element array, each! @cidr_list=Net::CIDR::cidradd($block, @cidr_list); The cidradd() functions allows a CIDR list to be built one CIDR netblock at a time, merging adjacent and overlapping ranges. $block is a single netblock, expressed as either "start-finish", or "address/prefix". Example: @cidr_list=Net::CIDR::range2cidr("192.68.0.0-192.68.0.255"); @cidr_list=Net::CIDR::cidradd("10.0.0.0/8", @cidr_list); @cidr_list=Net::CIDR::cidradd("192.68.1.0-192.68.1.255", @cidr_list); The result is a two-element array: ("10.0.0.0/8", "192.68.0.0/23"). IPv6 addresses are handled in an analogous fashion. $found=Net::CIDR::cidrlookup($ip, @cidr_list); Search for $ip in @cidr_list. $ip can be a single IP address, or a netblock in CIDR or start-finish notation. lookup() returns 1 if $ip overlaps any netblock in @cidr_list, 0 if not. $ip=Net::CIDR::cidrvalidate($ip); Validate whether $ip is a valid IPv4 or IPv6 address, or a CIDR. Returns its argument or undef. Spaces are removed, and IPv6 hexadecimal address are converted to lowercase. If $ip contains a "/", it must be a valid CIDR, otherwise it must be a valid IPv4 or an IPv6 address. A technically invalid CIDR, such as "192.168.0.1/24" fails validation, returning undef. BUGS
Garbage in, garbage out. Always use cidrvalidate() before doing anything with untrusted input. Otherwise, "slightly" invalid input will work (extraneous whitespace is generally OK), but the functions will croak if you're totally off the wall. AUTHOR
Sam Varshavchik <sam@email-scan.com> With some contributions from David Cantrell <david@cantrell.org.uk> perl v5.14.2 2012-05-01 CIDR(3pm)
All times are GMT -4. The time now is 06:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy