Re: Problem with multi-aliases network interfaces

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Is the same case Bruno?

A wifi iface and ethernet iface with many alises?
Or is more generic case?

The question is because I have many servers now with FC5 with multi-aliases ethernet ifaces and have no problem (at least this problem).

Anyone could confirm this problem and the workaround provided by Bruno?

Bruno Wolff III escribió:
On Wed, Apr 19, 2006 at 15:09:51 +0200,
  Samuel Díaz García <samueldg@xxxxxxxxxxxx> wrote:
Please help!!!

I have already bugzilla'd this (188321). You can work around the problem
by editing the config files for the alias interfaces (e.g. /etc/sysconfig/network-scripts/ifcfg-eth1:1) and removing all definitions
other than IPADDR and NETMASK. For example my eth1:1 file contains:
IPADDR=10.0.0.2
NETMASK=255.0.0.0

Samuel Díaz García escribió:
Distro: FC5

My network devices:
  eth1: ipw2200 (intel 2915 abg wifi).
  eth0: tg3 (broadcom gigabit etherner).

I'm using static ip's in all ifaces, and wpa_supplicant over eth1.

The problem is:

  a) only eth1 and eth0 configured with static ip's don't have problems.
b) when add more ips over eth0, as eth0:1, eth0:2, etc... with IPs over diferent IP subnetworks, the "network" init script appear to forgot the type of eth0 ifaces and when "service network restart" or when rebooting computer, my eth0 iface (and eth0:1 and so on) are lost.

I think that the problem were system-config-network app (that appears to be some problems with aliases and naming/saving new ifaces data), but manually revised and corrected ifcfg-eth0?? files (after adding them with system-config-network) and rebooting, the network script appears to think that eth0 (tg3 driver) is a wireless device and try to assign the wifi info (and I think is a bit confused the initialization of eth0:1 with the iface eth1).

A think anything were broken on last initscripts package update.

More info:
a) eth0:? are marked as dependant on eth0, as they go up when eth0 go up.
  b) I have configured wpa_supplicant over eth1 and eth1 is working fine.

Any patch/help to apply over the last "network" init script?

Thanks

--
   Samuel Díaz García
    Director Gerente
ArcosCom Wireless, S.L.L.

CIF: B11828068
c/ Romero Gago, 19
Arcos de la Frontera
11630 - Cadiz

http://www.arcoscom.com

mailto:samueldg@xxxxxxxxxxxx
msn: samueldg@xxxxxxxxxxxx

Móvil: 651 93 72 48
Tlfn.: 956 70 13 15
Fax:   956 70 34 83

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list


--
   Samuel Díaz García
    Director Gerente
ArcosCom Wireless, S.L.L.

CIF: B11828068
c/ Romero Gago, 19
Arcos de la Frontera
11630 - Cadiz

http://www.arcoscom.com

mailto:samueldg@xxxxxxxxxxxx
msn: samueldg@xxxxxxxxxxxx

Móvil: 651 93 72 48
Tlfn.: 956 70 13 15
Fax:   956 70 34 83


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux