04-22-2014
Packet forwarding to network stack
hello All,
I am not heavily conversant with *nix, so few of you may find the question to be naive.
Question : Will *nix Kernel process packets not originating from a loopback interface, but received on a loopback interface?
Scenario:
I have an application running which can strip packets of encapsulation , now once the packet is just IPv4 packet , I am trying to reprogram this application to hand over the packet-payload(IPV4 packet) back to network stack for IP routing.
How can I get this done?
Can I create a sockets to loopback interface and send the packet-payload(IPV4 packet) to the loopback interface? Will the kernel accept such packets to originating from loopback interface and still process it?
---------- Post updated 04-22-14 at 03:37 PM ---------- Previous update was 04-21-14 at 09:11 PM ----------
Bumping the thread , in hope of help
8 More Discussions You Might Find Interesting
1. IP Networking
Hi,
My small network consists of a mail server(postfix) and 2 clients.
I want to configure the clients so that all the mail they send is sent through the mailserver. I want to forward all outgoing mail to the mail server.
How should I configure the clients to achieve this?
Thanks for... (1 Reply)
Discussion started by: hjallebk
1 Replies
2. Cybersecurity
Hi,
from my workplace we use a proxy to connect to the outside world, including external ssh servers.
The problem is that the server is seeing the connection coming from the proxy and knows nothing about the client behind it. The ssh connection itself works fine, but x-forwarding does not work as... (1 Reply)
Discussion started by: vampirodolce
1 Replies
3. HP-UX
how to get network packet size
I would like get network output rate(kb/sec)
I type command "netstat -i"
Ipkts Ierrs Opkts Oerrs 653387 0 678202 0
but i didn't know what is it packet size ,
how could i get it? (1 Reply)
Discussion started by: alert0919
1 Replies
4. IP Networking
Hi all,
I am working on TUN/TAP for tunnelling IP packets from the application to the network.
I am able to open the tun device and assign the IP address to tun0. The steps I followed are given,
1. Opened the tun device /dev/net/tun
2. Assigned a IP address to the tun0 using ifconfig... (5 Replies)
Discussion started by: johnniealan
5 Replies
5. HP-UX
Hello,
I'm writing to you because I encountered the following problem. My program displayes all network interfaces that are available in the system, but I would like to add a functionality in which a user can enter a destination address IP (ex. the IP address of the Google search engine) and will... (1 Reply)
Discussion started by: foxrafi
1 Replies
6. SCO
Hi everybody
My SCO 5.0.2 OpenServer got its kernel corruptions and network stack was accicentially deleted. I would like to know if we have any chance to rebuild its kernel and network stack.
Any help will be great thankfully appreciate
TN (1 Reply)
Discussion started by: TinhNhi
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am new to the linux kernel development area. I want to know what is the difference between kernel mode stack and user mode stack? Does each process has a user mode stack and a kernel mode stack?? Or Each process has a user mode stack and there is only one kernel mode stack that is shared by... (4 Replies)
Discussion started by: saurabhkoar
4 Replies
8. AIX
(5 Replies)
Discussion started by: Vishal_dba
5 Replies
LEARN ABOUT OPENDARWIN
lo
LO(4) BSD Kernel Interfaces Manual LO(4)
NAME
lo -- software loopback network interface
SYNOPSIS
pseudo-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.
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
intro(4), inet(4), ns(4)
HISTORY
The lo device appeared in 4.2BSD.
BUGS
Previous versions of the system enabled the loopback interface automatically, using a nonstandard Internet address (127.1). Use of that
address is now discouraged; a reserved host address for the local network should be used instead.
4.2 Berkeley Distribution June 5, 1993 4.2 Berkeley Distribution