eth0 alias issue
Greetings fedora-list! I'm trying to add another IP address to one of my machines running FC11 and have run in to a difficult problem. I'm used to simply copying a working ifcfg-eth0 to ifcfg-eth0:1, changing DEVICE, NAME, and IPADDR and it works as expected. Not this time around.. /etc/sysconfig/network-scripts/ifcfg-eth0: DEVICE=eth0 BOOTPROTO=none DNS1=69.58.0.4 GATEWAY=69.58.21.129 HWADDR=00:10:4B:95:A1:99 IPADDR=69.58.21.130 NETMASK=255.255.255.240 ONBOOT=yes ETHTOOL_OPTS="speed 100 duplex full autoneg off" TYPE=Ethernet /etc/sysconfig/network-scripts/ifcfg-eth0:1 DEVICE=eth0:1 NAME=eth0:1 IPADDR=69.58.21.135 NETMASK=255.255.255.240 ONBOOT=yes TYPE=Ethernet After editing the file I run "ifup eth0:1" and it's bound as expected. Running "ip addr" confirms this.. 2: eth0: mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:10:4b:95:a1:99 brd ff:ff:ff:ff:ff:ff inet 69.58.21.130/28 brd 69.58.21.143 scope global eth0 inet 69.58.21.135/28 brd 69.58.21.143 scope global secondary eth0:1 inet6 fe80::210:4bff:fe95:a199/64 scope link valid_lft forever preferred_lft forever But when I reboot things go wonky. I can only access it via the new aliased IP address, and when I do the output of "ip addr" shows it's bound to eth0 and there is no mention of any aliases. 2: eth0: mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:10:4b:95:a1:99 brd ff:ff:ff:ff:ff:ff inet 69.58.21.135/28 brd 69.58.21.143 scope global eth0 inet6 fe80::210:4bff:fe95:a199/64 scope link valid_lft forever preferred_lft forever So I run "ifup eth0" and it responds with.. SIOCGIFADDR: Cannot assign requested address SIOCSIFBROADCAST: Cannot assign requested address SIOCSIFBRDADDR: Cannot assign requested address SIOCSIFFLAGS: Cannot assign requested address .. and now "ip addr" reports: 2: eth0: mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:10:4b:95:a1:99 brd ff:ff:ff:ff:ff:ff inet 69.58.21.135/28 brd 69.58.21.143 scope global eth0 inet 69.58.21.130/28 brd 69.58.21.143 scope global secondary eth0 inet6 fe80::210:4bff:fe95:a199/64 scope link valid_lft forever preferred_lft forever .. so I try "service network restart" to see what happens. Things stay the same - both IP addresses are bound to eth0 and are working as expected, but still no mention of eth0:1. It gets even stranger as when I "mv ifcfg-eth0:1 tmp-eth0" within a few seconds the second IP address stops responding, as if some daemon is watching that file and drops the interface as soon as it's removed. The output of "ip addr" confirms this: 2: eth0: mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:10:4b:95:a1:99 brd ff:ff:ff:ff:ff:ff inet 69.58.21.130/28 brd 69.58.21.143 scope global eth0 inet6 fe80::210:4bff:fe95:a199/64 scope link valid_lft forever preferred_lft forever I'm at a complete loss as to why it's behaving this way. Any ideas? Thanks, Tom Howell-Cintron -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eth0 alias issue
Mikkel L. Ellertson wrote: T. Howell-Cintron wrote: When I disable NetworkManager and enable /etc/rc.d/init.d/network everything works as expected. Because this is a headless server I'm not sure what the repercussions of reverting from NM to the old 'network' script but as long as it works I'm not going to complain. There shouldn't be any. You may run into problems on some future release, but you should get warning about it in the release notes. I hope you don't imply that NM would be the only network management allowed. Bad enough that the default network control is crippled, please don't talk away our crutch. There is still a need for machine which function without a user logged in, and which are determinant in behavior on boot and recovery from suspend and hibernate. -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eth0 alias issue
Bill Davidsen wrote: > Mikkel L. Ellertson wrote: >> T. Howell-Cintron wrote: >>> When I disable NetworkManager and enable /etc/rc.d/init.d/network >>> everything works as expected. Because this is a headless server I'm not >>> sure what the repercussions of reverting from NM to the old 'network' >>> script but as long as it works I'm not going to complain. >>> >> There shouldn't be any. You may run into problems on some future >> release, but you should get warning about it in the release notes. >> > I hope you don't imply that NM would be the only network management > allowed. Bad enough that the default network control is crippled, please > don't talk away our crutch. There is still a need for machine which > function without a user logged in, and which are determinant in behavior > on boot and recovery from suspend and hibernate. > My crystal ball has a crack in it, so I can not say for sure what F20 will be like. So I included a warning that it MAY happen. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eth0 alias issue
T. Howell-Cintron wrote: > Greetings fedora-list! > > I'm trying to add another IP address to one of my machines running FC11 > and have run in to a difficult problem. I'm used to simply copying a > working ifcfg-eth0 to ifcfg-eth0:1, changing DEVICE, NAME, and IPADDR > and it works as expected. Not this time around.. > > /etc/sysconfig/network-scripts/ifcfg-eth0: > DEVICE=eth0 > BOOTPROTO=none > DNS1=69.58.0.4 > GATEWAY=69.58.21.129 > HWADDR=00:10:4B:95:A1:99 > IPADDR=69.58.21.130 > NETMASK=255.255.255.240 > ONBOOT=yes > ETHTOOL_OPTS="speed 100 duplex full autoneg off" > TYPE=Ethernet > > /etc/sysconfig/network-scripts/ifcfg-eth0:1 > DEVICE=eth0:1 > NAME=eth0:1 > IPADDR=69.58.21.135 > NETMASK=255.255.255.240 > ONBOOT=yes > TYPE=Ethernet > Dumb question - shouldn't DEVICE be eth0 in both files? I thought it was the name of the physical device. DEVICE= Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eth0 alias issue
Mikkel L. Ellertson wrote: > > Dumb question - shouldn't DEVICE be eth0 in both files? I thought it > was the name of the physical device. > > DEVICE= devices where it is the "logical name")> > > You're correct - I wasn't paying attention. I've tried it without specifying DEVICE in ifcfg-eth0:1 but came up with the same results. Thanks, Tom -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eth0 alias issue
On Thu, 2009-07-23 at 20:32 -0500, Mikkel L. Ellertson wrote: > T. Howell-Cintron wrote: > > Greetings fedora-list! > > > > I'm trying to add another IP address to one of my machines running FC11 > > and have run in to a difficult problem. I'm used to simply copying a > > working ifcfg-eth0 to ifcfg-eth0:1, changing DEVICE, NAME, and IPADDR > > and it works as expected. Not this time around.. > > > > /etc/sysconfig/network-scripts/ifcfg-eth0: > > DEVICE=eth0 > > BOOTPROTO=none > > DNS1=69.58.0.4 > > GATEWAY=69.58.21.129 > > HWADDR=00:10:4B:95:A1:99 > > IPADDR=69.58.21.130 > > NETMASK=255.255.255.240 > > ONBOOT=yes > > ETHTOOL_OPTS="speed 100 duplex full autoneg off" > > TYPE=Ethernet > > > > /etc/sysconfig/network-scripts/ifcfg-eth0:1 > > DEVICE=eth0:1 > > NAME=eth0:1 > > IPADDR=69.58.21.135 > > NETMASK=255.255.255.240 > > ONBOOT=yes > > TYPE=Ethernet > > > Dumb question - shouldn't DEVICE be eth0 in both files? I thought it > was the name of the physical device. That is not strictly true. People on this list are found to complain that their wireless device is eth1 and their wired device is eth0. For example, the virbr0 on my machine is not physical device. What the OP is trying to do should work. > > DEVICE= devices where it is the "logical name")> > > Mikkel -- === There's no time like the pleasant. === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eth0 alias issue
Aaron Konstam wrote: >> Dumb question - shouldn't DEVICE be eth0 in both files? I thought it >> was the name of the physical device. > > That is not strictly true. People on this list are found to complain > that their wireless device is eth1 and their wired device is eth0. > For example, the virbr0 on my machine is not physical device. > > What the OP is trying to do should work. > The name is eth#, lan#, or something else is controlled by the driver. When doing an alias for eth0, shouldn't DEVICE still be eth0? It is still the same physical device. It is a different story when you get into things like VPN and bridging. But you don't use DEVICE is bridges or VPNs... Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eth0 alias issue
T. Howell-Cintron wrote: > Greetings fedora-list! > > I'm trying to add another IP address to one of my machines running FC11 > and have run in to a difficult problem. I'm used to simply copying a > working ifcfg-eth0 to ifcfg-eth0:1, changing DEVICE, NAME, and IPADDR > and it works as expected. Not this time around.. > When I disable NetworkManager and enable /etc/rc.d/init.d/network everything works as expected. Because this is a headless server I'm not sure what the repercussions of reverting from NM to the old 'network' script but as long as it works I'm not going to complain. Thanks, T. Howell-Cintron -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eth0 alias issue
T. Howell-Cintron wrote: > > When I disable NetworkManager and enable /etc/rc.d/init.d/network > everything works as expected. Because this is a headless server I'm not > sure what the repercussions of reverting from NM to the old 'network' > script but as long as it works I'm not going to complain. > There shouldn't be any. You may run into problems on some future release, but you should get warning about it in the release notes. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
