FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 05-16-2008, 11:31 PM
"Jeff Spaleta"
 
Default F9 potential service network bug?

On Fri, May 16, 2008 at 3:32 PM, Paul Wouters <paul@xelerance.com> wrote:
> To be honest, NM/avahi combo was not tested well enough. Even a stock
> install with selecting "static" via anaconda ended up not working.

I'll make an extra special effort to invite static users to
participate in testing in the upcoming release cycle.

-jef

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-16-2008, 11:40 PM
Jesse Keating
 
Default F9 potential service network bug?

On Fri, 2008-05-16 at 19:32 -0400, Paul Wouters wrote:
> I'd have figured BOOTPROTO=static would not be that hard to support :P

Static works. Bridging is what's not supported right now.

--
Jesse Keating
Fedora -- Freedom˛ is a feature!
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-17-2008, 01:57 AM
Dan Williams
 
Default F9 potential service network bug?

On Fri, 2008-05-16 at 19:32 -0400, Paul Wouters wrote:
> On Fri, 16 May 2008, Jeff Spaleta wrote:
>
> > NM doesn't handle all usage cases yet, which is why the legacy network
> > stack is still available for people who need it.
>
> I'd have figured BOOTPROTO=static would not be that hard to support :P
>
> > -jef"Rome wasn't built in a day and all that jazz"spaleta
>
> To be honest, NM/avahi combo was not tested well enough. Even a stock
> install with selecting "static" via anaconda ended up not working.

I've personally tested static IP addressing with static DNS servers with
anaconda on the F9 release LiveCD, and it worked fine for me through
multiple tests. What's not working for you? Can you attach the ifcfg
files anaconda generated right after you installed?

Dan


--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-17-2008, 03:26 AM
Chris Ricker
 
Default F9 potential service network bug?

On Fri, 16 May 2008, Dan Williams wrote:

> I've personally tested static IP addressing with static DNS servers with
> anaconda on the F9 release LiveCD, and it worked fine for me through
> multiple tests. What's not working for you? Can you attach the ifcfg
> files anaconda generated right after you installed?

Multiple people (including me) have put non-working examples in the mother
of all NM bugzilla tickets ;-)

Have you tried non-LiveCD?

later,
chris

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-17-2008, 03:47 AM
Paul Wouters
 
Default F9 potential service network bug?

On Fri, 16 May 2008, Chris Ricker wrote:

> > I've personally tested static IP addressing with static DNS servers with
> > anaconda on the F9 release LiveCD, and it worked fine for me through
> > multiple tests. What's not working for you? Can you attach the ifcfg
> > files anaconda generated right after you installed?
>
> Multiple people (including me) have put non-working examples in the mother
> of all NM bugzilla tickets ;-)
>
> Have you tried non-LiveCD?

Mine was from a non-LiveCD. The ifcfg files generated look fine:

# Intel Corporation 82557/8/9/0/1 Ethernet Pro 100
DEVICE=eth0
BOOTPROTO=static
HWADDR=00:d0:b7:85:f6:03
ONBOOT=no
DHCP_HOSTNAME=bofh.xelerance.com

# Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet
DEVICE=eth1
BOOTPROTO=static
HWADDR=00:0c:76:bc:9b:d1
IPADDR=193.110.157.17
NETMASK=255.255.255.248
ONBOOT=yes

eth0 has (or had) no link during install.

To be it looked like despite being confgured with BOOTPROTO=static, the
avahi daemon and NetworkManager got started, and one of them started
doing dhcp. The static IP did appear as an additiona IP on the eth1
interface, but since the DHCP was the main address, my public ip address
changed.

Paul

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-19-2008, 07:01 PM
Bill Nottingham
 
Default F9 potential service network bug?

Paul Wouters (paul@xelerance.com) said:
> Mine was from a non-LiveCD. The ifcfg files generated look fine:
>
> # Intel Corporation 82557/8/9/0/1 Ethernet Pro 100
> DEVICE=eth0
> BOOTPROTO=static
> HWADDR=00:d0:b7:85:f6:03
> ONBOOT=no
> DHCP_HOSTNAME=bofh.xelerance.com
>
> # Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet
> DEVICE=eth1
> BOOTPROTO=static
> HWADDR=00:0c:76:bc:9b:d1
> IPADDR=193.110.157.17
> NETMASK=255.255.255.248
> ONBOOT=yes
>
> eth0 has (or had) no link during install.
>
> To be it looked like despite being confgured with BOOTPROTO=static, the
> avahi daemon and NetworkManager got started, and one of them started
> doing dhcp. The static IP did appear as an additiona IP on the eth1
> interface, but since the DHCP was the main address, my public ip address
> changed.

