connecting and sending internet traffic through a specific host

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











up vote
1
down vote

favorite












I'm not sure it's a routing question - my understanding is too basic. There is the issue:



I am connected to a network as 10.103.38.4 and route goes per default per:



10.103.38.0/24 dev enp10s0 proto kernel scope link src 10.103.38.4 metric 100 
169.254.0.0/16 dev enp10s0 scope link metric 1000
192.168.13.148 via 10.103.38.1 dev enp10s0 proto dhcp metric 100


I understand the gateway / default route is 10.103.38.1 and packets are filtered through a nasty login, every time.



However, there are other hosts on the network, which directly connect to the outside world i.e. 10.103.108.1. I can see this latter host and connect to it.



What to do to send the default route through the 10.103.108.1 - if i set it up as a default route, the network is unreachable.







share|improve this question






















  • It is not clear at all what you are asking. Mind you a host/gateway having a private IP address is not directly connected to the Internet. Please do not write posts in a rush if you need help. Your post is difficult to follow, and what is your doubt is not entirely clear. Our focus is also into answering specific doubts, and not writing tutorials. please read our faq.
    – Rui F Ribeiro
    Oct 22 '17 at 10:20










  • You should edit and format your question. And I'm still wondering what's the question. "filtered through a nasty login". Are you talking about a captive portal and looking at how to be automatically authenticated without getting the portal? Then you're saying you have 10.103.108.1 as default route, but later you tell "if I set it up as default route...", that's a bit misleading. Perhaps you mean without doing a DHCP request first for example? Please update
    – A.B
    Oct 22 '17 at 12:44















up vote
1
down vote

favorite












I'm not sure it's a routing question - my understanding is too basic. There is the issue:



I am connected to a network as 10.103.38.4 and route goes per default per:



10.103.38.0/24 dev enp10s0 proto kernel scope link src 10.103.38.4 metric 100 
169.254.0.0/16 dev enp10s0 scope link metric 1000
192.168.13.148 via 10.103.38.1 dev enp10s0 proto dhcp metric 100


I understand the gateway / default route is 10.103.38.1 and packets are filtered through a nasty login, every time.



However, there are other hosts on the network, which directly connect to the outside world i.e. 10.103.108.1. I can see this latter host and connect to it.



What to do to send the default route through the 10.103.108.1 - if i set it up as a default route, the network is unreachable.







share|improve this question






















  • It is not clear at all what you are asking. Mind you a host/gateway having a private IP address is not directly connected to the Internet. Please do not write posts in a rush if you need help. Your post is difficult to follow, and what is your doubt is not entirely clear. Our focus is also into answering specific doubts, and not writing tutorials. please read our faq.
    – Rui F Ribeiro
    Oct 22 '17 at 10:20










  • You should edit and format your question. And I'm still wondering what's the question. "filtered through a nasty login". Are you talking about a captive portal and looking at how to be automatically authenticated without getting the portal? Then you're saying you have 10.103.108.1 as default route, but later you tell "if I set it up as default route...", that's a bit misleading. Perhaps you mean without doing a DHCP request first for example? Please update
    – A.B
    Oct 22 '17 at 12:44













up vote
1
down vote

favorite









up vote
1
down vote

favorite











I'm not sure it's a routing question - my understanding is too basic. There is the issue:



I am connected to a network as 10.103.38.4 and route goes per default per:



10.103.38.0/24 dev enp10s0 proto kernel scope link src 10.103.38.4 metric 100 
169.254.0.0/16 dev enp10s0 scope link metric 1000
192.168.13.148 via 10.103.38.1 dev enp10s0 proto dhcp metric 100


I understand the gateway / default route is 10.103.38.1 and packets are filtered through a nasty login, every time.



However, there are other hosts on the network, which directly connect to the outside world i.e. 10.103.108.1. I can see this latter host and connect to it.



What to do to send the default route through the 10.103.108.1 - if i set it up as a default route, the network is unreachable.







share|improve this question














I'm not sure it's a routing question - my understanding is too basic. There is the issue:



I am connected to a network as 10.103.38.4 and route goes per default per:



10.103.38.0/24 dev enp10s0 proto kernel scope link src 10.103.38.4 metric 100 
169.254.0.0/16 dev enp10s0 scope link metric 1000
192.168.13.148 via 10.103.38.1 dev enp10s0 proto dhcp metric 100


I understand the gateway / default route is 10.103.38.1 and packets are filtered through a nasty login, every time.



However, there are other hosts on the network, which directly connect to the outside world i.e. 10.103.108.1. I can see this latter host and connect to it.



