Sponsored Content
Operating Systems Linux Red Hat About the apache for ipv6 configuration Post 303019070 by rbatte1 on Friday 22nd of June 2018 12:28:22 PM
Old 06-22-2018
Two questions:-
  • What does netstat -na | grep LISTEN | grep 80 show?
  • Do you have an IPv6 address allocated? What do you get as output for ip a s ?

You may have it already available.

Please wrap all code, files, configurations, data, input & output/errors in CODE tags. It makes it easier to read, preserves spacing for indenting/fixed-width data and stops interpreting text as links, smileys, email addresses etc.



Robin

Last edited by rbatte1; 06-22-2018 at 01:31 PM.. Reason: Added second question.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

apache configuration

Hi. I run openbsd and apache 1.3.29 PHP/4.3.9 mod_perl/1.29 DAV/1.0.3 mod_ssl/2.8.16 OpenSSL/0.9.7c anyway,problem is i have in httpd.conf allow override all in /dir1 and 2 directories /dir1/.htaccess is AuthType Basic AuthName "Password Required" AuthUserFile /passwords/password.file... (1 Reply)
Discussion started by: hachik
1 Replies

2. Solaris

Apache Configuration issue on Solaris

I seem to have an issue with Apache configurationon our Sun solaris Server. Since there are 2 my_app instances running in parallel, the perl modules in my_app_perl_libs are getting shared between them, even though they are in different directories (/u01/my_app and /u01/my_app8). This is because... (1 Reply)
Discussion started by: rahulrathod
1 Replies

3. Web Development

Apache Configuration File

I am new in Linux configure Apache. I got few questions to ask. I am will grateful for the help. Thanks. 1) In the Apache Configuration File, where is actually the base for the web tree? 2) I wanted to create a directory (called java) inside the base of the web tree. How am I going to do... (5 Replies)
Discussion started by: newlinuxuser
5 Replies

4. Solaris

Solaris 19 10/09 ipv6 interface configuration

Hi, anyone has had experience in a static setting an IPv6 interface?, I'm trying accordance with the admin guide (ipv6 network configuration tasks), configure one interface in the server, actually i can do ping to my default gateway and access the Internet in IPv6, the specific point is however,... (3 Replies)
Discussion started by: pabloluja
3 Replies

5. Web Development

Need help on Apache configuration for redirecting URLS

I am extremely new to Apache httpd configuration. Can you please help here below is my requirement. If the URL match existing resource - return resource. If the URL doesn't match existing resource it should return index.html from the app root directory. Apps root directories are: 1.... (0 Replies)
Discussion started by: kar_333
0 Replies

6. Linux

Apache httpd configuration - Issues with APR

Hi I have tried setting up of Apache http server - httpd-2.4.25. During configuration, I understand it needs APR to be setup. Hence I have downloaded APR & APR-Util. Performed, tar xvfC apr-1.5.2.tar /root/httpd-2.4.25/srclib/apr What is happening is there is another directory... (1 Reply)
Discussion started by: videsh77
1 Replies

7. Shell Programming and Scripting

Apache configuration Automation based on location

Hi I need to find a way to automate the deployment of my apache configuration to a few servers. I make change frequently on apache/conf/... etc, and I usually do this manually by copying files to each servers(and country config path)and restart apache servers.Source file will be like... (1 Reply)
Discussion started by: naresh2389
1 Replies

8. UNIX for Advanced & Expert Users

Apache log rotate configuration

HI i was trying to configure logrotate for my apache server and it's not working properly. here is my lodrotate configuration /var/log/httpd/*log { daily missingok notifempty sharedscripts compress delaycompress postrotate /sbin/service httpd... (1 Reply)
Discussion started by: bentech4u
1 Replies

9. Red Hat

Apache log rotate configuration

HI i was trying to configure logrotate for my apache server and it's not working properly. Os: Red Hat 6 here is my lodrotate configuration /var/log/httpd/*log { daily missingok notifempty sharedscripts compress delaycompress postrotate ... (3 Replies)
Discussion started by: bentech4u
3 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 11:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy