Problem to bind to local ports on Fedora 13

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat Problem to bind to local ports on Fedora 13
# 1  
Old 11-17-2010
Problem to bind to local ports on Fedora 13

A problem with binding to local ports (22,23,80) in Fedora 13.
Ports look not used. sshd, webserver is not running.
I am using java remote connection manager. It is working fine with IE or Firefox in Windows with any user account.
With Fedora 13, it starts via Firefox with not root account and cannot bind to local ports.

I disabled SELinux, firewall, add a gui session user to the root group it doesn't help. If I start firefox as root and then run java remote connection manager via firefox it agains shows up a gui session user.

Please advice how to fix binding to local ports !
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

Local installation of package in Red Hat / Fedora Linux

Hi all, I have a requirement to install rpm package(*noarch.rpm) in local to a directory, ex /tmp/mydir. which steps I need to follow to install rpm package local to the directory only, not to the default directories. Please share me the link if the topic is already discussed. I tried few... (3 Replies)
Discussion started by: krbattu
3 Replies

2. Cybersecurity

[SELinux] Problem with Bind 9

Hi, I can not start named service: /etc/init.d/named start Iniciando named: Error in named configuration: zone default.domain/IN: loading from master file /home/admin/conf/dns/default.domain.db failed: permission denied zone default.domain/IN: not loaded due to errors.... (2 Replies)
Discussion started by: Anibal
2 Replies

3. Red Hat

local yum server on fedora 17

Hello friends I was creating local yum server from dvd but fedora 17 used pool method , i mean similar to debian for packages i.e a,b....z How can i create local yum server on fedora 17 like fedora 14,15,16 Any help Thanks (1 Reply)
Discussion started by: rink
1 Replies

4. Solaris

Can i bind to a local login terminal running using rsh or remotely

Hi Can i ask? I had multiple solaris workstation running and some local users using it. Is it possible to bind to the local user terminal or console he's using as if like the user well type and I can see it and what my typing in the local user see it also. Is it possible.. Thanks. (3 Replies)
Discussion started by: jao_madn
3 Replies

5. UNIX for Advanced & Expert Users

Bind Problem

Hi all, I've 2 Debian Etch (4) box used as ns1 and ns2 with BIND9. My domain name is something like this: subdomain.domain.com And I've 2 authorized DNS servers for the subdomain. I set this line in both of ns1 and ns2 (I.e. in ns1.subdomain.domain.com and ns2.subdomain.domain.com): cw ... (1 Reply)
Discussion started by: mjdousti
1 Replies

6. BSD

Problem with re-installing ports

Hello, I am fairly new at FreeBSD. I tried searching existing topics for a similar problem, but I found none :) I have a problem reinstalling apache22 which I had to remove in my troubleshooting with mysql. Since I've got MySQL working now (joy unbounded!) I now have the task of... (3 Replies)
Discussion started by: brightstorm
3 Replies

7. Linux

BIND problem in Fedora Core

Hi , I am facing a strange with BIND in Fedora Core 6. Here is the config for more info. #cat /etc/named.caching-nameserver.conf options { listen-on port 53 { any; }; directory "/var/named"; // dump-file "/var/named/data/cache_dump.db"; ... (3 Replies)
Discussion started by: narasimhulu
3 Replies

8. SuSE

Fedora 9 problem

I appeal to all those of you that have experience with Fedora 9 for help. I am trying to install a suite of software which tries to make changes to the /etc/dhcpd.conf file. After the changes have been made the dhcpd service will not start and the original conf file is restored. However dhcpd... (1 Reply)
Discussion started by: johnf
1 Replies

9. IP Networking

problem opening TCP ports

Please can somebody help me. I'm trying to open ports 999, 1982 and 1983 but am not having much luck. I used iptables -A INPUT -i eth0 -p tcp --sport 999 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A INPUT -i eth0 -p tcp --sport 1982 -m state --state NEW,ESTABLISHED -j ACCEPT iptables... (5 Replies)
Discussion started by: thehaapyappy
5 Replies

10. Shell Programming and Scripting

Perl DBI - Bind Parameters Problem

I have a SQL statement that includes a UNION that I can't get to work when I bind the parameters. (I am binding the parameters to prevent SQL injection.) Does anybody have any suggestion on how I can use a SQL statement that includes a UNION and bind the params? Code would be something like... (1 Reply)
Discussion started by: mh53j_fe
1 Replies
Login or Register to Ask a Question
gatling(1)						      General Commands Manual							gatling(1)

