07-26-2009
Quote:
Originally Posted by
ilikecows
To connect the laptop to the Sun server directly to each other you would use a crossover cable.
Not really, you can use straight cables for E150.
Btw, have the problem got resolved?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Dear Reader,
I have a very unique problem. Quite often my on board ethernet port( hme0 ) related message is appearing in /var/adm/messages.
The message is hme0: babble.. The port is up and alive.
What does this message mean.. Is the on board port is about to fail??
Thanks in advance, (2 Replies)
Discussion started by: joseph_shibu
2 Replies
2. UNIX for Advanced & Expert Users
How do you configure more than one network on a single hme0 interface under SunOS? And why would you want to do this?
Thanx :)
-Michelle (1 Reply)
Discussion started by: Michelle1977
1 Replies
3. BSD
hi
I want to setup my cable modem under OpenBSD. I did not configure my network while installing the system.
When I type, I get
# ifconfig -a
lo0 : ....
...
...
rl0 : ....
...
...
vr0 : ...
...
...
I have two network cards (the machine will be a router).
I created... (1 Reply)
Discussion started by: fnoyan
1 Replies
4. Solaris
Hi all,
Is there any difference between a null modem cable or a modem cable ?
i assume that a null modem cable is a normal cable that i used from cpu serial ports to a modem for dialup.
please correct if i am wrong,
thks (2 Replies)
Discussion started by: waterbear
2 Replies
5. Solaris
Hi .....
My problem is that when i reboot the system i can't connect to the network because my ethernet ( hme0 ) is down , i must up it by ifconfig command
after reboot :
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask... (1 Reply)
Discussion started by: tt155
1 Replies
6. Solaris
I have a 420r server it boots up all of the network settings are correct, however the machines network connection is not working. Cant ping anything from it, cant ping it from another machine on the network.
If I ping 127.0.0.1 it says alive.
Is there a chance the network card has been... (2 Replies)
Discussion started by: alanj4
2 Replies
7. Solaris
Hi All,
1. modify /etc/default/login file as
make commented # console=
2.put my laptops ip at both
/etc/inet/ipnodes and /etc/host file
still i can login via telnet/ftp through a DB9-serial cable, but when i tried
through a lan stratight cable directly connected that machine... (7 Replies)
Discussion started by: mahadib
7 Replies
8. Solaris
Hi all,
really interesting thing I have encountered . So :
root@host4 # uname -a
SunOS host4 5.9 Generic_122300-31 sun4u sparc SUNW,Sun-Fire-880
root@host4 # scinstall -p
3.2
latest recommended patches applied ..all SUN cluster patches applied.
SUN cluster software installed without... (2 Replies)
Discussion started by: samar
2 Replies
9. Solaris
We are unable to ping from Sun Ultra 60 to Ultra 10 machine and vice versa. We are getting an error message Cable Link Down ?. It was working fine.
Troubleshooting steps taken.
1) Changed the IPaddresses on both machines 192.168.10.10 and 192.168.10.20. These machines connected through 8 port... (2 Replies)
Discussion started by: vijaykrishna
2 Replies
10. Red Hat
I am facing strange problem regarding hostname on my Linux(2.6.18-164.el5xen x86_64 GNU/Linux), the hostname changes if reboot with lan cable and with NO lan cable
Reboot with lan cable:
The hostname is ubunut
Unable to connect Oracle database using sqlplus some times database is not... (2 Replies)
Discussion started by: LinuxLearner
2 Replies
LEARN ABOUT DEBIAN
vde_over_ns
VDE_OVER_NS(1) General Commands Manual VDE_OVER_NS(1)
NAME
vde_over_ns - Steganographic cable over NS protocol for Virtual Distributed Ethernet
SYNOPSIS
vde_over_ns [-D] [-c server_address] [-s vde_plug] [-i ip.to.bi.nd] domain.name
DESCRIPTION
A vde_over_ns allows to connect two remote vde_switches through steganographic NS query/response datagrams. e.g.:
dpipe vde_plug /tmp/s1 = vde_over_ns tun.mydomain.vde
binds to udp port 53 and listen for incoming steganographic NS queries (server mode). All the traffic to/from stdout/stdin is redirected
to the client via ns responses.
creates a wire between two vde_switches (with sockets /tmp/s1 and /tmp/s2 respectively). This cable looses 10% of the packets in each
direction.
The same vde_over_dns server can be created using:
vde_over_ns -s /tmp/s1 tun.mydomain.vde
The syntax is almost identical for the client mode, except that to have a vde_over_ns client connect to that server, the -c server option
must be specified.
OPTIONS
-s vdeplug
If specified, the vde_over_ns will connect to the local vde socket vdeplug instead pf stdin/stdout, using the libvdeplug library.
-D Detach console and send the process to background.
-b ip.to.bind
The NS server will bind only to the specified ip, instead of any ip. Only valid in server mode (without -c)
-c server_addr
If specified, client mode is enabled. Vde_over_ns will try to send NS requests to server_addr. If not specified, server mode is
enabled by default.
NOTICE
Virtual Distributed Ethernet is not related in any way with www.vde.com ("Verband der Elektrotechnik, Elektronik und Informationstechnik"
i.e. the German "Association for Electrical, Electronic & Information Technologies").
SEE ALSO
vde_switch(1), vdeq(1). dpipe(1). unixterm(1).
AUTHORS
VDE_OVER_NS is a tool by Daniele Lacamera <root@danielinux.net>
VDE is a project by Renzo Davoli <renzo@cs.unibo.it>
based on nstx, a steganographic ns client/server software by:
Florian Heinz <sky@sysv.de>
Julien Oster <frodo@sysv.de>
Virtual Distributed Ethernet May 2, 2007 VDE_OVER_NS(1)