| | |
Assigning IPs to one NIC
![]() |
How many IPs can I configure on Linux system on one NIC ??
If its different for freeBSD, Fedora and RedHat Linux then whats the exact figures for each ....
If its different for freeBSD, Fedora and RedHat Linux then whats the exact figures for each ....
That's actually a tough question to answer. I can tell you, though, that Fedora and RedHat will likely be the same. You will probably have to manually configure them via the ifconfig command, rather than using the GUI tools, as they usually only support one address per interface.
I tried going through the source code for both FreeBSD and Linux, but really didn't find a way to go. Perhaps this would be a great question to pose to each the Linux and FreeBSD kernel developers' Network mailing lists?
I tried going through the source code for both FreeBSD and Linux, but really didn't find a way to go. Perhaps this would be a great question to pose to each the Linux and FreeBSD kernel developers' Network mailing lists?
Alex Cavnar, aka alc6379
•
•
•
•
Originally Posted by alc6379
I tried going through the source code for both FreeBSD and Linux, but really didn't find a way to go. Perhaps this would be a great question to pose to each the Linux and FreeBSD kernel developers' Network mailing lists?
Example:
alias_fxp0="inet 10.0.3.4 netmask 255.255.255.0"
If you spend more on coffee than on IT security, you will be hacked.
What's more, you deserve to be hacked.
-- former White House cybersecurity czar Richard Clarke
What's more, you deserve to be hacked.
-- former White House cybersecurity czar Richard Clarke
•
•
•
•
Originally Posted by nanosani
How many IPs can I configure on Linux system on one NIC ??
If its different for freeBSD, Fedora and RedHat Linux then whats the exact figures for each ....
[ifcfg-eth1]
DEVICE=eth1
BOOTPROTO=none
HWADDR=00:D0:B7:4D:50:ED
ONBOOT=yes
USERCTL=no
PEERDNS=yes
TYPE=Ethernet
IPADDR=192.168.0.102
NETMASK=255.255.255.0
NETWORK=192.168.0.0
BROADCAST=192.168.0.255
GATEWAY=192.168.0.1
[ifcfg-eth1:1]
DEVICE=eth1:1
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.0.121
NETMASK=255.255.255.0
USERCTL=no
IPV6INIT=no
PEERDNS=yes
GATEWAY=192.168.0.1
TYPE=Ethernet
These files are located in /etc/sysconfig/network-scripts. Configuring these through the GUI utilities will work almost as well as manually editing the files yourself.
Hope this helps.
--
Later...
"Wherever you go, there you are." -- Buckaroo Banzai
Later...
"Wherever you go, there you are." -- Buckaroo Banzai
•
•
•
•
Originally Posted by hagcomcol
Here's how we do it where I work. Just set up an alias for the ethernet port you want to apply multiple IP addresses to. Theoretically you could apply as many IP addresses to an ethernet port as you want. We typically have never used more than 4. We're also using RedHat Enterprise Linux Server v3/v4.
[ifcfg-eth1]
DEVICE=eth1
BOOTPROTO=none
HWADDR=000:B7:4D:50:ED
ONBOOT=yes
USERCTL=no
PEERDNS=yes
TYPE=Ethernet
IPADDR=192.168.0.102
NETMASK=255.255.255.0
NETWORK=192.168.0.0
BROADCAST=192.168.0.255
GATEWAY=192.168.0.1
[ifcfg-eth1:1]
DEVICE=eth1:1
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.0.121
NETMASK=255.255.255.0
USERCTL=no
IPV6INIT=no
PEERDNS=yes
GATEWAY=192.168.0.1
TYPE=Ethernet
These files are located in /etc/sysconfig/network-scripts. Configuring these through the GUI utilities will work almost as well as manually editing the files yourself.
Hope this helps.
•
•
•
•
Originally Posted by nanosani
And thats why I was asking ... how many aliases like these can I make in Linux?
/proc/sys/net/core/net_aliax_max
Does that answer your question?
--
Later...
"Wherever you go, there you are." -- Buckaroo Banzai
Later...
"Wherever you go, there you are." -- Buckaroo Banzai
One of the things not pointed out here was the ability of the alias
to exist on more than one subnet. Meaning eth0 is the first and eth:1
the second in traditionial fashion. This comes in really handy when merging
domains or for load balancing applications such as Oracle.
In the most basic sence, you can really name it anything as long as
the mac addresses are bound to the correct common device. You can
even go as far as to edit the scripts and files by hand in
/etc/sysconfig/network*.
just copy the initial eth0 files to the new name and edit appropriately.
after:
ifup eth0:1
or the like or simply:
service network restart
you can also use miitool or the current version, ethtool
to set persistant forced speeds, duplexing and whatnot.
gotta love it!
to exist on more than one subnet. Meaning eth0 is the first and eth:1
the second in traditionial fashion. This comes in really handy when merging
domains or for load balancing applications such as Oracle.
In the most basic sence, you can really name it anything as long as
the mac addresses are bound to the correct common device. You can
even go as far as to edit the scripts and files by hand in
/etc/sysconfig/network*.
just copy the initial eth0 files to the new name and edit appropriately.
after:
ifup eth0:1
or the like or simply:
service network restart
you can also use miitool or the current version, ethtool
to set persistant forced speeds, duplexing and whatnot.
gotta love it!
I used up all my money on you baby...
... and I want it BACK.
... and I want it BACK.
![]() |
Similar Threads
- Configuring mac's built-in firewall (Darwin, X11 and BSD)
- FreeBSD only assigning inet6 addresses to ndis0 (*nix Software)
- ME to XP home network problem (Windows NT / 2000 / XP)
Other Threads in the *nix Software Forum
- Previous Thread: Bench-marks of MySQL compared to Oracle
- Next Thread: Deleted /home
| Thread Tools | Search this Thread |







0:B7:4D:50:ED