Login or Register to Ask a Question and Join Our Community


Red Hat

SSH broke and network traffic / talking issue between hosts and server

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat SSH broke and network traffic / talking issue between hosts and server
# 1  
Old 02-12-2009
SSH broke and network traffic / talking issue between hosts and server
Ok Time warner cable / voip modem feeding Cisco PIX 501 Wan port from PIX 501 LAN port to WAN port on Linksys wrt54GL wireless router.

so

-->Modem-->PIX 501-->WRT54GL-->Linux Server, wireless desktop, wireless laptop (2), Wireless MAC Pro, Wireless Apple TV, Wireless printer.

my wrt54gl is configured to hand out leases from 192.168.8.2 starting address to 192.168.8.12 ending address (10 leases total) the default gateway is 192.168.8.1

I have the linux box (Centos 5.2) plugged into the linksysy wrt54gl by wire

I was under the assumption that as long as anything on the linksys had an address of 192.168.8.X they could talk back and forth through the linksys without going out to the PIX.

I want my linux box to be statically assigned to 192.168.8.100

when i do this i cant ping any of the leased addresses, nor pull up google.com or ping it. however if i statically assign it to one the free lease addresses it works fine and can be pinged.

that is my first problem and i dont know how to fix it.

My second problem is i had sshd working fine but i changed the sshd_config to listenaddress at 192.168.8.0 it wasnt working so i changed that to 192.168.0.0 and did a service sshd restart and it keeps giving me failed on stop but ok on start but service sshd status returns sshd dead but subsystem locked.

when i had it at listenaddress 0.0.0.0 it was working fine.

what is going on here?
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. IP Networking

I would like to monitor network traffic for a computer on my network

My son does homework on a school laptop. I was thinking about setting up a gateway on my home network, so that I can monitor web traffic and know if he is doing his homework without standing over his shoulder. Ideally I would like to use the Raspberry Pi Model b that I already have. However, I... (15 Replies)
Discussion started by: gandolf989
15 Replies

2. UNIX for Dummies Questions & Answers

Network Issue on virtual server

I have a virtual (vmware player) on which i have two small RHEL 6.7 servers and two win7pro 64 bit guest nodes running. #virt. host issue: accessible remotely but difficulty joining domain. The virtual host itself uses static IP and it is accessible. It is using win 7 pro 64 bit, as its host... (2 Replies)
Discussion started by: rsheikh01
2 Replies

3. Proxy Server

IPtable rules for DNS/http/https traffic for specific hosts only, not working.

Hi there, I have a VPS and am working on a little side project for myself and friend which is a DNS proxy. Everything was great till recently. My VPS IP has been detected by some botnet or something, and I believe SMURF attacks are occuring. The VPS provider keeps shutting down my VPS... (3 Replies)
Discussion started by: phi0x
3 Replies

4. Solaris

Ssh connection broke after patching

Hi, I have a user - e3t3user on two Solaris-10 servers. We did patching source server and after that e3t3user is not able to ssh from one server to another. Passwordless ssh connection is setup between both servers (with ssh keys share). I am not able to figure out, where it is failing. Here is... (1 Reply)
Discussion started by: solaris_1977
1 Replies

5. Solaris

nestat on server involved in high traffic network

Hi All My Server is doing a very intense netowrk traffic operations and the cards are under very high pressure. I need to call NETSTAT on the shell. Do you know whether this command, under high pressure, might have some impact on the server traffic or can I proceed without any problem? (2 Replies)
Discussion started by: manustone
2 Replies

6. Solaris

Server unexpectedly closed network connection error in passwordless in ssh through

Hi , when i try to passwordless connection login in ssh through putty, i am getting the "Server unexpectedly closed network connection" error.i have already finished the public and private key settings for the particular user. thanks MaroV (1 Reply)
Discussion started by: vr_mari
1 Replies

7. Cybersecurity

Enable SSH for root over certain network connection of a server...is it possible?

