question on dual NIC in linux
I set NIC as:
they both work.
I want to bind ssh on eth0, bind SIP traffic on eth1, then I set ssh to
listen on 184.108.40.206, bind the socket of SIP on 220.127.116.11.
But use tcpdump can get the packet on eth1, though ssh address is
Is that becase linux get the best route for it? how to disable the function
I want to make all ssh packet on eth0, even from 135.252.222.*
thanks a lot!
- Re: Specifying tunnel output interface?
... eth1: ext.ext.ext.ext ... Is there any way to ssh in through eth0 and direct all traffic tunneled ... The outgoing interface is chosen ...
- Re: Net::SSH::Perl bind socket problem
... >> bind to), maybe the ssh object is not destroyed between the loops. ... > I did use netstat -neat during, and after the script launch. ... only to handle the "port already in use" case... ...
- Re: Attacks against SSH?
... It would be interesting to know what version of BIND and SSH he was ... If he was running the latest versions of BIND and OpenSSH that RedHat ... I saw several things in the logs which gave me the ... Did you restart sshd after upggrading it? ...
- Re: What happened to SSH?
... It's because:: is IPv6 address, and this is what SSH binds to when it first start's, being that IPv4 is also enabled, when it tries to bind to the IPv4 address, it find's that it is already being used. ... Possibly disable IPv6 support in kernel or use the ListenAddress option in your SSHD server config file. ... (or bind the ListenAddress to a specific IP) ...
- Re: 5.2p1 no longer sets DISPLAY
... client ssh is still 3.9p1 and sshd_config is the same). ... what's happening is that the OS is asked for a list of addresses for localhost and is returning a list that includes the inet6 address, however attempting to bind to it fails. ... Previously sshd would ignore this failure, but that allows third parties to bind to inet6 ports in the X11 forwarding range and potentially hijack X connections. ... Good judgement comes with experience. ...