What to do to send the default route through the 10.103.108.1 - if i set it up as a default route, the network is unreachable.









share|improve this question













share|improve this question




share|improve this question








edited Oct 22 '17 at 12:54









WhiteWinterWolf

1,586830




1,586830










asked Oct 22 '17 at 8:45









The Arkaroo

61




61











  • It is not clear at all what you are asking. Mind you a host/gateway having a private IP address is not directly connected to the Internet. Please do not write posts in a rush if you need help. Your post is difficult to follow, and what is your doubt is not entirely clear. Our focus is also into answering specific doubts, and not writing tutorials. please read our faq.
    – Rui F Ribeiro
    Oct 22 '17 at 10:20










  • You should edit and format your question. And I'm still wondering what's the question. "filtered through a nasty login". Are you talking about a captive portal and looking at how to be automatically authenticated without getting the portal? Then you're saying you have 10.103.108.1 as default route, but later you tell "if I set it up as default route...", that's a bit misleading. Perhaps you mean without doing a DHCP request first for example? Please update
    – A.B
    Oct 22 '17 at 12:44

















  • It is not clear at all what you are asking. Mind you a host/gateway having a private IP address is not directly connected to the Internet. Please do not write posts in a rush if you need help. Your post is difficult to follow, and what is your doubt is not entirely clear. Our focus is also into answering specific doubts, and not writing tutorials. please read our faq.
    – Rui F Ribeiro
    Oct 22 '17 at 10:20










  • You should edit and format your question. And I'm still wondering what's the question. "filtered through a nasty login". Are you talking about a captive portal and looking at how to be automatically authenticated without getting the portal? Then you're saying you have 10.103.108.1 as default route, but later you tell "if I set it up as default route...", that's a bit misleading. Perhaps you mean without doing a DHCP request first for example? Please update
    – A.B
    Oct 22 '17 at 12:44
















It is not clear at all what you are asking. Mind you a host/gateway having a private IP address is not directly connected to the Internet. Please do not write posts in a rush if you need help. Your post is difficult to follow, and what is your doubt is not entirely clear. Our focus is also into answering specific doubts, and not writing tutorials. please read our faq.
– Rui F Ribeiro
Oct 22 '17 at 10:20




It is not clear at all what you are asking. Mind you a host/gateway having a private IP address is not directly connected to the Internet. Please do not write posts in a rush if you need help. Your post is difficult to follow, and what is your doubt is not entirely clear. Our focus is also into answering specific doubts, and not writing tutorials. please read our faq.
– Rui F Ribeiro
Oct 22 '17 at 10:20












You should edit and format your question. And I'm still wondering what's the question. "filtered through a nasty login". Are you talking about a captive portal and looking at how to be automatically authenticated without getting the portal? Then you're saying you have 10.103.108.1 as default route, but later you tell "if I set it up as default route...", that's a bit misleading. Perhaps you mean without doing a DHCP request first for example? Please update
– A.B
Oct 22 '17 at 12:44





You should edit and format your question. And I'm still wondering what's the question. "filtered through a nasty login". Are you talking about a captive portal and looking at how to be automatically authenticated without getting the portal? Then you're saying you have 10.103.108.1 as default route, but later you tell "if I set it up as default route...", that's a bit misleading. Perhaps you mean without doing a DHCP request first for example? Please update
– A.B
Oct 22 '17 at 12:44











1 Answer
1






active

oldest

votes

















up vote
0
down vote













Here is your issue as I understand it:



  • Your IP is 10.103.38.4.

  • You are part of the network 10.103.38.0/24 which uses the default router 10.103.38.1.

  • This router requires a annoying login to access the Internet.

  • Other networks such as 10.103.108.0/24 have access to the Internet without requiring login, their default router (10.103.108.1) is accessible to you.

So, first thing first, I will take your question from a pure theoretical perspective as it raises an interesting concept since, otherwise, it would mean you are trying to bypass a local policy which is no good.



As a stated above, the other routers are in fact located on different networks, this means that you have to go through your main router 10.103.38.1 to reach the other routers like 10.103.108.1, you cannot reach them directly.



What you may wonder is if there is a way to use 10.103.108.1 as your first hop router, but then instead of directly going to the Internet ask it to first go through 10.103.108.1 (internal network so no login required) and only then go to the Internet (10.103.108.1 used as exit node, so login bypassed).



Such feature technically exists and is called source routing. Normally it's up to the router to determine the best route, but source routing allows the initial sender to impose the route that its packets should take.



Obviously, this feature is usually disabled everywhere precisely to avoid tricky people to exploit it maliciously ;).