NAME
gatling - high performance file server SYNOPSIS
gatling [-hnvVtdDfFUlaEe] [-i bind-to-ip] [-p bind-to-port] [-T seconds] [-u uid] [-c dir] [-w workgroup] [-P bytes] [-O [f/]ip/port/regex] [-r redir-url] [-X timeout,sshd] DESCRIPTION
gatling is a HTTP and FTP server. It will export the current working directory to the world. Use -i 127.0.0.1 to only bind to a certain IP address. Use -p 81 to bind HTTP to a different TCP port than 80. Use -f -p 2100 to bind FTP to a different TCP port than 21. When running as non- root, the default ports are 8000 and 2121, respectively. Use -u nobody to run under a different UID than root. This is done after binding the server ports, so it is safe to use -u and still bind to port 80 -- in fact, it is recommended not to run gatling as superuser. Use -c /home/www to chdir and chroot to another directory than the current working directory. It is recommended to run gatling in a chroot environment to lessen the impact of possible future security problems. Use -P 2M to activate prefetching mode. Gatling will then make sure this much data is prefetched. This can reduce disk activity and improve throughput dramatically if your OS I/O scheduler is not state of the art and you are serving several large files from the same hard disk to different downloaders. Without prefetching, the disk will otherwise waste time moving the disk head between the two large files. Use -f to enable anonymous FTP (default) or -F to disable it. Use -U to disable uploads altogether (normally gatling will allow file uploads). Gatling only allows uploads to world writable directories to prevent accidental upload permission, and the files will not be world readable (use -a if you want them world readable). Gatling will only allow downloads of world readable files, that's why this switch is important. These options are only available if gatling is compiled with SUPPORT_FTP defined. Use -e to enable encryption support (https) or -E to disable it. These options are only available if gatling is compiled with SUP- PORT_HTTPS defined. Use -l to make gatling always ask for FTP passwords. Normally gatling does not, which confuses some stupid clients. This option makes gatling ask for (and ignore) a password. Use -d to enable directory index generation for HTTP (listing directories is always possible in FTP), -D to disable. It is harder to acci- dentally publish a document if the attacker can not find out the file name through directory listings. Use -t to enable transparent proxy mode. Normally, gatling will replace the port in Host: HTTP headers and FTP virtual host names with the actual port the connection arrived at. This is important for security (in case you have a secret intranet web site on port 81, which is blocked at the firewall). However, when using a firewall to redirect connections to gatling, it may make more sense to keep the ports from the HTTP Host: headers for virtual hosting. Use -v to enable virtual hosting mode, -V to disable it. Normally, when a HTTP connection asks for /foo.html and carries a "Host: www.fefe.de:80" header, gatling will chdir to "www.fefe.de:80". If "www.fefe.de:80" does not exist, gatling will chdir to "default". If this also does not exist, and neither -v or -V are given, gatling will serve "foo.html" from the current working directory. Specifying -v will make sure that no file is ever served from the current working directory, only from the virtual host directories or from default. Specifying -V means that gatling will not try to chdir at all and always serve from the current working directory. Use -T 600 to set the timeout for HTTP and FTP data connections to 10 minutes (600 seconds, default is 23 seconds). Use -f -T 600 to set the timeout for FTP control connections (default is 600 seconds). If you use -r http://master.example.com/ on mirror.example.com, and someone asks for a file that does not exist, gatling will not create a 404 error but a redirect to the same file on master.example.com. Use -X timeout,sshd to enable SSH passthrough mode. If someone connects on the SSL socket, but does not say anything for timeout (sane value: 2-10) seconds, then gatling will run an sshd in inetd mode with that socket. sshd is the full path name to sshd, plus the command line you want to give it, if any. gatling automatically appends -i, so use this for example for -u0 to disable DNS lookups. Use -O [flag/]ip/port/regex to enable proxy mode, also used for SCGI and FastCGI. To use the proxy mode, there has to be a ".proxy" file in the root of the virtual host it is meant for. Specify ip and port to point to your app server, and give a regex to match the URI. Note: the regex needs to match the full file name, so use the extension for matching. If no flags are given, HTTP proxying is used. Oth- erwise, flags specifies the proxying mode: Use S for SCGI and F for FastCGI mode. See README.php for an example. It is also possible to specify a Unix Domain socket, using the syntax --O [flag/]|filename|regex. Remember to put the argument in quotes when typing it in the shell. Gatling will not serve or list dotfiles unless they are aliased with :dotfile, e.g. to enable serving .dotfile, you have to ln -s .dotfile ":dotfile". SIGNALS
Sending gatling SIGHUP will make it close all the server sockets (so you can start a new gatling process with different options on the same ports). The old gatling process will continue serving the established connections until they are all finished. AUTHOR
Initially written by Felix von Leitner <felix-gatling@fefe.de>. LICENSE
GPLv2 (see http://www.gnu.org/copyleft/gpl.html) with an exception to allow linking against openssl. gatling(1)