Routing problem : two interfaces one gateway

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Inconsistency between RedHat 6.5 global gateway and single gateway leads to loss of default gateway

Dear friends I use RedHat 6.5, which sets the gateway in the configuration file / etc / sysconfig / network as GATEWAY = 192.168.1.26, and the gateway in the configuration file / etc / sysconfig / network-scripts / ifcfg-eth11 as GATEWAY = 192.168.1.256. The two gateways are different....

2. IP Networking

Network Interfaces Problem - Monitoring equipment

Dear gurus of Linux / Unix. I have a server, which I use to monitoring traffic, the problem that I find is when I run the following command: probe:~ # sar -n DEV 1 I see that I one second appear info in some interface and in the other second no appear, I don't know what will be the...

3. AIX

Problem with multiple network interfaces

Hi .. we have two AIX 5.3 systems with a small client server app communicating over a TCP socket. Box A has a single network interface where the server app (in Java) opens a well known port and waits for connections from Box B. Box B has two network interfaces, X and Y. Interface X has the...

4. Solaris

Routing problem

Hi, I have two physical interfaces on a servers. We have connected them to differerent subnets. 1) First interface: 10.158.49.87 to newtwork 10.158.49.0, its gateway is 10.158.49.1 (It is added as default gateway) It is existing set up. It works well 2) Second interface: ...

5. IP Networking

Problem when I Open my WireShark - No Interfaces Option available

Hi gurus of unix, I haved installed my openSolaris in a HP530, Recently I use the following command beadm destry opensolaris1 beadm destry opensolaris2 After That I reboot my Laptop. Well when I go to my work I try to open my wireshark tool, but the option in GUI interface does not appear!!!...

6. Debian

/etc/network/interfaces problem

Hello i am configuring a debian lenny sever ,/etc/network/interfaces is modified so that eth1 takes a static IP address then i save it wq! then i restart the networking , /etc/init.d/networking restart . but after reboot ,the file is reset ,note that the interfaces had by defauklt IPv6 address...

7. Linux

GNUGK-How to setup static gateway to gateway routing

Dear Sir I am a newbie in the world of IP telephony. I have been working with Asterisk PBX (SIP) and Cisco Call Manager (MGCP) but now I am learning on how to work GNUGK for H.323 Gatekeeper. I am having a problem, configuring static call routing on GNUGK in the section ...

8. Linux

Routing via several interfaces for hosted virtual machines

My setup consists of a hardware node, which hosts several virtual machines (OpenVZ, to be precise). The hardware node has two network interfaces (<ifA>, <ifB>) connected to different subnets (<networkA>, <networkB>). I want to route the traffic of certain VEs over <ifB> while routing the other VEs...

9. SCO

Network interfaces problem

Hi, I have problems with my SCO unix network interfaces. Intel integrated adapter was failing, so I installed new one - 3COM adapter into free PCI slot. Installed driver using SCO Software manager - successfully Added new Network adapter using SCO Network configuration manager - successfully...

10. IP Networking

Network interfaces problem

LEARN ABOUT DEBIAN

atalkd

ATALKD(8)							   Netatalk 2.2 							 ATALKD(8)

NAME

       atalkd - AppleTalk RTMP, NBP, ZIP, and AEP manager

SYNOPSIS

       atalkd [-f configfile] [-1] [-2]

DESCRIPTION

       atalkd is responsible for all user level AppleTalk network management. This includes routing, name registration and lookup, zone lookup,
       and the AppleTalk Echo Protocol (similar to ping(8)).  atalkd is typically started at boot time, out of /etc/rc. It first reads from its
       configuration file, /etc/netatalk/atalkd.conf. If there is no configuration file, atalkd will attempt to configure all available interfaces
       and will create a configuration file. The file consists of a series of interfaces, one per line. Lines with `#' in the first column are
       ignored, as are blank lines. The syntax is

       interface [ -seed ] [ -phase number ] [ -net net-range ] [ -addr address ] [ -zone zonename ] ...

       Note that all fields except the interface are optional. The loopback interface is configured automatically. If -seed is specified, all
       other fields must be present. Also, atalkd will exit during bootstrapping, if a router disagrees with its seed information. If -seed is not
       given, all other information may be overriden during auto-configuration. If no -phase option is given, the default phase as given on the
       command line is used (the default is 2). If -addr is given and -net is not, a net-range of one is assumed.

       The first -zone directive for each interface is the ``default'' zone. Under Phase 1, there is only one zone. Under Phase 2, all routers on
       the network are configured with the default zone and must agree.  atalkd maps ``*'' to the default zone of the first interface. Note: The
       default zone for a machine is determined by the configuration of the local routers; to appear in a non-default zone, each service, e.g.
       afpd, must individually specify the desired zone. See also nbp_name(3).

ROUTING

       If you are connecting a netatalk router to an existing AppleTalk internet, you should first contact your local network administrators to
       obtain appropriate network addresses.

       atalkd can provide routing between interfaces by configuring multiple interfaces. Each interface must be assigned a unique net-range
       between 1 and 65279 (0 and 65535 are illegal, and addresses between 65280 and 65534 are reserved for startup). It is best to choose the
       smallest useful net-range, i.e. if you have three machines on an Ethernet, don't chose a net-range of 1000-2000. Each net-range may have an
       arbitrary list of zones associated with it.

EXAMPLES

       Below is an example configuration file for a sun4/40. The machine has two interfaces, ``le0'' and ``le1''. The ``le0'' interface is
       configured automatically from other routers on the network. The machine is the only router for the ``le1'' interface.

	      le0
	      le1 -seed -net 9461-9471 -zone netatalk -zone Argus

       atalkd automatically acts as a router if there is more than one interface.

FILES

       /etc/netatalk/atalkd.conf configuration file

BUGS

       On some systems, atalkd can not be restarted.

SEE ALSO

       atalkd.conf(5)

Netatalk 2.2							    06 Sep 2004 							 ATALKD(8)

IP Networking