Internal ip can't talk to the internet, PLEASE HELP
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Internal ip can't talk to the internet, PLEASE HELP
Hello guys,
I have problem.
I configured an internal fake ip 192.168.1.11 on a virtual interface of my server.
I'm running one of my postfix instances on this ip.
The problem is that postfix can't talk to external hosts on the internet when running from this internal ip 192.168.1.11
I get an error in the mail log
Feb 21 22:43:00 localhost postfix-R1/smtp[11372]: connect to 7zips.com[109.169.46.199]:25: Connection timed out
It works fine when I run postfix on real ips, but I need it to work from the internal.
I thought it should just work.
Am I missing anything?
Is the "fake" IP on the same network as your real gateway ?
No, my gateway is on the same network as real IPs on this server 91.210.107.102, 91.210.107.102 which work fine
Destination Gateway Genmask Flags Metric Ref Use Iface
default 91.210.107.65 255.255.255.255 UGH 0 0 0 eth0
and the internal ip is 192.168.1.11
but its all on the same server, so I thought it should just work for outbound traffic.
Am I missing something?
Yes, you are missing something: basic subnetting. If there is no pathway from one subnet to another (usually called a gateway), two two subnets can't communicate.
Check this out--it's the best intro to subnetting that I've seen:
Yes, you are missing something: basic subnetting. If there is no pathway from one subnet to another (usually called a gateway), two two subnets can't communicate.
Check this out--it's the best intro to subnetting that I've seen:
I'm still not clear whether you need to enable a connection from the 192.168.1.x subnet to the 91.210.107.x subnet or from 192.168.1.x to the Big Wide World of the inner tubes or from 192.168.1.x to the Big Wide World via 91.210.107.x.
How to do it with your virtualization setup will depend on what virtualization engine you are using. The answer is likely specific to how your virtualization product works.
I would suggest you check the docs for that product to find out how to enable it to communicate with other networks.
If you want us to help you, you need to let us know what virtualization product you are using: VirtualBox, VMWare, or what? Different virtualization products will work in different ways.
It would probably help to know what Linux platform you are using; too much information is better than too little when it comes to trouble-shooting.
I have some experience with VirtualBox as a hobbyist and might be able to help with that, but I am not a virtualization guru by any means.
I'm still not clear whether you need to enable a connection from the 192.168.1.x subnet to the 91.210.107.x subnet or from 192.168.1.x to the Big Wide World of the inner tubes or from 192.168.1.x to the Big Wide World via 91.210.107.x.
How to do it with your virtualization setup will depend on what virtualization engine you are using. The answer is likely specific to how your virtualization product works.
I would suggest you check the docs for that product to find out how to enable it to communicate with other networks.
If you want us to help you, you need to let us know what virtualization product you are using: VirtualBox, VMWare, or what? Different virtualization products will work in different ways.
It would probably help to know what Linux platform you are using; too much information is better than too little when it comes to trouble-shooting.
I have some experience with VirtualBox as a hobbyist and might be able to help with that, but I am not a virtualization guru by any means.
I need to communicate from 192.168.1.x to the Big Wide World.
It's not a virtual, its a dedicated server.
Ok, here is the weird part, I just did a test
# ping -I 192.168.1.11 7zips.com
PING 7zips.com (109.169.46.199) from 192.168.1.11 : 56(84) bytes of data.
64 bytes from 109.169.46.199: icmp_seq=1 ttl=56 time=53.4 ms
So it looks like everything is working like I thought it should, because my internal ips are on the same server as real working ones.
but when I run postfix on inet_interfaces = 192.168.1.11
when I try to send mail through 192.168.1.11 I get an error in the mail log
Feb 22 00:59:09 localhost postfix-R1/smtp[13547]: connect to 7zips.com[109.169.46.199]:25: Connection timed out.
Also when I telnet 7zips.com 25 from my server it connects but when I do it from my house,
Connecting To 7zips.com...
Then in about 20 seconds I get
Could not open connection to the host, on port 25: Connect failed
I'm trying to connect to my other postfix server to relay email.
But I'm not sure where in the config it restricts source ips.
first of all it will NEVER work on that ip beacuse it is a prive network ip ... ergo the interface of your provider will drop every thing it sees coming from that ip .
first of all it will NEVER work on that ip beacuse it is a prive network ip ... ergo the interface of your provider will drop every thing it sees coming from that ip .
I'm trying to relay this to my other postfix server
I have mynetworks = 192.168.1.11 on the receiving server but they are not on the same ISP.
I know it can talk to this server because
ping -I 192.168.1.11 7zips.com
PING 7zips.com (109.169.46.199) from 192.168.1.11 : 56(84) bytes of data.
64 bytes from 109.169.46.199: icmp_seq=1 ttl=56 time=53.4 ms
So how do I configure my receiving postfix to accept mail from my private address?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.