01-13-2011
Bumping up posts or double posting is not permitted in these forums.
Please read the
rules, which you agreed to when you registered, if you have not already done so.
You may receive an infraction for this. If so, don't worry, just try to follow the rules more carefully. The infraction will expire in the near future
Thank You.
The UNIX and Linux Forums.
Continue here:
solaris routing between two networks
8 More Discussions You Might Find Interesting
1. IP Networking
hi,
below is the situation:
my server is in 128.10.200.xxx network.
i have a solaris computer running in a subnet. this computer got 2 nic card.
1 is 172.18.198.xxx , another 1 is 10.100.xxx.11
there is a machine stick with this computer, ip is 10.100.xxx.12
so, 10.100.xxx.11 and... (3 Replies)
Discussion started by: kyhah
3 Replies
2. Solaris
Does anyone know how to delete a an ip off the routing table ? i tried route delete 10.0.0.0 and gateway but it still comes back. i have 2 zones sharing one interface. help... (4 Replies)
Discussion started by: 23patrick
4 Replies
3. IP Networking
hi all,
how do i make sure that the new routing should take effect on the os memory right away? what should i run after i add all the new "route add ....".
I have an example below:
bash-2.03# netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface... (1 Reply)
Discussion started by: itik
1 Replies
4. Solaris
Hi,
I got problem of Sun Solaris 8 routing.
IP of SunA is 10.16.64.164, and have routing table:
10.16.64.0 10.16.64.164 U 1 19236 bge1
10.6.0.0 10.6.0.3 U 1 16534 bge0
224.0.0.0 10.6.0.3 U 1 ... (4 Replies)
Discussion started by: milo
4 Replies
5. Solaris
I have a SUN ultra 5 machine running Solaris 6. it has two ethernet interfaces qe0 192.168.0.111 and qe1 192.168.1.111
the two subnets are 192.168.0.111 255.255.255.0
192.168.1.111 255.255.255.0
the specified routes are
add route -net 192.168.0.0 255.255.255.0 192.168.0.111
add route... (3 Replies)
Discussion started by: adol65
3 Replies
6. Solaris
ce0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2
inet 10.162.212.132 netmask ffffff00 broadcast 10.162.212.255
ether 0:14:4f:55:82:9
ce1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3
inet 10.231.11.232 netmask... (3 Replies)
Discussion started by: busyboy
3 Replies
7. Ubuntu
Hi everyone,
Hopefully there is someone here that can help me with the problem I got.
At my office I have 1 ubuntu firewall/gateway and several networks.
On the firewall/gateway I have three network cards, one for internet, one for network 192.168.100.0 and one for network 172.20.1.0
We... (0 Replies)
Discussion started by: thbor83
0 Replies
8. Solaris
Hello All,
Problem is that redundancy doesn't work, probably a routing issue I need to get sorted out When 172.29.11.x net is down, neither node3 nor node4 is trying 172.29.12.x network,The problem lies in network 172.29.13.x
if 172.29.11.x network is down, node3/node4 should route to... (6 Replies)
Discussion started by: nadeemahmed
6 Replies
LEARN ABOUT V7
ppmtosixel
ppmtosixel(1) General Commands Manual ppmtosixel(1)
NAME
ppmtosixel - convert a portable pixmap into DEC sixel format
SYNOPSIS
ppmtosixel [-raw] [-margin] [ppmfile]
DESCRIPTION
Reads a portable pixmap as input. Produces sixel commands (SIX) as output. The output is formatted for color printing, e.g. for a DEC
LJ250 color inkjet printer.
If RGB values from the PPM file do not have maxval=100, the RGB values are rescaled. A printer control header and a color assignment table
begin the SIX file. Image data is written in a compressed format by default. A printer control footer ends the image file.
OPTIONS
-raw If specified, each pixel will be explicitly described in the image file. If -raw is not specified, output will default to com-
pressed format in which identical adjacent pixels are replaced by "repeat pixel" commands. A raw file is often an order of magni-
tude larger than a compressed file and prints much slower.
-margin
If -margin is not specified, the image will be start at the left margin (of the window, paper, or whatever). If -margin is speci-
fied, a 1.5 inch left margin will offset the image.
PRINTING
Generally, sixel files must reach the printer unfiltered. Use the lpr -x option or cat filename > /dev/tty0?.
BUGS
Upon rescaling, truncation of the least significant bits of RGB values may result in poor color conversion. If the original PPM maxval was
greater than 100, rescaling also reduces the image depth. While the actual RGB values from the ppm file are more or less retained, the
color palette of the LJ250 may not match the colors on your screen. This seems to be a printer limitation.
SEE ALSO
ppm(5)
AUTHOR
Copyright (C) 1991 by Rick Vinci.
26 April 1991 ppmtosixel(1)