03-25-2008
ipv6 routing
I am trying to capture the ipv6 packets through pcap utility.
For that i am redirecting the ipv6 packets to the loopback address , but the ipv6 packets are not getting redirected to tha loopback address.Instead they are taking there normal routes.
8 More Discussions You Might Find Interesting
1. IP Networking
Hello guyz..
did some of u have implement or making a testbed for IPv6?
if yes, can u attached the procedures and standard guidelines because i really need for my proposal..
thanx.. (2 Replies)
Discussion started by: unknown2205
2 Replies
2. SuSE
Hi gurus,
In a few month, we must enable IPv6 on our Linux Server!
Should we reinstall the Linux machine to enable IPv6 or could we just make some change in configuration's files?
Could Linux run simultaneous IPv4 and IPv6?
Thanks in advance for our help our ideas?
Best regards,
nm (3 Replies)
Discussion started by: hiddenshadow
3 Replies
3. Solaris
I am currently trying to setup static ipv6 address with a persistent default gateway. This is on a Solaris 10 non global zone running inside a Solaris 10 global zone. My production server I am comparing against is a Solaris 10 xen instance running on a Oracle Solaris xen instance.
I have got... (12 Replies)
Discussion started by: jpolachak
12 Replies
4. Red Hat
In our server routing ipv6 auth config IP and IPv6 routing got flushed out automatically.
Can some one help what could be the cause (0 Replies)
Discussion started by: dpmoorthy
0 Replies
5. HP-UX
my problem: i want to change from ipv4 to ipv6 on my home network.
On hpux i can assign only address non routable as fe80::1 fe80::3 etc to my lan0
Editing netconf-ipv6 i can assing a routable ipv6 address like
fd55:282f:3b98::/48
or
2001:470:26:307:89a0:aba1:f98b:eb3e
but only to alias... (0 Replies)
Discussion started by: Linusolaradm1
0 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I have created a bonding bond1 interface with 6 Eth , mode=4. Recently i have changed my old ipv6 to new one and tried to restart as well as reload network service. Post which i can see old as well as changed ipv6 in ifconfig command output. Below are few files and command output for your... (1 Reply)
Discussion started by: omkar.jadhav
1 Replies
7. IP Networking
I am trying to setup an IPv6 network.
I modified the interfaces file:
/etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback
iface etho0 inet static
address 2620:7:a000::1
netmask 64
gateway ::ffff:c0a8:101
... (0 Replies)
Discussion started by: Meow613
0 Replies
8. Solaris
Hello Dears ,
please I need your support I have Oracle Solaris 10 X86 server please if you can advise how can I add IP v6 on my server and if IPv6 was disabled how can i enable it also how can i add two IP (v4 and v6) on the same interface or I have to add another interface .
Thanks in... (1 Reply)
Discussion started by: ttashman
1 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 with the appropriate ioctl(2) commands for corresponding address families. 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 hardware 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
January 25, 2012 BSD