5 More Discussions You Might Find Interesting
1. SuSE
Hello,
I have a project that I have compiled on a number of linux systems including CentOS, Ubuntu, and Windows Cygwin. I am trying to build the project under SUSE 12.1. The make file runs allot of the way through, but then throws an error that an included file can't be opened.
This is the... (4 Replies)
Discussion started by: LMHmedchem
4 Replies
2. IP Networking
My router has UPnP,how to make it work with ubuntu to automatically open ports
I try to open the following command " /sbin/iptables -I INPUT -d 0/0 -s 0/0 -p tcp --dport 21 -j ACCEPT" ,local only opens ,if i put the ip 192.168.1.68, it works correctly, if i`m put my external ip does not work,I... (9 Replies)
Discussion started by: dhalus
9 Replies
3. UNIX for Dummies Questions & Answers
I set up remote printing on a clients Unix server to my Windows XP USB printer. My USB printer is connected directly to my PC (no print server and no network input on printer). With my Win XP PC connected to my cable modem (without the router), i can do
lp -dhp842c /etc/hosts and it prints. I... (7 Replies)
Discussion started by: jmhohne
7 Replies
4. SuSE
Does anybody who uses open SUSE 11.0?
I have used open SUSE 10.2 for about 18 months.
Today I installed open SUSE 11.0
The printer does not work. I tried all the tricks tweak it.
My printer is an old one. It is HP Deskjet 5600 series.
It works fine.
I did the configuration using... (0 Replies)
Discussion started by: Angelo
0 Replies
5. Programming
Okay, so here is some code that when compiled on Fedora Core 6 works great, but when I compile and run it on OpenSuse 10 it gives back a seg fault when trying to join the 2nd thead.
#include <pthread.h>
#include <stdio.h>
int print_message_function( void *ptr );
int x = 1;
main()
{
... (1 Reply)
Discussion started by: chrisdrobison
1 Replies
LEARN ABOUT OSF1
gateways
gateways(4) Kernel Interfaces Manual gateways(4)
NAME
gateways - Specifies Internet routing information to the routed daemon
SYNOPSIS
/etc/gateways
DESCRIPTION
The /etc/gateways file identifies gateways for the routed daemon. Ordinarily, the routed daemon queries the network and builds routing
tables. The routed daemon builds the tables from routing information transmitted by other hosts directly connected to the network. How-
ever, there may be gateways that this command cannot identify through its queries. These unidentified gateways are known as distant gate-
ways. Such gateways should be identified in the /etc/gateways file, which the routed daemon reads when it starts.
The general format of an file entry in the /etc/gateways file is: Destination Name1 gateway Name2 metric Value Type
The following is a brief description of each element in an /etc/gateways file entry: A keyword that indicates whether the route is to a
network or to a specific host. The two possible keywords are net and host. The name associated with Destination. Name1 can be either a
symbolic name (as used in the /etc/hosts or /etc/networks file) or an Internet address specified in dotted-decimal format. An indicator
that the following string identifies the gateway host. The name or address of the gateway host to which messages should be forwarded. An
indicator that the next string represents the hop count to the destination host or network. The hop count, or number of gateways, from the
local network to the destination network. A keyword that indicates whether the gateway should be treated as active, passive, or external.
The three possible keywords are as follows: An active gateway is treated like a network interface. That is, it is expected to exchange RIP
(Routing Information Protocol) routing information. Information about it is maintained in the internal routing tables as long as it is
active and is included in any routing information that is transmitted through RIP. If it does not respond for a period of time, the route
associated with it is deleted from the internal routing tables. A passive gateway is not expected to exchange RIP routing information.
Information about it is maintained in the routing tables indefinitely and is included in any routing information that is transmitted
through RIP. An external gateway is identified to inform the routed daemon that another routing process will install such a route and that
alternative routes to that destination should not be installed. Information about external gateways is not maintained in the internal rout-
ing tables and is not transmitted through RIP.
Note that these routes must be to networks.
EXAMPLES
To specify a route to a network through a gateway host with an entry in the gateways file, enter: net net2 gateway host4 metric 4 passive
This example specifies a route to a network, net2, through the gateway host4. The hop count metric to net2 is 4, and the gateway is
treated as passive. To specify a route to a host through a gateway host with an entry in the gateways file, enter: host host2 gate-
way host4 metric 4 passive
This example specifies a route to a host, host2, through the gateway host4. The hop count metric to host2 is 4, and the gateway is
treated as passive. To specify a route to a host through an active Internet gateway with an entry in the gateways file, enter: host
host10 gateway 192.100.11.5 metric 9 active
This example specifies a route to a specific host, host10, through the gateway 192.100.11.5. The hop count metric to host10 is 9 and
the gateway is treated as active. To specify a route to a host through a passive Internet gateway with an entry in the gateways
file, enter: host host10 gateway 192.100.11.5 metric 9 passive
This example specifies a route to a specific host, host10, through the gateway 192.100.11.5. The hop metric count to host10 is 9
and the gateway is treated as passive. To specify a route to a network through an external gateway, enter a line in the following
format: net net5 gateway host7 metric 11 external
This example specifies a route to a network, net5, through the gateway host7. The hop count metric to net5 is 11 and the gateway is
treated as external (that is, it is not advertised through RIP, but is advertised through an unspecified routing protocol).
RELATED INFORMATION
Daemons: gated(8), routed(8) delim off
gateways(4)