12-18-2002
IP may be incorrect.
First I see what may be a discrepancy. You have 194.x.x.x defined and 195.x.x.x defined. That may be your problem right away. If not keep reading.
I recently had problems with my lan and a router in the company. I found that one of my problems was that my broadcast address was incorrect. You may need to open up that for your second IP. Something like 195.255.255.255 and your broadcast to be 255.0.0.0. or possibly move it one more octet to the right 195.111.255.255 and 255.255.0.0.
May not be it but I would check. Print your Ifconfig output for each lan card maybe that would help as well.
Also, you should have an interface for 195.222.222.222. you may have to do a route add gateway again for this. I see you did set it up as a gateway.
9 More Discussions You Might Find Interesting
1. IP Networking
Hi, does anybody know how to set the IP source address of an IP packet to be zero? The problem is that when you create a raw socket and set the IP_HDRINCL socket option, if you put the ip_src address to zero (INADDR_ANY) the kernel will automatically set the source address to the primary IP address... (2 Replies)
Discussion started by: developer
2 Replies
2. Solaris
Good Day,
I've remotely mounted a cdrom (no problems theere). The kicker is I can see the directories on the remote CD bout I can't see the files. What am I doing wrong? I'm logged in as root on both systems. All the permissions seem okay - what am I missing? Thanks (2 Replies)
Discussion started by: greg69
2 Replies
3. Solaris
Morning all,
I am attempting to load a package from a Solaris 8 CDROM.
This fails with the error :
"pkgadd: ERROR: unable to access pkgmap file </cdrom/ .........../SUNWlibC/pkgmap>
No changes were made to the system"
Any help would be appreciated
Andy (6 Replies)
Discussion started by: AndyD
6 Replies
4. IP Networking
Hi all,
I have some doubts in selecting the interface to transfer packets and receive the packets.
--> Multiple interfaces :
--------------------
1) 0.0.0.0 --------> wild card address.
2) x.x.x.x --------> valid address.(192.168.1.156)
3) ff.ff.ff.ff -------->... (0 Replies)
Discussion started by: vijaypdp2006
0 Replies
5. Solaris
Greetings Forumers!
I've been fighting a locale problem on a v490 running Solaris 10 u4 (8/07). When I login to the system, I get several "locale" error messages:
user1's password:
Last login: Wed May 26 2010 09:14:13 -0400 from system1
You have mail.
couldn't set locale correctly
couldn't... (0 Replies)
Discussion started by: bluescreen
0 Replies
6. Solaris
Hello,
is there any way to ping with source address on Solaris ? (3 Replies)
Discussion started by: marmellata
3 Replies
7. IP Networking
Hi,
I'm trying to set up a test bed where I can use a single machine to do some network packet captures between 2 different applications without needing a network connection.
I'm actually trying to do some SIP VoIP development, but for illustration purposes will use ping. I want:
ping 127.0.0.1... (0 Replies)
Discussion started by: racitup
0 Replies
8. IP Networking
Hello
I have a question about routing in MANET using Dynamic Source Routing protocol.
IN RFC4728 (DSR) in section "IP fields" of RREP (Route Reply) packet we have this:
ok.
I read in several books and also in rfc4728 that: when a source node (node that initiate route discovery process)... (1 Reply)
Discussion started by: acu281
1 Replies
9. AIX
Hi all
With the recent virus attacks we have been tasked with upgrading Samba to a "secure" version. Currently running 3.0.29a and looking to put the latest version down 4.6.5.
Being a lazy bod I have only ever installed this, a long time ago, when you could get it in BFF filesets. Have... (6 Replies)
Discussion started by: splattty
6 Replies
LEARN ABOUT NETBSD
networks
NETWORKS(5) BSD File Formats Manual NETWORKS(5)
NAME
networks -- Internet Protocol network name data base
DESCRIPTION
The networks file is used as a local source to translate between Internet Protocol (IP) network addresses and network names (and vice versa).
It can be used in conjunction with the DNS, as controlled by nsswitch.conf(5).
While the networks file was originally intended to be an exhaustive list of all IP networks that the local host could communicate with, dis-
tribution and update of such a list for the world-wide Internet (or, indeed, for any large "enterprise" network) has proven to be prohibi-
tive, so the Domain Name System (DNS) is used instead, except as noted.
For each IP network a single line should be present with the following information:
name network [alias ...]
These are:
name Official network name
network IP network number
alias Network alias
Items are separated by any number of blanks and/or tab characters. A ``#'' indicates the beginning of a comment; characters up to the end of
the line are not interpreted by routines which search the file.
Network number may be specified in the conventional dot (``.'') notation using the inet_network(3) routine from the IP address manipulation
library, inet(3). Network names may contain "a" through "z", zero through nine, and dash.
IP network numbers on the Internet are generally assigned to a site by its Internet Service Provider (ISP), who, in turn, get network address
space assigned to them by one of the regional Internet Registries (e.g. ARIN, RIPE NCC, APNIC). These registries, in turn, answer to the
Internet Assigned Numbers Authority (IANA).
If a site changes its ISP from one to another, it will generally be required to change all its assigned IP addresses as part of the conver-
sion; that is, return the previous network numbers to the previous ISP, and assign addresses to its hosts from IP network address space given
by the new ISP. Thus, it is best for a savvy network manager to configure his hosts for easy renumbering, to preserve his ability to easily
change his ISP should the need arise.
FILES
/etc/networks The networks file resides in /etc.
SEE ALSO
getnetent(3), nsswitch.conf(5), resolv.conf(5), hostname(7), dhclient(8), dhcpd(8), named(8)
Classless IN-ADDR.ARPA delegation, RFC 2317, March 1998.
Address Allocation for Private Internets, RFC 1918, February 1996.
Network 10 Considered Harmful, RFC 1627, July 1994.
Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy, RFC 1519, September 1993.
DNS Encoding of Network Names and Other Types, RFC 1101, April 1989.
HISTORY
The networks file format appeared in 4.2BSD.
BSD
November 17, 2000 BSD