Bind the incoming IP to outgoing IP in a multi public IP server [closed]Network routing issues on Linuxipv6: `ifconfig` shows “Scope:Link” . What is “Scope:Link”?Translating debian network configuration to gentooStatic virtual IP in debian 6.0.4IP address reuse on macvlan devicesRemote end of IPSec transport is 'permenantly glued' to loopback after some messing around with GRERoute traffic through private IP for only certain hosts - CentOS 6.6How to correctly set up routing on machine with 4 interfaces so that three of interfaces are on the same subnet?IPTables DNAT WAN interface to hosted VM fails but DNAT to WAN IP succeedsLinux: Bridging two ethernet connections together to allow second host onto first network
Should homeowners insurance cover the cost of the home?
Find magical solution to magical equation
Does "Captain Marvel" contain spoilers for "Avengers: Infinity War"?
What do I do if my advisor made a mistake?
Would you use "llamarse" for an animal's name?
Is there precedent or are there procedures for a US president refusing to concede to an electoral defeat?
As a GM, is it bad form to ask for a moment to think when improvising?
Which sphere is fastest?
How do I calculate how many of an item I'll have in this inventory system?
Proper use of Wikipedia code sample in open source projects
What is the closest airport to the center of the city it serves?
How do I, as a DM, handle a party that decides to set up an ambush in a dungeon?
Why would a military not separate its forces into different branches?
Out of scope work duties and resignation
To kill a cuckoo
Typeset year in old-style numbers with biblatex
Prove that a definite integral is an infinite sum
Will 700 more planes a day fly because of the Heathrow expansion?
Voltage Balun 1:1
When an imagined world resembles or has similarities with a famous world
How can internet speed be 10 times slower without a router than when using the same connection with a router?
Why is my arithmetic with a long long int behaving this way?
What to use instead of cling film to wrap pastry
Notation: What does the tilde bellow of the Expectation mean?
Bind the incoming IP to outgoing IP in a multi public IP server [closed]
Network routing issues on Linuxipv6: `ifconfig` shows “Scope:Link” . What is “Scope:Link”?Translating debian network configuration to gentooStatic virtual IP in debian 6.0.4IP address reuse on macvlan devicesRemote end of IPSec transport is 'permenantly glued' to loopback after some messing around with GRERoute traffic through private IP for only certain hosts - CentOS 6.6How to correctly set up routing on machine with 4 interfaces so that three of interfaces are on the same subnet?IPTables DNAT WAN interface to hosted VM fails but DNAT to WAN IP succeedsLinux: Bridging two ethernet connections together to allow second host onto first network
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have a server (Ubuntu 18.04) with multiple IP address in the same Ethernet card.
This is the ip a return:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 06:9b:1c:00:00:2a brd ff:ff:ff:ff:ff:ff
inet 191.XXX.XXX.51/23 brd 191.XXX.XXX.255 scope global dynamic ens3
valid_lft 80087sec preferred_lft 80087sec
inet 179.XXX.XXX.0/32 scope global ens3
valid_lft forever preferred_lft forever
inet 179.XXX.XXX.1/32 scope global ens3
valid_lft forever preferred_lft forever
inet 179.XXX.XXX.2/32 scope global ens3
valid_lft forever preferred_lft forever
inet 179.XXX.XXX.3/32 scope global ens3
valid_lft forever preferred_lft forever
inet6 fe80::XXX:XXX:XXX:2a/64 scope link
valid_lft forever preferred_lft forever
So I have a main public IP: 191.XXX.XXX.51 and 4 more secondary public IPs: 179.XXX.XXX.0-3
My final goal is to install squid and have multiple outgoing IP address, so for the client that connects using 179.XXX.XXX.1 the outgoing IP address has to be the same 179.XXX.XXX.1.
I tried to modify the Squid conf file using acl with outgoing address:
tcp_outgoing_address 179.XXX.XXX.1
But without success. I can connect to the server with the secondary IPs but the outgoing IP is always the primary IP and if I specify the secondary IP in the squid the connection just timeout, looks like my Linux doesn't know how to route this.
This is my route -n return:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 191.XXX.XXX.1 0.0.0.0 UG 100 0 0 ens3
191.XXX.XXX.0 0.0.0.0 255.255.254.0 U 0 0 0 ens3
191.XXX.XXX.1 0.0.0.0 255.255.255.255 UH 100 0 0 ens3
How can I make the secondary IPs usable?
linux networking iptables squid route
asked Apr 25 at 21:08
GuiGui
993
closed as off-topic by womble♦ Apr 26 at 1:42
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking installation, configuration or diagnostic help must include the desired end state, the specific problem or error, sufficient information about the configuration and environment to reproduce it, and attempted solutions. Questions without a clear problem statement are not useful to other readers and are unlikely to get good answers." – womble
add a comment |
I have a server (Ubuntu 18.04) with multiple IP address in the same Ethernet card.
This is the ip a return:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 06:9b:1c:00:00:2a brd ff:ff:ff:ff:ff:ff
inet 191.XXX.XXX.51/23 brd 191.XXX.XXX.255 scope global dynamic ens3
valid_lft 80087sec preferred_lft 80087sec
inet 179.XXX.XXX.0/32 scope global ens3
valid_lft forever preferred_lft forever
inet 179.XXX.XXX.1/32 scope global ens3
valid_lft forever preferred_lft forever
inet 179.XXX.XXX.2/32 scope global ens3
valid_lft forever preferred_lft forever
inet 179.XXX.XXX.3/32 scope global ens3
valid_lft forever preferred_lft forever
inet6 fe80::XXX:XXX:XXX:2a/64 scope link
valid_lft forever preferred_lft forever
So I have a main public IP: 191.XXX.XXX.51 and 4 more secondary public IPs: 179.XXX.XXX.0-3
My final goal is to install squid and have multiple outgoing IP address, so for the client that connects using 179.XXX.XXX.1 the outgoing IP address has to be the same 179.XXX.XXX.1.
I tried to modify the Squid conf file using acl with outgoing address:
tcp_outgoing_address 179.XXX.XXX.1
But without success. I can connect to the server with the secondary IPs but the outgoing IP is always the primary IP and if I specify the secondary IP in the squid the connection just timeout, looks like my Linux doesn't know how to route this.
This is my route -n return:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 191.XXX.XXX.1 0.0.0.0 UG 100 0 0 ens3
191.XXX.XXX.0 0.0.0.0 255.255.254.0 U 0 0 0 ens3
191.XXX.XXX.1 0.0.0.0 255.255.255.255 UH 100 0 0 ens3
How can I make the secondary IPs usable?
linux networking iptables squid route
asked Apr 25 at 21:08
GuiGui
993
closed as off-topic by womble♦ Apr 26 at 1:42
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking installation, configuration or diagnostic help must include the desired end state, the specific problem or error, sufficient information about the configuration and environment to reproduce it, and attempted solutions. Questions without a clear problem statement are not useful to other readers and are unlikely to get good answers." – womble
3
Your redaction has masked potentially useful information, you haven't described what "failure" means or show what exact configuration(s) you have tried, and the behaviour you are saying you have observed does not match any known behaviour. Please provide a lot more raw material from which we can draw our own conclusions.
– womble♦
Apr 26 at 1:42
To me the question isn't that unclear. Gui can use ACLs to match incoming connections and then use thetcp_outgoing_addressdirective to select what address to use as the source address to make the corresponding outgoing connection. See squid-cache.org/Doc/config/tcp_outgoing_address
– wurtel
Apr 26 at 11:13
I yes tried to use acls with tcp_outgoing_address using this tutoral: adamscheller.com/systems-administration/… and this another: tastyplacement.com/squid-proxy-multiple-outgoing-ip-addresses . But this doesn't work.
– Gui
Apr 26 at 16:29
add a comment |
I have a server (Ubuntu 18.04) with multiple IP address in the same Ethernet card.
This is the ip a return:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 06:9b:1c:00:00:2a brd ff:ff:ff:ff:ff:ff
inet 191.XXX.XXX.51/23 brd 191.XXX.XXX.255 scope global dynamic ens3
valid_lft 80087sec preferred_lft 80087sec
inet 179.XXX.XXX.0/32 scope global ens3
valid_lft forever preferred_lft forever
inet 179.XXX.XXX.1/32 scope global ens3
valid_lft forever preferred_lft forever
inet 179.XXX.XXX.2/32 scope global ens3
valid_lft forever preferred_lft forever
inet 179.XXX.XXX.3/32 scope global ens3
valid_lft forever preferred_lft forever
inet6 fe80::XXX:XXX:XXX:2a/64 scope link
valid_lft forever preferred_lft forever
So I have a main public IP: 191.XXX.XXX.51 and 4 more secondary public IPs: 179.XXX.XXX.0-3
My final goal is to install squid and have multiple outgoing IP address, so for the client that connects using 179.XXX.XXX.1 the outgoing IP address has to be the same 179.XXX.XXX.1.
I tried to modify the Squid conf file using acl with outgoing address:
tcp_outgoing_address 179.XXX.XXX.1
But without success. I can connect to the server with the secondary IPs but the outgoing IP is always the primary IP and if I specify the secondary IP in the squid the connection just timeout, looks like my Linux doesn't know how to route this.
This is my route -n return:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 191.XXX.XXX.1 0.0.0.0 UG 100 0 0 ens3
191.XXX.XXX.0 0.0.0.0 255.255.254.0 U 0 0 0 ens3
191.XXX.XXX.1 0.0.0.0 255.255.255.255 UH 100 0 0 ens3
How can I make the secondary IPs usable?
linux networking iptables squid route
asked Apr 25 at 21:08
GuiGui
993
I have a server (Ubuntu 18.04) with multiple IP address in the same Ethernet card.
This is the ip a return:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 06:9b:1c:00:00:2a brd ff:ff:ff:ff:ff:ff
inet 191.XXX.XXX.51/23 brd 191.XXX.XXX.255 scope global dynamic ens3
valid_lft 80087sec preferred_lft 80087sec
inet 179.XXX.XXX.0/32 scope global ens3
valid_lft forever preferred_lft forever
inet 179.XXX.XXX.1/32 scope global ens3
valid_lft forever preferred_lft forever
inet 179.XXX.XXX.2/32 scope global ens3
valid_lft forever preferred_lft forever
inet 179.XXX.XXX.3/32 scope global ens3
valid_lft forever preferred_lft forever
inet6 fe80::XXX:XXX:XXX:2a/64 scope link
valid_lft forever preferred_lft forever
So I have a main public IP: 191.XXX.XXX.51 and 4 more secondary public IPs: 179.XXX.XXX.0-3
My final goal is to install squid and have multiple outgoing IP address, so for the client that connects using 179.XXX.XXX.1 the outgoing IP address has to be the same 179.XXX.XXX.1.
I tried to modify the Squid conf file using acl with outgoing address:
tcp_outgoing_address 179.XXX.XXX.1
But without success. I can connect to the server with the secondary IPs but the outgoing IP is always the primary IP and if I specify the secondary IP in the squid the connection just timeout, looks like my Linux doesn't know how to route this.
This is my route -n return:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 191.XXX.XXX.1 0.0.0.0 UG 100 0 0 ens3
191.XXX.XXX.0 0.0.0.0 255.255.254.0 U 0 0 0 ens3
191.XXX.XXX.1 0.0.0.0 255.255.255.255 UH 100 0 0 ens3
How can I make the secondary IPs usable?
linux networking iptables squid route
linux networking iptables squid route
asked Apr 25 at 21:08
GuiGui
993
asked Apr 25 at 21:08
GuiGui
993
edited Apr 26 at 16:28
Gui
asked Apr 25 at 21:08
GuiGui
993
asked Apr 25 at 21:08
GuiGui
993
asked Apr 25 at 21:08
GuiGui
993
993
closed as off-topic by womble♦ Apr 26 at 1:42
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking installation, configuration or diagnostic help must include the desired end state, the specific problem or error, sufficient information about the configuration and environment to reproduce it, and attempted solutions. Questions without a clear problem statement are not useful to other readers and are unlikely to get good answers." – womble
closed as off-topic by womble♦ Apr 26 at 1:42
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking installation, configuration or diagnostic help must include the desired end state, the specific problem or error, sufficient information about the configuration and environment to reproduce it, and attempted solutions. Questions without a clear problem statement are not useful to other readers and are unlikely to get good answers." – womble
3
Your redaction has masked potentially useful information, you haven't described what "failure" means or show what exact configuration(s) you have tried, and the behaviour you are saying you have observed does not match any known behaviour. Please provide a lot more raw material from which we can draw our own conclusions.
– womble♦
Apr 26 at 1:42
To me the question isn't that unclear. Gui can use ACLs to match incoming connections and then use thetcp_outgoing_addressdirective to select what address to use as the source address to make the corresponding outgoing connection. See squid-cache.org/Doc/config/tcp_outgoing_address
– wurtel
Apr 26 at 11:13
I yes tried to use acls with tcp_outgoing_address using this tutoral: adamscheller.com/systems-administration/… and this another: tastyplacement.com/squid-proxy-multiple-outgoing-ip-addresses . But this doesn't work.
– Gui
Apr 26 at 16:29
add a comment |
3
Your redaction has masked potentially useful information, you haven't described what "failure" means or show what exact configuration(s) you have tried, and the behaviour you are saying you have observed does not match any known behaviour. Please provide a lot more raw material from which we can draw our own conclusions.
– womble♦
Apr 26 at 1:42
To me the question isn't that unclear. Gui can use ACLs to match incoming connections and then use thetcp_outgoing_addressdirective to select what address to use as the source address to make the corresponding outgoing connection. See squid-cache.org/Doc/config/tcp_outgoing_address
– wurtel
Apr 26 at 11:13
I yes tried to use acls with tcp_outgoing_address using this tutoral: adamscheller.com/systems-administration/… and this another: tastyplacement.com/squid-proxy-multiple-outgoing-ip-addresses . But this doesn't work.
– Gui
Apr 26 at 16:29
3
3
Your redaction has masked potentially useful information, you haven't described what "failure" means or show what exact configuration(s) you have tried, and the behaviour you are saying you have observed does not match any known behaviour. Please provide a lot more raw material from which we can draw our own conclusions.
– womble♦
Apr 26 at 1:42
Your redaction has masked potentially useful information, you haven't described what "failure" means or show what exact configuration(s) you have tried, and the behaviour you are saying you have observed does not match any known behaviour. Please provide a lot more raw material from which we can draw our own conclusions.
– womble♦
Apr 26 at 1:42
To me the question isn't that unclear. Gui can use ACLs to match incoming connections and then use the
tcp_outgoing_address directive to select what address to use as the source address to make the corresponding outgoing connection. See squid-cache.org/Doc/config/tcp_outgoing_address– wurtel
Apr 26 at 11:13
To me the question isn't that unclear. Gui can use ACLs to match incoming connections and then use the
tcp_outgoing_address directive to select what address to use as the source address to make the corresponding outgoing connection. See squid-cache.org/Doc/config/tcp_outgoing_address– wurtel
Apr 26 at 11:13
I yes tried to use acls with tcp_outgoing_address using this tutoral: adamscheller.com/systems-administration/… and this another: tastyplacement.com/squid-proxy-multiple-outgoing-ip-addresses . But this doesn't work.
– Gui
Apr 26 at 16:29
I yes tried to use acls with tcp_outgoing_address using this tutoral: adamscheller.com/systems-administration/… and this another: tastyplacement.com/squid-proxy-multiple-outgoing-ip-addresses . But this doesn't work.
– Gui
Apr 26 at 16:29
add a comment |
0
active
oldest
votes
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
3
Your redaction has masked potentially useful information, you haven't described what "failure" means or show what exact configuration(s) you have tried, and the behaviour you are saying you have observed does not match any known behaviour. Please provide a lot more raw material from which we can draw our own conclusions.
– womble♦
Apr 26 at 1:42
To me the question isn't that unclear. Gui can use ACLs to match incoming connections and then use the
tcp_outgoing_addressdirective to select what address to use as the source address to make the corresponding outgoing connection. See squid-cache.org/Doc/config/tcp_outgoing_address– wurtel
Apr 26 at 11:13
I yes tried to use acls with tcp_outgoing_address using this tutoral: adamscheller.com/systems-administration/… and this another: tastyplacement.com/squid-proxy-multiple-outgoing-ip-addresses . But this doesn't work.
– Gui
Apr 26 at 16:29