Two Different Gateways
Mar 11, 2007
We have used till this very moment a fixed IP address space (lets consider 192.168.0.0/25 (128 IP's), with 192.168.0.1 being the GW). Now we have run out of IP address and our provider is not able to offer us the upper IP address space on the same range we have, so we have been offered a new IP address space (let's consider 192.168.1.0/25 with 192.168.1.1 being the GW).
Both this are configured on a cisco 3550 switch (provider side). We have behind that a 3550 of our own, for subnetting and VLAN purposes (we are getting every server a /29 on a VLAN with a default GW and so on. Typical setup).
The problem is, how are we supposed to route the new ip address space? Can we add a second gateway to the 3550 and traffic will get to it if it comes from the new IP block?
We had also thought about PBR, but 3550-SMI does not seem to support that.
Can you give us a clue on the best config to solve this issue?
View 3 Replies
Jun 30, 2008
I'm trying to add a second nic to one of my servers.
eth0 is connected directly to the internet on a public IP.
eth1 is connected to a private network 172.16.0.0/24.
When I try to add the eth1, I can no longer reach my server from the public address. The gateway for eth1 is 172.16.0.1.
If I leave the gateway field blank for eth1, the server can still be reached on the public address and can also talk to clients on the lan. However, I would really like to figure out why I can't add the default gateway parameter.
View 4 Replies
View Related
Jun 7, 2007
I want to send mail to SMS gateways via setting up a free SMS site. How can I best configure qmail to handle large amounts of emails. Also, I plan to run a cron that will pull the messages to send from a db and send them in large chunks. qmail-inject and sendmail seems incredibly slow.
View 6 Replies
View Related
Dec 5, 2008
OpenVZ different gateways IP ranges, unpingable from outside world "feature" any fix?
The server main IP (eth0) is 200.44.32.42, the allocation is 200.44.32.40/29 - 200.44.32.41 being the GATEWAY.
The ADDITIONAL IP allocation is 200.44.32.96/28, 200.44.32.97 being the GATEWAY.
Now, if I be specific on /etc/sysconfig/network-scripts/ifcfg-eth0 and declare everything like so:
DEVICE=eth0
BOOTPROTO=none
BROADCAST=10.20.47.255
HWADDR=
IPADDR=10.20.42.198
NETMASK=255.255.248.0
NETWORK=10.20.40.0
ONBOOT=yes
GATEWAY=10.20.40.1
TYPE=Ethernet
Please ignore all the above IPs config.
Now, using that VE nodes on the 200.44.32.96/28 range are unpingable. How can I fix that?
Please take note that I remove all settings from ifcfg, and leave IPADDR and GATEWAY, the internet can ping the nodes. But within the 200.44.32.0/24 no-one can ping the nodes on the 200.44.32.96/28 range ( Which is my problem, that I came here to solve).
Here's the VE ...
View 7 Replies
View Related
