12-14-2001
You have to have modifications in the kernel to allow IP spoofing or similar mod. Linux does this in the kernel configuration file.
10 More Discussions You Might Find Interesting
1. IP Networking
I'm new to Solaris.
How do I set a server's IP address?
Thanks in advance. (3 Replies)
Discussion started by: confused
3 Replies
2. IP Networking
I have checkpoint firewall-1 running on a solaris 7 sparc box with two physical working networks interface cards hme0, qfe0,
(please note these are false addresses)
qfe0 = 195.111.222.178 internet ISP
hme0 = 172.19.12.58 /24 internal Lan which has a router to france on it
I want to... (3 Replies)
Discussion started by: hcclnoodles
3 Replies
3. Forum Support Area for Unregistered Users & Account Problems
I set up the email address for my account too late for it to be activated prior to the transmission of the activate message from unix.com. Can you resend that message? (2 Replies)
Discussion started by: Retson Retap
2 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. UNIX for Dummies Questions & Answers
Hello, I need to write a program which sets server's ip address, router, network mask. Program also should set if it is an internal or external ip. Maybe someone can help me ? Any information from u is very useful :b:
I stopped at .. :(
#!/bin/sh
A=`hostname -i`
echo "server ip address is $A"... (4 Replies)
Discussion started by: zagaruika
4 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. SuSE
I have a file on Suse Linux which is created in codepage 420. I need to FTP this file to a remote server with codepage 1256.
How do I specify in FTP that the source codepage is 420 instead of the Linux default? Is this possible with curl or any other ftp client on Linux. I don't see a... (2 Replies)
Discussion started by: tsdjim
2 Replies
9. Solaris
How to set gateway address to a particular interface? waht are the files need to update to make it permanent? (2 Replies)
Discussion started by: Naveen.6025
2 Replies
10. 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
MEM(4) Linux Programmer's Manual MEM(4)
NAME
mem, kmem, port - system memory, kernel memory and system ports
DESCRIPTION
/dev/mem is a character device file that is an image of the main memory of the computer. It may be used, for example, to examine (and even
patch) the system.
Byte addresses in /dev/mem are interpreted as physical memory addresses. References to nonexistent locations cause errors to be returned.
Examining and patching is likely to lead to unexpected results when read-only or write-only bits are present.
Since Linux 2.6.26, and depending on the architecture, the CONFIG_STRICT_DEVMEM kernel configuration option limits the areas which can be
accessed through this file. For example: on x86, RAM access is not allowed but accessing memory-mapped PCI regions is.
It is typically created by:
mknod -m 660 /dev/mem c 1 1
chown root:kmem /dev/mem
The file /dev/kmem is the same as /dev/mem, except that the kernel virtual memory rather than physical memory is accessed. Since Linux
2.6.26, this file is available only if the CONFIG_DEVKMEM kernel configuration option is enabled.
It is typically created by:
mknod -m 640 /dev/kmem c 1 2
chown root:kmem /dev/kmem
/dev/port is similar to /dev/mem, but the I/O ports are accessed.
It is typically created by:
mknod -m 660 /dev/port c 1 4
chown root:kmem /dev/port
FILES
/dev/mem
/dev/kmem
/dev/port
SEE ALSO
chown(1), mknod(1), ioperm(2)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux 2015-01-02 MEM(4)