Block all ports except SSH on a specific network card

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I have 2 network cards, I need one of them to be used for work and the other is an open public network.



I'd like to use the work network card for ssh only:



hutber@hutber-blade ~ $ sudo iptables -S | grep enx9cebe863eaa8
-A INPUT -i enx9cebe863eaa8 -p tcp -m tcp --dport 22 -j ACCEPT
-A INPUT ! -i enx9cebe863eaa8 -p tcp -m tcp --dport 22 -j


I have setup the following rules, but once I enable enx9cebe863eaa8 all network traffic goes through this card.




ssh networking network-interface




share|improve this question



















  • That second rule would match tcp/22 on all other interfaces, but you're missing the argument to -j. You'd need DROP (or REJECT) on the same interface to block everything else. And routes set up sanely for the communication to work. Do you have that already in place, or setting up the routing part of the question?
    – ilkkachu
    Jul 4 at 16:55






  • 1




    there is a listen adress in sshd_config which restrict sshd ot listen only in that IP.
    – Archemar
    Jul 4 at 17:26










  • Thanks @Archemar I always thought the sshd config ListenAddress would mean that ssh can't use any other IP, but I didn't realise it blocked the IP from using any other ports as well. If I understand you correctly?
    – Jamie Hutber
    Jul 5 at 10:26










  • yes ListenAddress 192.168.100.100 will listen only on this IP, incomming ssh connection to 192.168.1.100 on same host will be droped by inetd (not sshd). You won't be able to ssh localhost either. (this might or might not be an indrance, but can be usefull to test)
    – Archemar
    Jul 5 at 11:07










  • Thanks again Arch. I still think you mis understand me. Please confirm back lol because I am confused. When I use ListenAddress 192.168.100.100 in my ssh/config file. 192.168.100.100 will ONLY be able to use port 22 and NO other ports?
    – Jamie Hutber
    Jul 6 at 9:17















up vote
1
down vote

favorite












I have 2 network cards, I need one of them to be used for work and the other is an open public network.



I'd like to use the work network card for ssh only:



hutber@hutber-blade ~ $ sudo iptables -S | grep enx9cebe863eaa8
-A INPUT -i enx9cebe863eaa8 -p tcp -m tcp --dport 22 -j ACCEPT
-A INPUT ! -i enx9cebe863eaa8 -p tcp -m tcp --dport 22 -j


I have setup the following rules, but once I enable enx9cebe863eaa8 all network traffic goes through this card.




ssh networking network-interface




share|improve this question



















  • That second rule would match tcp/22 on all other interfaces, but you're missing the argument to -j. You'd need DROP (or REJECT) on the same interface to block everything else. And routes set up sanely for the communication to work. Do you have that already in place, or setting up the routing part of the question?
    – ilkkachu
    Jul 4 at 16:55






  • 1




    there is a listen adress in sshd_config which restrict sshd ot listen only in that IP.
    – Archemar
    Jul 4 at 17:26










  • Thanks @Archemar I always thought the sshd config ListenAddress would mean that ssh can't use any other IP, but I didn't realise it blocked the IP from using any other ports as well. If I understand you correctly?
    – Jamie Hutber
    Jul 5 at 10:26










  • yes ListenAddress 192.168.100.100 will listen only on this IP, incomming ssh connection to 192.168.1.100 on same host will be droped by inetd (not sshd). You won't be able to ssh localhost either. (this might or might not be an indrance, but can be usefull to test)
    – Archemar
    Jul 5 at 11:07










  • Thanks again Arch. I still think you mis understand me. Please confirm back lol because I am confused. When I use ListenAddress 192.168.100.100 in my ssh/config file. 192.168.100.100 will ONLY be able to use port 22 and NO other ports?
    – Jamie Hutber
    Jul 6 at 9:17













up vote
1
down vote

favorite









up vote
1
down vote

favorite











I have 2 network cards, I need one of them to be used for work and the other is an open public network.



I'd like to use the work network card for ssh only:



hutber@hutber-blade ~ $ sudo iptables -S | grep enx9cebe863eaa8
-A INPUT -i enx9cebe863eaa8 -p tcp -m tcp --dport 22 -j ACCEPT
-A INPUT ! -i enx9cebe863eaa8 -p tcp -m tcp --dport 22 -j


I have setup the following rules, but once I enable enx9cebe863eaa8 all network traffic goes through this card.




ssh networking network-interface




share|improve this question











I have 2 network cards, I need one of them to be used for work and the other is an open public network.



I'd like to use the work network card for ssh only:



hutber@hutber-blade ~ $ sudo iptables -S | grep enx9cebe863eaa8
-A INPUT -i enx9cebe863eaa8 -p tcp -m tcp --dport 22 -j ACCEPT
-A INPUT ! -i enx9cebe863eaa8 -p tcp -m tcp --dport 22 -j


I have setup the following rules, but once I enable enx9cebe863eaa8 all network traffic goes through this card.





ssh networking network-interface





share|improve this question










share|improve this question




share|improve this question









asked Jul 4 at 15:57









Jamie Hutber

931212




931212











  • That second rule would match tcp/22 on all other interfaces, but you're missing the argument to -j. You'd need DROP (or REJECT) on the same interface to block everything else. And routes set up sanely for the communication to work. Do you have that already in place, or setting up the routing part of the question?
    – ilkkachu
    Jul 4 at 16:55






  • 1




    there is a listen adress in sshd_config which restrict sshd ot listen only in that IP.
    – Archemar
    Jul 4 at 17:26










  • Thanks @Archemar I always thought the sshd config ListenAddress would mean that ssh can't use any other IP, but I didn't realise it blocked the IP from using any other ports as well. If I understand you correctly?
    – Jamie Hutber
    Jul 5 at 10:26










  • yes ListenAddress 192.168.100.100 will listen only on this IP, incomming ssh connection to 192.168.1.100 on same host will be droped by inetd (not sshd). You won't be able to ssh localhost either. (this might or might not be an indrance, but can be usefull to test)
    – Archemar
    Jul 5 at 11:07










  • Thanks again Arch. I still think you mis understand me. Please confirm back lol because I am confused. When I use ListenAddress 192.168.100.100 in my ssh/config file. 192.168.100.100 will ONLY be able to use port 22 and NO other ports?
    – Jamie Hutber
    Jul 6 at 9:17

















  • That second rule would match tcp/22 on all other interfaces, but you're missing the argument to -j. You'd need DROP (or REJECT) on the same interface to block everything else. And routes set up sanely for the communication to work. Do you have that already in place, or setting up the routing part of the question?
    – ilkkachu
    Jul 4 at 16:55






  • 1




    there is a listen adress in sshd_config which restrict sshd ot listen only in that IP.
    – Archemar
    Jul 4 at 17:26










  • Thanks @Archemar I always thought the sshd config ListenAddress would mean that ssh can't use any other IP, but I didn't realise it blocked the IP from using any other ports as well. If I understand you correctly?
    – Jamie Hutber
    Jul 5 at 10:26










  • yes ListenAddress 192.168.100.100 will listen only on this IP, incomming ssh connection to 192.168.1.100 on same host will be droped by inetd (not sshd). You won't be able to ssh localhost either. (this might or might not be an indrance, but can be usefull to test)
    – Archemar
    Jul 5 at 11:07










  • Thanks again Arch. I still think you mis understand me. Please confirm back lol because I am confused. When I use ListenAddress 192.168.100.100 in my ssh/config file. 192.168.100.100 will ONLY be able to use port 22 and NO other ports?
    – Jamie Hutber
    Jul 6 at 9:17
















That second rule would match tcp/22 on all other interfaces, but you're missing the argument to -j. You'd need DROP (or REJECT) on the same interface to block everything else. And routes set up sanely for the communication to work. Do you have that already in place, or setting up the routing part of the question?
– ilkkachu
Jul 4 at 16:55




That second rule would match tcp/22 on all other interfaces, but you're missing the argument to -j. You'd need DROP (or REJECT) on the same interface to block everything else. And routes set up sanely for the communication to work. Do you have that already in place, or setting up the routing part of the question?
– ilkkachu
Jul 4 at 16:55




1




1




there is a listen adress in sshd_config which restrict sshd ot listen only in that IP.
– Archemar
Jul 4 at 17:26




there is a listen adress in sshd_config which restrict sshd ot listen only in that IP.
– Archemar
Jul 4 at 17:26












Thanks @Archemar I always thought the sshd config ListenAddress would mean that ssh can't use any other IP, but I didn't realise it blocked the IP from using any other ports as well. If I understand you correctly?
– Jamie Hutber
Jul 5 at 10:26




Thanks @Archemar I always thought the sshd config ListenAddress would mean that ssh can't use any other IP, but I didn't realise it blocked the IP from using any other ports as well. If I understand you correctly?
– Jamie Hutber
Jul 5 at 10:26












yes ListenAddress 192.168.100.100 will listen only on this IP, incomming ssh connection to 192.168.1.100 on same host will be droped by inetd (not sshd). You won't be able to ssh localhost either. (this might or might not be an indrance, but can be usefull to test)
– Archemar
Jul 5 at 11:07




yes ListenAddress 192.168.100.100 will listen only on this IP, incomming ssh connection to 192.168.1.100 on same host will be droped by inetd (not sshd). You won't be able to ssh localhost either. (this might or might not be an indrance, but can be usefull to test)
– Archemar
Jul 5 at 11:07












Thanks again Arch. I still think you mis understand me. Please confirm back lol because I am confused. When I use ListenAddress 192.168.100.100 in my ssh/config file. 192.168.100.100 will ONLY be able to use port 22 and NO other ports?
– Jamie Hutber
Jul 6 at 9:17





Thanks again Arch. I still think you mis understand me. Please confirm back lol because I am confused. When I use ListenAddress 192.168.100.100 in my ssh/config file. 192.168.100.100 will ONLY be able to use port 22 and NO other ports?
– Jamie Hutber
Jul 6 at 9:17
















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f453453%2fblock-all-ports-except-ssh-on-a-specific-network-card%23new-answer', 'question_page');

);

Post as a guest






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f453453%2fblock-all-ports-except-ssh-on-a-specific-network-card%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
Read more