Sponsored Content
Operating Systems Solaris Getting Solaris machine into Network Post 302143525 by porter on Thursday 1st of November 2007 11:01:38 PM
Old 11-02-2007
What is your network configuration?

What network will your machine plug into?

Is there a DHCP server which dynamically allocates IP addresses?

Have you been told on an IP address you must use?

Are you on a network that is going through a NAT router?

How are names going to be resolved?

Which name server are you going to use?
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Machine names changing on network

Hello, this is my first post, and yeah, I'm quite new to UNIX, so please bare with me... My question has to do with a few Macs on a Windows network, but since the question is not OS X specific (I think) or Windows specific (I think), but rather UNIXish (I think) I chose to post here rather than... (3 Replies)
Discussion started by: fxj
3 Replies

2. Solaris

Best possible communication mechanism between a Solaris machine and a windows machine

hi, I have some windows client machines which require a signal to be sent by a Solaris machine( SunOS 5.6) when ever a particular event occurs on that Solaris machine. What are possible communication mechanisms by which i can do this. the constraints are > the windows machines have to... (7 Replies)
Discussion started by: Krsh
7 Replies

3. IP Networking

RSH to Ubuntu machine from Solaris machine?

This is probably really basic compared to what you guys are usually talking about here, but I have a problem and I have no idea what to do about it. I try to RSH to my Ubuntu computer from my Solaris one and run into a dead end: >> rsh 192.168.1.103 ::ffff:192.168.1.103: Connection timed out... (4 Replies)
Discussion started by: Bradj47
4 Replies

4. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies

5. UNIX for Dummies Questions & Answers

how to see network speed of virtual linux machine?

After installing PV (Para virtual drivers) drivers I m not able to check the network speed of my Ethernet port. Please check the output of mii-tool and ethtool. # mii-tool eth0 SIOCGMIIPHY on 'eth0' failed: Operation not supported # ethtool eth0 Settings for eth0: Link... (2 Replies)
Discussion started by: pinga123
2 Replies

6. Red Hat

How do I network a Suse installed machine with other computers, specifically Red hat Linux?

How do I network a Suse installed machine with other computers, specifically Red hat Linux? This is for a school project, and I can't find any pages that tell how to network a Suse to other computers except how to use a printer. (1 Reply)
Discussion started by: Anna Hussie
1 Replies

7. Solaris

Solaris ssh client hangs when connecting to another Solaris machine

Got a strange problem. I have 4 Solaris servers all configured the same, Solaris 10 x86 update 10. When I try to ssh from one Solaris 10 server to another server ssh hangs. I have an identical server and when I try this everything works fine. The weird thing is if I am root on the server... (1 Reply)
Discussion started by: ccj4467
1 Replies

8. Solaris

Network of Virtual machine not working

Hello, I have a problem. I have a server SPARC T3-1 with solaris 11 on the base. The server is working well. And then i did a virtual machine using again Solaris 11 to do this, but now my notwork on my virtual machine is not working anymore. There says that the network that i have created is... (11 Replies)
Discussion started by: keziacp
11 Replies

9. IP Networking

Finding lost machine on network trouble

Couldn't find my PC on network. Root of evil the was in bad patch-cable. (0 Replies)
Discussion started by: useretail
0 Replies
SLIRPVDE(1)						      General Commands Manual						       SLIRPVDE(1)

NAME
slirpvde - Virtual Distributed Ethernet-Slirp interface SYNOPSIS
slirpvde OPTIONS [ socketdir ] DESCRIPTION
slirpvde is a slirp interface for a VDE network. Slirpvde connects all the units (virtual or real machines) to the network of the host where slirpvde runs as it were a NAT/Masquerading router. The default route is the node 2 (10.0.2.2 in the default network configuration) and DNS is re-mapped in node 3 (10.0.2.3). Slirpvde runs using standard user privileges (no need for root access): all the connections are re-generated by slirpvde itself. IPv4 only. IPv6 is still unsupported (will be supported when slirpvde will be rewritten using the LWIPv6 network stack). OPTIONS
-s, --sock, --socket, --vdesock, --unix directory specify the VDE switch directory (default /var/run/vde.ctl). The VDE switch directory can be also specified at the end of the com- mand, as illustrated by the optional parameter socketdir in the synopsis section, above. When '-' is used in place of the VDE switch directory, slirpvde works as a plug (see vde_plug(1)). The command: dpipe vde_plug = ssh remote.machine.org slirpvde - which is the same as: dpipe vde_plug = ssh remote.machine.org slirpvde -s - connects the default local switch to a remote slirpvde. -p, --pidfile filename specify the name of the file which contains the PID of slirpvde. -g, --group group specify the UNIX group for the VDE communication socket. -m, --mod mode specify the octal UNIX permissions for the VDE communication socket. -P, --port port specify the port of the vde switch whern slirpvde must be connected. -d, --daemon detach from terminal and run slirpvde in background. -H, --host address [ / masklen ] specify the host address (default 10.0.2.2/24). This option automatically defines the network. e.g. -H 192.168.55.1 or: --host 10.1.2.3/16 The default value for masklen is 24. If the host part of the address is zero this option defines only the network. The default host addr is addr 2, the default dns proxy is 3. e.g. -H 10.1.0.0/16 defines the network only. The host address is 10.1.0.2 and the DNS proxy 10.1.0.3. -n, --network address [ / masklen ] specify the network address (default 10.0.2.0/24). Deprecated, it has been included for back compatibility only. It is an alias of -H, --host. -N, --dns address Specify the address of the dns server. If this is an address inside the slirp network, slirvde acts as a dns proxy on that address. The slirpvde dhcp server sends this dns address to the clients. By default this is the host number 3 in the slirpvde network. Using the default network it is 10.0.2.3. Warning: do not use the same address for host and dns. -D, --dhcp turn on the DHCP server for the network autoconfiguration of all the units connected to the VDE. It is possible to specify the start address assigned by the DHCP server as follows: --dhcp=10.1.1.44 DHCP assign addresses starting at host number 15 by default. Using the default network it starts from 10.0.2.15 -L port:vde_host:vde_hostport specifyes a TCP port redirection. All the TCP packets received by the host running slirpvde at port port will be forwarded to vde_host at port vde_hostport. -U port:vde_host:vde_hostport specifyes a UDP port redirection. All the UDP packets received by the host running slirpvde at port port will be forwarded to vde_host at port vde_hostport. -X vde_host[:display.[screen]]i redirect a X window screen of a virtual machine. Slirpvde gets the first unused X display on the host running slirpvde and redirects all the requests to vde_host. display and screen] must be specified when different from :0.0. -x port:unix_socket_path] redirect a port of the virtual router (usually 10.0.2.2) to a unix stream socket. It is used for example to redirect a X display of the hosting computer on the virtual network. e.g. -x6000:/tmp/.X11-unix/X0. (A suitable xhost configuration is needed (e.g. 'xhost local:'). -t, --tftp pathname slirpvde enables a tftp server sharing (read-only) the directory at pathname. -q, --quiet Quiet; do not write anything to standard output. 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), vde_plug(1), vde_plug2tap(1), dpipe(1). AUTHOR
VDE is a project by Renzo Davoli <renzo@cs.unibo.it>. This tool includes software developed by Danny Gasparovski: Slirp code is by Danny Gasparovsky. Bootp/DHCP code is by Fabrice Bellard. Virtual Distributed Ethernet June 15, 2008 SLIRPVDE(1)
All times are GMT -4. The time now is 02:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy