|
|
|
|
||||
|
Welcome to the GoFuckYourself.com - Adult Webmaster Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact us. |
|
|||||||
| New Webmasters ask "How-To" questions here. This is where other fucking Webmasters help. |
|
|
Thread Tools |
10-14-2013, 01:50 PM
|
#1 | |||
|
Confirmed User
Industry Role:
Join Date: Nov 2005
Posts: 1,251
|
Incorrect netmask in network configuration
Hi guys,
I had some problems with netmask of my additional IPs that was showing 255.255.255.0 instead of 255.255.255.255. I fixed that and contacted my hosting provider support to confirm if everything was correct with the new IP configuration showing the log of the command "ifconfig": Quote:
And they said this: Quote:
Code:
sed -i 's/94.23.78.255/94.23.78.68/g' /etc/ips; /etc/init.d/ipaliases restart Here goes the log: Quote:
1- I don't have 'eth0:0' anymore,now I have a 'eth0:cp1' and 'eth0:cp2', it seems that was renamed. Is this ok? 2- It seems that eth0:cp1 is fine now: inet addr:94.23.78.68 Bcast:94.23.78.68 Mask:255.255.255.255 But eth0:cp2 (old eth0:0 that was already fine) is not: inet addr:178.32.52.69 Bcast:178.32.52.255 Mask:255.255.255.255 Any ideas? Can someone help me with these? Thank you guys! Regards!! |
|||
|
|
|
10-14-2013, 07:06 PM
|
#2 |
|
Guest
Posts: n/a
|
Why would you even need a netmask.
|
|
|
|
10-16-2013, 06:17 AM
|
#3 | |
|
Confirmed User
Industry Role:
Join Date: Jan 2003
Location: In a Tater Patch
Posts: 2,321
|
Quote:
These are subinterfaces and a method of adding additional IP addresses along with their subnets to an interface. The part after the colon is arbitrary. iptables cannot reference subinterfaces, so any rules required would be based on IP addresses, but bound to the physical interface if required. As far as netmasks go. having a /32 netmask on an alias ip is fine actually. since the only one that matters is the netmask that defines the default route which is accessible is the main IP on the box, well you could use any actually as long as your default gateway is pointing to an aces sable IP on that netmask. Since they are different ips not in the same broadcast domain issuing a /32 on each IP is the correct way to do this masking. Now with that being said this is actually HORRIFIC practice and VERY poor network design which will lead into a lot of "shit talking" on the broadcast domain, lots of crap traffic and actually you are vulnerable to a broadcast flood on the broadcast domain, which would take you down and everyone else on that broadcast domain if it was to happen. In short this his horrible, while I realize this is OVH.. its not a real good design to do.
__________________
Managed Hosting - Colocation - Network Services Yellow Fiber Networks icq: 19876563 |
|
|
|
|
|
10-16-2013, 07:56 AM
|
#4 |
|
Confirmed User
Industry Role:
Join Date: Nov 2005
Posts: 1,251
|
Spudstr, thank you for your reply buddy.
So what do you suggest to do? Thanks once again! |
|
|
|
|
10-16-2013, 09:52 AM
|
#5 | |
|
Confirmed User
Industry Role:
Join Date: Jan 2003
Location: In a Tater Patch
Posts: 2,321
|
Quote:
Unless they just don't work? then that is a different set of issues.
__________________
Managed Hosting - Colocation - Network Services Yellow Fiber Networks icq: 19876563 |
|
|
|
|