share|improve this answer




















  • The 10.103.108.1 host will also have to be configured to act as a router, i.e. it should be able to forward received packets that are not destined to it. Forwarding is usually disabled.
    – Johan Myréen
    Oct 22 '17 at 13:17










  • @JohanMyréen: 10.103.108.1 is most likely the default router for the 10.103.108.0/24 network (relying both on OP message stating it "connect to the outside world" and given the apparent naming scheme, as we know from OP message that 10.103.38.1 is the default router for the 10.103.38.0/24 network).
    – WhiteWinterWolf
    Oct 22 '17 at 13:22










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%2f399670%2fconnecting-and-sending-internet-traffic-through-a-specific-host%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote













Here is your issue as I understand it:



  • Your IP is 10.103.38.4.

  • You are part of the network 10.103.38.0/24 which uses the default router 10.103.38.1.

  • This router requires a annoying login to access the Internet.

  • Other networks such as 10.103.108.0/24 have access to the Internet without requiring login, their default router (10.103.108.1) is accessible to you.

So, first thing first, I will take your question from a pure theoretical perspective as it raises an interesting concept since, otherwise, it would mean you are trying to bypass a local policy which is no good.



As a stated above, the other routers are in fact located on different networks, this means that you have to go through your main router 10.103.38.1 to reach the other routers like 10.103.108.1, you cannot reach them directly.



What you may wonder is if there is a way to use 10.103.108.1 as your first hop router, but then instead of directly going to the Internet ask it to first go through 10.103.108.1 (internal network so no login required) and only then go to the Internet (10.103.108.1 used as exit node, so login bypassed).



Such feature technically exists and is called source routing. Normally it's up to the router to determine the best route, but source routing allows the initial sender to impose the route that its packets should take.



Obviously, this feature is usually disabled everywhere precisely to avoid tricky people to exploit it maliciously ;).






share|improve this answer




















  • The 10.103.108.1 host will also have to be configured to act as a router, i.e. it should be able to forward received packets that are not destined to it. Forwarding is usually disabled.
    – Johan Myréen
    Oct 22 '17 at 13:17










  • @JohanMyréen: 10.103.108.1 is most likely the default router for the 10.103.108.0/24 network (relying both on OP message stating it "connect to the outside world" and given the apparent naming scheme, as we know from OP message that 10.103.38.1 is the default router for the 10.103.38.0/24 network).
    – WhiteWinterWolf
    Oct 22 '17 at 13:22














up vote
0
down vote













Here is your issue as I understand it:



  • Your IP is 10.103.38.4.

  • You are part of the network 10.103.38.0/24 which uses the default router 10.103.38.1.

  • This router requires a annoying login to access the Internet.

  • Other networks such as 10.103.108.0/24 have access to the Internet without requiring login, their default router (10.103.108.1) is accessible to you.

So, first thing first, I will take your question from a pure theoretical perspective as it raises an interesting concept since, otherwise, it would mean you are trying to bypass a local policy which is no good.



As a stated above, the other routers are in fact located on different networks, this means that you have to go through your main router 10.103.38.1 to reach the other routers like 10.103.108.1, you cannot reach them directly.



What you may wonder is if there is a way to use 10.103.108.1 as your first hop router, but then instead of directly going to the Internet ask it to first go through 10.103.108.1 (internal network so no login required) and only then go to the Internet (10.103.108.1 used as exit node, so login bypassed).



Such feature technically exists and is called source routing. Normally it's up to the router to determine the best route, but source routing allows the initial sender to impose the route that its packets should take.



Obviously, this feature is usually disabled everywhere precisely to avoid tricky people to exploit it maliciously ;).






share|improve this answer




















  • The 10.103.108.1 host will also have to be configured to act as a router, i.e. it should be able to forward received packets that are not destined to it. Forwarding is usually disabled.
    – Johan Myréen
    Oct 22 '17 at 13:17










  • @JohanMyréen: 10.103.108.1 is most likely the default router for the 10.103.108.0/24 network (relying both on OP message stating it "connect to the outside world" and given the apparent naming scheme, as we know from OP message that 10.103.38.1 is the default router for the 10.103.38.0/24 network).
    – WhiteWinterWolf
    Oct 22 '17 at 13:22












up vote
0
down vote










up vote
0
down vote









Here is your issue as I understand it:



  • Your IP is 10.103.38.4.

  • You are part of the network 10.103.38.0/24 which uses the default router 10.103.38.1.

  • This router requires a annoying login to access the Internet.

  • Other networks such as 10.103.108.0/24 have access to the Internet without requiring login, their default router (10.103.108.1) is accessible to you.

