05-23-2011
Hi jim,
sorry for not updating this post.
TCP issue was the problem!
Let me explain: the core network sends TCP packets with parameter Window=0 (this happens on process restart, still not clear why it restarts).
The AS handle such scenario in a standard manner: no more traffic toward the core NE.
This lead to some asserts in log files reporting disconnection from all the nodes.
Regards,
Evan
9 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Hello guys , i have a big big problem.
At the company that i work for there are like 4 pcs that are sending and recieving a lot of packets to the point that the network is down.
we think that it might be a virus, we run all the antivirus that you could posible think of and nothing so far.
... (2 Replies)
Discussion started by: josramon
2 Replies
2. SuSE
Hullo everyone,
I have recently installed SUSE 9.1 and attached it to my Network router (Actiontec 54Mbps Wireless DSL Gateway) but can't connect to the internet. It comes up with the following error message:
An error occurred while loading "http://www.yahoo.com":Timeout on server - connection... (2 Replies)
Discussion started by: sybella1
2 Replies
3. Slackware
I recently installed slackware 11 and have been very happy with it until I found out that some gnome related apps can cause gnome's network manager to alter the rc.init1 script by adding 3 lines to the script containing only the command, eth_up. This causes the script not to run properly and not... (1 Reply)
Discussion started by: djtrippin
1 Replies
4. Solaris
Hey. i have a SPARCstation 5 running solaris 8 and CDE,
i know this hardware is really old but its the only Solaris machine i can afford at this time, (Student) but im having a hard time getting it on the internet, im using a cable modem, andt DHCP IPv4, but i can`t get a connection, i have heard... (0 Replies)
Discussion started by: mads-nielsen
0 Replies
5. Solaris
Hi
I am trying to do a network install of Solaris 10 08_07 onto a Sunfire T2000. I have configured all my network-boot-arguments on the client server (named sundb1). I have installed my image of Solaris on my install server (sun1).
But when I try to install using
# boot net -s
I get the... (0 Replies)
Discussion started by: Bobby76
0 Replies
6. Solaris
recently I've setup a Solaris 10 box & am having network disruption, e.g. disconnects, interrupted pings, etc) when I
connect to it from another machine, how should I troubleshoot this !
The machine is a x86 box with 3 NICs (Differnet providors). The Current NIC is a Intel Gigabit, which is... (4 Replies)
Discussion started by: stevie_velvet
4 Replies
7. SCO
SCO unix 5.0.5 - Suddently network lost & has to be reboot. I try to stop TCP & start TCP. but no connection. Any idea about that.
thanks (8 Replies)
Discussion started by: ajantha
8 Replies
8. SCO
hello, i am new to unix and need support</SPAN></SPAN>
</SPAN></SPAN>The problem is:
I have a SCO 5.0.5 server, and has no local network access, I think my problem are the drivers for network card.
my network card is Kingston EtheRx PCI Fast Ethernet Adapter KNE120TX and already installed the... (9 Replies)
Discussion started by: daniel_cie
9 Replies
9. UNIX for Advanced & Expert Users
i need help, i will always accord mine if my scope allows me, help me in this one..
am running vmware 7.0 in winserver 2008 on a cq61-425el, my network driver is installed correctly. and my vmware network drivers have added as well (in the device manager section).
During installation i wasnt... (0 Replies)
Discussion started by: baitz
0 Replies
FAITH(4) BSD Kernel Interfaces Manual FAITH(4)
NAME
faith -- IPv6-to-IPv4 TCP relay capturing interface
SYNOPSIS
device faith
DESCRIPTION
The faith interface captures IPv6 TCP traffic, for implementing userland IPv6-to-IPv4 TCP relay like faithd(8).
Each faith interface is created at runtime using interface cloning. This is most easily done with the ifconfig(8) create command or using
the cloned_interfaces variable in rc.conf(5).
Special action will be taken when IPv6 TCP traffic is seen on a router, and the routing table suggests to route it to the faith interface.
In this case, the packet will be accepted by the router, regardless of the list of IPv6 interface addresses assigned to the router. The
packet will be captured by an IPv6 TCP socket, if it has the IN6P_FAITH flag turned on and matching address/port pairs. As a result, faith
will let you capture IPv6 TCP traffic to some specific destination addresses. Userland programs, such as faithd(8) can use this behavior to
relay IPv6 TCP traffic to IPv4 TCP traffic. The program can accept some specific IPv6 TCP traffic, perform getsockname(2) to get the IPv6
destination address specified by the client, and perform application-specific address mapping to relay IPv6 TCP to IPv4 TCP.
The IN6P_FAITH flag on a IPv6 TCP socket can be set by using setsockopt(2), with level IPPROTO_IPV6 and optname IPv6_FAITH.
To handle error reports by ICMPv6, some ICMPv6 packets routed to an faith interface will be delivered to IPv6 TCP, as well.
To understand how faith can be used, take a look at the source code of faithd(8).
As the faith interface implements potentially dangerous operations, great care must be taken when configuring it. To avoid possible misuse,
the sysctl(8) variable net.inet6.ip6.keepfaith must be set to 1 prior to using the interface. When net.inet6.ip6.keepfaith is 0, no packets
will be captured by the faith interface.
The faith interface is intended to be used on routers, not on hosts.
SEE ALSO
inet(4), inet6(4), faithd(8)
Jun-ichiro itojun Hagino and Kazu Yamamoto, An IPv6-to-IPv4 transport relay translator, RFC3142.
HISTORY
The FAITH IPv6-to-IPv4 TCP relay translator first appeared in the WIDE hydrangea IPv6 stack.
BSD
April 10, 1999 BSD