all ports on the switch are in the same vlan and these ports are working fine. when I try to deconnect hostA from switch and replace it by hostB on the same port, hostB can communicate with hostC (pings are working fine). so i think that the issue come from hostA network config.
I'm pinging IP address and not hostnames
Howto check if a ethernet interface is up?
It's impossible to determine via the ipaddress i have learned, or?
Can someone please give me a hint on howto do?
Environment == Linux x86 GNU GCC.
:D
regards
Esaia (2 Replies)
Installed a replacement 3com pci card on an ibm PC 300 GL, running OpenServer 6.0 , brought up system, and recieved this message:
Fsstat:/dev/boot mounted
Mounted /stand filesystem
System auditing is not enabled.
Dlpid:Unable to open network adapter driver (/dev/mdi/r8e0)
Dlpid:No such... (0 Replies)
Hi all,
Here im facing problem with NIC Interface with my X86 Version of Solaris Express, even after loading module for that Interface. So please check this below mentioned log for your use and get back to me ASAP.
- - - -- --... (0 Replies)
I need to install ethernet card drivers on intel machine. How can i know which Ethernet card interface (sfe,rh,rtls...) is it? How can i know the speed of that card? How can i know network traffic ? If network traffic is more with that interface what should i do?
Thanks in advance (2 Replies)
Hi All,
I want to configure network into my system.
i tried following in to configure the interface
to find the name of interface
#prtdiag |grep net
i got following
0 PCI-1 33 1 network-SUNW, hme
then i tried following
#prtconf -v |grep net
network, instance #0 (6 Replies)
Hi,
During the installation of solaris suppose I am configuring one ethernet interface that is primary but on my server there are 4 ethernet interfaces,because all other interface not configured,
what is way to find out how many ethernet interfaces are there on Server, (6 Replies)
This is my situation
DOS pc serial cable (sl0) Linux Pc eth1
192.168.0.10 <-------------------->192.168.0.2 <------------>192.168.0.1 (router)
I connected the linux pc and the dos pc with a SLIP (serial line internet protocol), so they can communicate in the sl0 interface.
... (3 Replies)
Hi,
is there any method to check the interface collisions on ethernet NIC in AIX. I know that in Solaris it's netstat -i but I've written that in AIX it doesn't show this.
Thanks®ards,
p (1 Reply)
Hello,
I am trying to set up Channel Bonding on a RHEL6 Virtual Box VM. I have 2 ethernet cards on the machine which are set up in Internal Network mode. I followed all the steps exactly as mentioned in the RHEL6 deployment Guide, but for some reason i think results are not correct. Here are my... (13 Replies)
Hi ,
Could someone let me know how to detect duplicate ip address after assigning ip address to ethernet interface using c program (3 Replies)
Discussion started by: Gopi Krishna P
3 Replies
LEARN ABOUT DEBIAN
sc_tracediff
SC_TRACEDIFF(1) BSD General Commands Manual SC_TRACEDIFF(1)NAME
sc_tracediff -- display traceroute paths where the path has changed.
SYNOPSIS
sc_tracediff [-a] [-m method] [-n] file1.warts file2.warts
DESCRIPTION
The sc_tracediff utility displays pairs of traceroutes to a destination where the path has changed. It takes two warts files as input and
displays paths where a hop differs by its address. The options are as follows:
-a dump all traceroute pairs regardless of whether they have changed.
-m method
specifies the method used to match pairs of traceroutes together. If dst is specified, traceroutes are matched if the destination IP
address of both traces are the same. If userid is specified, traceroutes are matched if the userid field of both traces are the
same. If dstuserid is specified, traceroutes are matched if the destination IP address and userid fields are the same. By default,
the destination IP address is used.
-n names should be reported instead of IP addresses, where possible.
sc_tracediff can be useful in network monitoring to identify when a forward IP path has changed. In this scenario, it is recommended that
Paris traceroute is used with the same UDP source and destination ports for each execution of scamper so that only paths that have changed
are identified, not merely alternate paths visible due to per-flow load-balancing. By default scamper uses a source port based on the
process ID, which will change with each execution of scamper.
EXAMPLES
The command:
scamper -O warts -o file1.warts -c 'trace -P udp-paris -s 31337' -f list.txt
collects the forward IP paths towards a set of IP addresses found in list.txt using 31337 as the UDP source port value. If the above command
is adjusted to subsequently collect file2.warts, then we can identify paths that have subsequently changed with the command:
sc_tracediff file1.warts file2.warts
If Paris traceroute with ICMP probes is preferred, then the following invocation of scamper is appropriate:
scamper -O warts -o file1.warts -c 'trace -P icmp-paris -d 31337' -f list.txt
In this case, scamper uses 31337 as the ICMP checksum value in each probe.
SEE ALSO scamper(1),
B. Augustin, X. Cuvellier, B. Orgogozo, F. Viger, T. Friedman, M. Latapy, C. Magnien, and R. Teixeira, Avoiding traceroute anomalies with
Paris traceroute, Proc. ACM/SIGCOMM Internet Measurement Conference 2006.
AUTHOR
sc_tracediff is written by Matthew Luckie <mjl@luckie.org.nz>.
BSD April 21, 2011 BSD