So, first thing first, I will take your question from a pure theoretical perspective as it raises an interesting concept since, otherwise, it would mean you are trying to bypass a local policy which is no good.



As a stated above, the other routers are in fact located on different networks, this means that you have to go through your main router 10.103.38.1 to reach the other routers like 10.103.108.1, you cannot reach them directly.



What you may wonder is if there is a way to use 10.103.108.1 as your first hop router, but then instead of directly going to the Internet ask it to first go through 10.103.108.1 (internal network so no login required) and only then go to the Internet (10.103.108.1 used as exit node, so login bypassed).



Such feature technically exists and is called source routing. Normally it's up to the router to determine the best route, but source routing allows the initial sender to impose the route that its packets should take.



Obviously, this feature is usually disabled everywhere precisely to avoid tricky people to exploit it maliciously ;).






share|improve this answer












Here is your issue as I understand it:



  • Your IP is 10.103.38.4.

  • You are part of the network 10.103.38.0/24 which uses the default router 10.103.38.1.

  • This router requires a annoying login to access the Internet.

  • Other networks such as 10.103.108.0/24 have access to the Internet without requiring login, their default router (10.103.108.1) is accessible to you.

So, first thing first, I will take your question from a pure theoretical perspective as it raises an interesting concept since, otherwise, it would mean you are trying to bypass a local policy which is no good.



As a stated above, the other routers are in fact located on different networks, this means that you have to go through your main router 10.103.38.1 to reach the other routers like 10.103.108.1, you cannot reach them directly.



What you may wonder is if there is a way to use 10.103.108.1 as your first hop router, but then instead of directly going to the Internet ask it to first go through 10.103.108.1 (internal network so no login required) and only then go to the Internet (10.103.108.1 used as exit node, so login bypassed).



Such feature technically exists and is called source routing. Normally it's up to the router to determine the best route, but source routing allows the initial sender to impose the route that its packets should take.



Obviously, this feature is usually disabled everywhere precisely to avoid tricky people to exploit it maliciously ;).







share|improve this answer












share|improve this answer



share|improve this answer










answered Oct 22 '17 at 12:41









WhiteWinterWolf

1,586830




1,586830











  • The 10.103.108.1 host will also have to be configured to act as a router, i.e. it should be able to forward received packets that are not destined to it. Forwarding is usually disabled.
    – Johan Myréen
    Oct 22 '17 at 13:17










  • @JohanMyréen: 10.103.108.1 is most likely the default router for the 10.103.108.0/24 network (relying both on OP message stating it "connect to the outside world" and given the apparent naming scheme, as we know from OP message that 10.103.38.1 is the default router for the 10.103.38.0/24 network).
    – WhiteWinterWolf
    Oct 22 '17 at 13:22
















  • The 10.103.108.1 host will also have to be configured to act as a router, i.e. it should be able to forward received packets that are not destined to it. Forwarding is usually disabled.
    – Johan Myréen
    Oct 22 '17 at 13:17










  • @JohanMyréen: 10.103.108.1 is most likely the default router for the 10.103.108.0/24 network (relying both on OP message stating it "connect to the outside world" and given the apparent naming scheme, as we know from OP message that 10.103.38.1 is the default router for the 10.103.38.0/24 network).
    – WhiteWinterWolf
    Oct 22 '17 at 13:22















The 10.103.108.1 host will also have to be configured to act as a router, i.e. it should be able to forward received packets that are not destined to it. Forwarding is usually disabled.
– Johan Myréen
Oct 22 '17 at 13:17




The 10.103.108.1 host will also have to be configured to act as a router, i.e. it should be able to forward received packets that are not destined to it. Forwarding is usually disabled.
– Johan Myréen
Oct 22 '17 at 13:17












@JohanMyréen: 10.103.108.1 is most likely the default router for the 10.103.108.0/24 network (relying both on OP message stating it "connect to the outside world" and given the apparent naming scheme, as we know from OP message that 10.103.38.1 is the default router for the 10.103.38.0/24 network).
– WhiteWinterWolf
Oct 22 '17 at 13:22




@JohanMyréen: 10.103.108.1 is most likely the default router for the 10.103.108.0/24 network (relying both on OP message stating it "connect to the outside world" and given the apparent naming scheme, as we know from OP message that 10.103.38.1 is the default router for the 10.103.38.0/24 network).
– WhiteWinterWolf
Oct 22 '17 at 13:22

















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f399670%2fconnecting-and-sending-internet-traffic-through-a-specific-host%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

Peggy Mitchell

Palaiologos

The Forum (Inglewood, California)