Hi - I have a SUSE Enterprise Linux Server V9 that I have an issue with. Policy says that root connectivity via ssh needs to be disabled. So, to do that, I made the following change in the sshd_config section: # Authentication: #LoginGraceTime 2m #PermitRootLogin yes PermitRootLogin no... (3 Replies)
Discussion started by: cpolikowsky
3 Replies

8. IP Networking

ssh server is attachable from local network not from another network

hello i have a ubuntu ssh server that i can acess from any of my comnputers but only if they are on the same wireless network as the server. i tested trhis my tehtehring my samsung blackjack to my windows partition and installing openssh to windows it works when windows is on the wireless but no... (1 Reply)
Discussion started by: old noob
1 Replies

9. Solaris

network config problem - how to set the server for others to ssh without password

Hi, I want to ssh the linux server without inputting the password, how can I config this server? Thanks in advance! (1 Reply)
Discussion started by: GCTEII
1 Replies

10. UNIX for Advanced & Expert Users

Encrypt traffic between Solaris 8 hosts

I have two Solaris 8 hosts that send data to one another throughout the day. It is a legacy system and the programs used are rdist, rcp and ftp. I have been asked to ensure that the data transferred is encrypted beween the two hosts. My first thought was to replace these commands with ssh.... (2 Replies)
Discussion started by: blp001
2 Replies
Login or Register to Ask a Question

LEARN ABOUT NETBSD

sc

SC(4)							   BSD Kernel Interfaces Manual 						     SC(4)

NAME

     sc -- Sun Sun-2 SCSI bus host adaptor driver

SYNOPSIS

   sun2
     sc0 at mbmem0 addr 0x80000 ipl 2
     sc1 at mbmem0 addr 0x84000 ipl 2

   sun2 and sun4
     sc0 at vme0 addr 0x200000 irq 2 vec 0x40

DESCRIPTION

     The sc driver provides support for the Sun Microsystems "Sun-2" SCSI Bus Controller chipset found on various VME boards (Sun part #s
     501-1045, 501-1138, 501-1149, and 501-1167) and on the "Sun-2 SCSI/Serial" (Sun part # 501-1006) Multibus board.

     All versions of this driver can be configured with a flags directive in the config(1) file.  The values are bits in a bitfield, and are
     interpreted as follows:

	   0x0ff    Set bit (1<<target) to disable SCSI parity checking
	   0x100    Set this bit to disable DMA interrupts (poll)
	   0x200    Set this bit to disable DMA entirely (use PIO)

     For example: "flags 0x1ff" would disable DMA interrupts, and disable parity checking for targets 0-7.  The "target" is the SCSI ID number of
     a particular device on a particular SCSI bus.

SEE ALSO

     cd(4), ch(4), intro(4), scsi(4), sd(4), st(4)

AUTHORS

     Matt Fredette <fredette@NetBSD.org>,
     David Jones,
     Gordon Ross <gwr@NetBSD.org>,
     Adam Glass <glass@NetBSD.org>,
     Jason R. Thorpe <thorpej@NetBSD.org>.

BUGS

     This SCSI chipset is rumored to have bugs in its handling of SCSI parity, therefore it is recommended that you disable parity on all SCSI
     devices connected to this controller, and configure it with a 0x0ff value for its flags directive in the config(1) file.

     This chipset has no support for raising the ATN signal, so there is no way to ever schedule a MSG_OUT phase on the bus.  Currently, the
     driver will ultimately reset the bus if this phase is ever requested by the upper layer SCSI driver.

     This chipset has no support for SCSI disconnect/reselect.	This means that slow devices, such as tape drives, can hog, or "lock up" the SCSI
     bus.

     This driver has not been tested in combination with non-SCSI devices behind Emulex or Adaptec bridges, which are common in Sun 2s and in Sun
     Shoebox-type configurations.  These devices pre-date the SCSI-I spec, and might not behave the way the chipset code currently expects.

BSD
								   June 28, 2001							       BSD