07-23-2001
It is hard to believe that the Darwin kernel (OS X) cannot be configured forward IP packets.
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is there a way that i can create some start up disks for a computer with no hard drive to become a router? I know there are types of Linux OS's that can do it but i dont know which ones they are or where i can get them from. I am very new to the UNIX/Linux thing so I thank you for any help. (2 Replies)
Discussion started by: e980238
2 Replies
2. SCO
Hi,
I am trying to setup an old SCO Unix 2.x box to act as a router. I have got 2 network cards in the box. As far as I know, I need to setup "ip forwarding" and "routes". Can anyone tell me how to setup "ip forwarding" on SCO Unixware 2.X? (0 Replies)
Discussion started by: sreenir
0 Replies
3. Shell Programming and Scripting
Hi,
I want to write a script in unix for my routers which will collect the output to a file..
how do i do that?
thanks in advance (3 Replies)
Discussion started by: pasandhu
3 Replies
4. Programming
Hello everyone,
After 8 years of being out of school I am trying to start my Masters degree. This specific type of degree is being done only by research (research mode vs. coursework mode). I need to prepare a research proposal and send it to the school. I will need a professor to accept me as a... (2 Replies)
Discussion started by: wmac
2 Replies
5. UNIX for Dummies Questions & Answers
dear all,
hi... my name rian,
i have some problem here, i'm trying to make router on UNIX machine, is there anyone know how to make it....... :confused: please let me know about the step.... thanks before..
cheers
Rian (2 Replies)
Discussion started by: afriansyah
2 Replies
6. 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
LO(4) BSD Kernel Interfaces Manual LO(4)
NAME
lo -- software loopback network interface
SYNOPSIS
device loop
DESCRIPTION
The loop interface is a software loopback mechanism which may be used for performance analysis, software testing, and/or local communication.
As with other network interfaces, the loopback interface must have network addresses assigned for each address family with which it is to be
used. These addresses may be set or changed with the SIOCSIFADDR ioctl(2). The loopback interface should be the last interface configured,
as protocols may use the order of configuration as an indication of priority. The loopback should never be configured first unless no hard-
ware interfaces exist.
If the transmit checksum offload capability flag is enabled on a loopback interface, checksums will not be generated by IP, UDP, or TCP for
packets sent on the interface.
If the receive checksum offload capability flag is enabled on a loopback interface, checksums will not be validated by IP, UDP, or TCP for
packets received on the interface.
By default, both receive and transmit checksum flags will be enabled, in order to avoid the overhead of checksumming for local communication
where data corruption is unlikely. If transmit checksum generation is disabled, then validation should also be disabled in order to avoid
packets being dropped due to invalid checksums.
DIAGNOSTICS
lo%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was
dropped.
SEE ALSO
inet(4), intro(4)
HISTORY
The lo device appeared in 4.2BSD. The current checksum generation and validation avoidance policy appeared in FreeBSD 8.0.
BSD March 15, 2009 BSD