ONBOOT=no means that NM won't try to automatically bring it up. That
may be what you're seeing.

Bill

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-19-2008, 07:36 PM
Dan Williams
 
Default F9 potential service network bug?

On Fri, 2008-05-16 at 23:47 -0400, Paul Wouters wrote:
> On Fri, 16 May 2008, Chris Ricker wrote:
>
> > > I've personally tested static IP addressing with static DNS servers with
> > > anaconda on the F9 release LiveCD, and it worked fine for me through
> > > multiple tests. What's not working for you? Can you attach the ifcfg
> > > files anaconda generated right after you installed?
> >
> > Multiple people (including me) have put non-working examples in the mother
> > of all NM bugzilla tickets ;-)
> >
> > Have you tried non-LiveCD?
>
> Mine was from a non-LiveCD. The ifcfg files generated look fine:
>
> # Intel Corporation 82557/8/9/0/1 Ethernet Pro 100
> DEVICE=eth0
> BOOTPROTO=static
> HWADDR=00:d0:b7:85:f6:03
> ONBOOT=no
> DHCP_HOSTNAME=bofh.xelerance.com

Bill figured this one out.

> # Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet
> DEVICE=eth1
> BOOTPROTO=static
> HWADDR=00:0c:76:bc:9b:d1
> IPADDR=193.110.157.17
> NETMASK=255.255.255.248
> ONBOOT=yes

And for this one, I'm building:

http://koji.fedoraproject.org/koji/taskinfo?taskID=618281

which will pull the gateway out of /etc/sysconfig/network, which seems
to be where the non-LiveCD installer puts the gateway. Not sure why the
livecd and the non-livecd cases are different, but this update should
fix it.

Dan

> eth0 has (or had) no link during install.
>
> To be it looked like despite being confgured with BOOTPROTO=static, the
> avahi daemon and NetworkManager got started, and one of them started
> doing dhcp. The static IP did appear as an additiona IP on the eth1
> interface, but since the DHCP was the main address, my public ip address
> changed.
>
> Paul
>

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-20-2008, 12:09 AM
Paul Wouters
 
Default F9 potential service network bug?

On Mon, 19 May 2008, Bill Nottingham wrote:

> > ONBOOT=yes
> >
> > To me it looked like despite being confgured with BOOTPROTO=static, the
> > avahi daemon and NetworkManager got started, and one of them started
> > doing dhcp. The static IP did appear as an additiona IP on the eth1
> > interface, but since the DHCP was the main address, my public ip address
> > changed.
>
> ONBOOT=no means that NM won't try to automatically bring it up. That
> may be what you're seeing.

Are you saying that ONBOOT= changed its meaning from "start at boot or not"
to "start at boot, but either with NM or without" ?

What combination of BOOTPROTO= and ONBOOT= will both "start on boot" and
"not use NM"? BOOTPROTO=static and ONBOOT=no. That would be odd (and breaking
the API for ONBOOT without a proper migration on update)

Paul

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-20-2008, 12:57 AM
Dan Williams
 
Default F9 potential service network bug?

On Mon, 2008-05-19 at 20:09 -0400, Paul Wouters wrote:
> On Mon, 19 May 2008, Bill Nottingham wrote:
>
> > > ONBOOT=yes
> > >
> > > To me it looked like despite being confgured with BOOTPROTO=static, the
> > > avahi daemon and NetworkManager got started, and one of them started
> > > doing dhcp. The static IP did appear as an additiona IP on the eth1
> > > interface, but since the DHCP was the main address, my public ip address
> > > changed.
> >
> > ONBOOT=no means that NM won't try to automatically bring it up. That
> > may be what you're seeing.
>
> Are you saying that ONBOOT= changed its meaning from "start at boot or not"
> to "start at boot, but either with NM or without" ?

NM interprets ONBOOT=no as "don't autoconnect this configuration". They
are just about the same thing. If you mark ONBOOT=no then NM won't
bring the device up on boot.

> What combination of BOOTPROTO= and ONBOOT= will both "start on boot" and
> "not use NM"? BOOTPROTO=static and ONBOOT=no. That would be odd (and breaking
> the API for ONBOOT without a proper migration on update)

Try:

NM_CONTROLLED=no
ONBOOT=yes

Dan

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 

Thread Tools




All times are GMT. The time now is 07:36 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org