Sponsored Content
Full Discussion: vnc4server on debian
Top Forums UNIX for Dummies Questions & Answers vnc4server on debian Post 302518282 by hachik on Friday 29th of April 2011 06:35:16 AM
Old 04-29-2011
Thanks, really helped,
The problem was that uname -n returns 127.0.1.1 bind hostname, and when I added entry in my /etc/hosts with same hostname to real ipv4, then it worked.

However, Interesting thing is that still only tcp6 listen...
$ netstat -an | grep 5901
tcp6 0 0 :::5901 :::* LISTEN

And established connection is also ipv6
tcp6 0 0 192.168.10.1:5901 192.168.10.100:17823 ESTABLISHED
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

debian help

ok -- i've got the main install done, but when it goes to set up apt, i can't get to an http or ftp server to get the packages. seems my dns isn't working. problem is -- i have no way, or at least don't know a way, to get into any sort of gui, in which i think i could get it going myself. i'm stuck... (1 Reply)
Discussion started by: aenemated
1 Replies

2. Debian

Networking in Debian

I've recently installed the Sarge version of Debian Linux and have run into a problem with it's networking abilities. I access the internet by cable modem, connected to a linksys broadband router. The router is set up to allow full access to this computer. When I run dhclient from Debian, it... (0 Replies)
Discussion started by: Losie
0 Replies

3. UNIX for Dummies Questions & Answers

command for debian OS

Hi All, I am unable to find the command for knowing the RAM size on debian os. Also i am unable to use the command shutdown on command line. it asks for the following options: cloud9:~# shutdown Usage: shutdown time -a: use /etc/shutdown.allow ... (6 Replies)
Discussion started by: gauri
6 Replies

4. Debian

Debian Help

It says that these files should be written to a floppy: Studenten Net Twente - Index of /debian/dists/etch/main/installer-i386/current/images/floppy/ How would all of those fit onto a floppy? Could I write a CD instead? (8 Replies)
Discussion started by: Bradj47
8 Replies

5. UNIX for Advanced & Expert Users

Debian becomes slow!

Hi all, I've a debian 4 etch machine which runs on a HP Proliant G5 server. My server became too slow yesterday. I restarted the it and also try to run in Run Level 1 but nothing changed. This is the status of my debian box: top - 12:33:11 up 34 min, 3 users, load average: 0.00, 0.03, 0.21... (2 Replies)
Discussion started by: mjdousti
2 Replies

6. Debian

Can't see anything after debian loads

Hey, I recently installed Debian on a desktop PC but when it starts I can't see anything (the monitor say no signal). I don't have any idea or even a way to figure out what going on here since I can't see anything at all not even the console. Is there something that I missed in the install, or is... (22 Replies)
Discussion started by: neur0n
22 Replies

7. Debian

Debian SPARC

Hello, Anyone already tried to install Debian Sparc in a Sun V880 ?! I'm trying to and after I boot it with the CDROM the system starts to boot up and I don't see any errors message but it freezes after it detects the USB ports (There is nothing attached to it and I don't use it). Here is a... (8 Replies)
Discussion started by: pxb368@motorola
8 Replies

8. Debian

Can't Login to Debian 8.1

I installed Debian 8.1:cool: with Xubuntu as dual boot :D... During installation of Debian 8.1 i skipped user account creation :confused: ...now i can't login to Debian 8.1 :(:eek: ..help... (1 Reply)
Discussion started by: Zorion10
1 Replies

9. Debian

Need to upgrade Debian 7.8 to Debian 8.5 (Not 8.5)

Hello, I need to upgrade my Debian system 7.8 to 8.5 but by default via apt-get It moves to 8.6 version(latest stable version). I'm new to Debian so didn't figure out the solution. I've checked few suggestions over internet like editing apt source list file using snapshot archive. Please... (2 Replies)
Discussion started by: Mannu2525
2 Replies
routeadm(1M)															      routeadm(1M)

NAME
routeadm - IP forwarding and routing configuration SYNOPSIS
routeadm [-p] routeadm [-R root-dir] [-e option...] [-d option...] [-r option...] [-s var=value] routeadm [-u] The routeadm command is used to administer system-wide configuration for IP forwarding and routing. IP forwarding is the passing of IP packets from one network to another; IP routing is the use of a routing protocol to determine routes. routeadm is used to enable or disable each function independently, overriding any system default setting for each function. The first usage, above, reports the current configuration. The following command-line options are supported: -p Print the configuration in parseable format. -R root-dir Specify an alternate root directory where routeadm applies changes. This can be useful from within JumpStart scripts, where the root directory of the system being modified is mounted elsewhere. Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). -e option... Enable the specified option. -d option... Disable the specified option. -r option... Revert the specified option to the system default. The system defaults are specified in the description of each option. -u Apply the currently configured options to the running system. Enable or disable IP forwarding, and/or launch or kill routing daemons. It does not alter the state of the system for those settings that have been set to default. This option is meant to be used by adminis- trators who do not want to reboot to apply their changes. -s var=value Specify string values for specific variables in a comma-separated list with no intervening spaces. If invalid options are specified, a warning message is printed and the program exits. The following variables can be specified: ipv4-routing-daemon=<full_path_to_routing_daemon> Specifies the routing daemon to be started when ipv4-routing is enabled. The routing daemon specified must be an executable binary or shell-script. Default: "/usr/sbin/in.routed" ipv4-routing-daemon-args=<args> Specifies the startup arguments to be passed to the ipv4-routing-daemon when ipv4-routing is enabled. Default: no arguments ipv4-routing-stop-cmd=<command> Specifies the command to be executed to stop the routing daemon when ipv4-routing is disabled. <command> may be an executable binary or shell-script, or a string that can be parsed by system(3C). Default: "kill -TERM `cat /var/run/in.routed.pid`" ipv6-routing-daemon=<full_path_to_routing_daemon> Specifies the routing daemon to be started when ipv6-routing is enabled. The routing daemon specified must be an executable binary or shell-script. Default: "/usr/lib/inet/in.ripngd" ipv6-routing-daemon-args=<args> Specifies the startup arguments to be passed to the ipv6-routing-daemon when ipv6-routing is enabled. Default: "-s" ipv6-routing-stop-cmd=<command> Specifies the command to be executed to stop the routing daemon when ipv6-routing is disabled. <command> can be an executable binary or shell-script, or a string that can be parsed by system(3C). Default: "kill -TERM `cat /var/run/in.ripngd.pid`" Note that, if you change the routing daemon and stop commands from their defaults, routeadm does not monitor these daemons or commands. This is because the status of these programs depends on user configuration. When non-default daemons or stop commands are in use, routeadm always returns a status of "unknown". Multiple -e, -d, and -r options can be specified on the command line. Changes made by -e, -d, and -r are persistent, but are not applied to the running system unless routeadm is called later with the -u option. Use the following options as arguments to the -e, -d, and -r options (shown above as option...). ipv4-forwarding Controls the global forwarding configuration for all IPv4 interfaces. The system default is disabled. If enabled, IP will forward IPv4 packets to and from interfaces when appropriate. If disabled, IP will not forward IPv4 packets to and from interfaces when appropriate. ipv4-routing Determines whether or not an IPv4 routing daemon is run. The system default is enabled unless the /etc/defaultrouter file exists, in which case the default is disabled. The routing daemon for IPv4 is /usr/sbin/in.routed. ipv6-forwarding Controls the global forwarding configuration for all IPv6 interfaces. The system default is disabled. If enabled, IP will forward IPv6 packets to and from interfaces when appropriate. If disabled, IP will not forward IPv6 packets to and from interfaces when appropriate. ipv6-routing Determines whether or not an IPv6 routing daemon is run. The system default is disabled. The routing daemon for IPv6 is /usr/lib/inet/in.ripngd. If not set, the system boot scripts' current default logic determines whether or not to run in.ripngd. Note that even if this option is enabled, an IPv6 routing daemon will run only if ipv6-forwarding is enabled. The forwarding and routing settings are related but not mutually dependent. For example, a router will typically forward IP packets and use a routing protocol, but nothing would prevent an administrator from configuring a router that forwards packets and does not use a routing protocol. In that case, the administrator would enable forwarding, disable routing, and populate the router's routing table with static routes. The forwarding settings are global settings. Each interface also has an IFF_ROUTER forwarding flag that determines whether packets can be forwarded to or from a particular interface. That flag can be independently controlled by means of ifconfig(1M)'s router option. When the global forwarding setting is changed (that is, -u is issued to change the value from enabled to disabled or vice-versa), all interface flags in the system are changed simultaneously to reflect the new global policy. Interfaces configured by means of DHCP automatically have their interface-specific IFF_ROUTER flag cleared. When a new interface is plumbed by means of ifconfig(1M), the value of the interface-specific forwarding flag is set according to the cur- rent global forwarding value. Thus, the forwarding value forms the "default" for all new interfaces. The following exit values are returned: 0 Successful completion. !=0 An error occurred while obtaining or modifying the system configuration. Example 1: Enabling IPv4 Forwarding IPv4 forwarding is disabled by default. The following command enables IPv4 forwarding: example# routeadm -e ipv4-forwarding Example 2: Apply Configured Settings to the Running System In the previous example, a system setting was changed, but will not take effect until the next reboot unless a command such as the follow- ing is used: example# routeadm -u Example 3: Making a Setting Revert to its Default To make the setting changed in the first example revert to its default, enter the following: example# routeadm -r ipv4-forwarding example# routeadm -u Example 4: Starting in.routed with the -q Flag The following sequence of commands starts in.routed with the -q flag: example# routeadm -s ipv4-routing-daemon-args="-q" example# routeadm -u See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ ifconfig(1M), in.routed(1M), gateways(4), attributes(5) 8 Apr 2005 routeadm(1M)
All times are GMT -4. The time now is 08:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy