Sample non-NetworkManager config (ala: if*)

[neptho]

Hi all,

I’m a recent convert - I’ve been BSD and Debian for years, but after opting to “waste a CD and a weekend” on 10.3, I have found a new home. Despite my disdain for zypper (and the over-engineering that means it takes 10 minutes to do a 3 second task), SuSE feels just about right.

I’ve always been one to ‘cut my own wood’, as it were, and being reliant upon NetworkManager is not what I’d like to be.

I created a /etc/sysconfig/network/ifcfg-wlan0 (after repairing the ethernet device in udevd to be wlan0, not wlan0_rename), and no matter what I do, ifup/ifdown state that the device is managed by NetworkManager.

Other than beating on the keyboard until YaST opens and says ‘make this a manual config device’, what are my options to make it load before X11?

NetworkManager works 100% in SuSE so far, unlike any other Linux derivative, but I just don’t like using it. I want my /etc/network/interfaces and a tree, dang it!

I’ve looked at SuSE 9, and earlier 10.x docs, but am still unable to answer myself. Any pointers will be greatly appreciated.

Thanks!

[swerdna]

Hi
You can switch control from NetworkManager to ifup/down in Yast. GoTo Yast → Net devices → net card → global options: put the dot in “traditional ifup” rather than in “NetworkManager”

[neptho]

Hi swerdna,

Thanks for your reply.

When I do that, it will config “up” the interface, but it never establishes the default gateway route. I’m on 10.3 w/ all (current) updates.

[swerdna]

@neptho

Hi swerdna,

Thanks for your reply.

When I do that, it will config “up” the interface, but it never establishes the default gateway route. I’m on 10.3 w/ all (current) updates.

You can define the gateway in Yast, check out Pics numbered 7 and 8 in this tutorial: HowTo Configure a network card in Suse/openSUSE 10.x for LAN and Internet Access.

Not exactly cutting wood, but you’ll get ideas.

[lccts1]

neptho, I’d like to work with you through the gateway issue when using traditional ifup. I’m not a fan of networkmanager either. Ironically, I had exactly the opposite problem earlier today when doing a fresh 10.3 install to work on another problem; Networkmanager got an IP but wouldn’t add gateway. I switched to traditional and, bam, gateway. Traditional has never failed me so you’ve piqued my interest.

1. run “dhcpcd-test eth0” (or eth1, blah blah) and verify that your machine is getting a gateway in the dhcp response.

2. check /etc/sysconfig/network/dhcp and make sure DHCLIENT_SET_DEFAULT_ROUTE=“yes”

[neptho]

@swerdna

You can define the gateway in Yast, check out Pics numbered 7 and 8 in this tutorial: HowTo Configure a network card in Suse/openSUSE 10.x for LAN and Internet Access.

Not exactly cutting wood, but you’ll get ideas.

That kind of destroys the point of using DHCP, no? Thanks for the assistance.

@lccts1

neptho, I’d like to work with you through the gateway issue when using traditional ifup. I’m not a fan of networkmanager either. Ironically, I had exactly the opposite problem earlier today when doing a fresh 10.3 install to work on another problem; Networkmanager got an IP but wouldn’t add gateway. I switched to traditional and, bam, gateway. Traditional has never failed me so you’ve piqued my interest.

1. run “dhcpcd-test eth0” (or eth1, blah blah) and verify that your machine is getting a gateway in the dhcp response.

2. check /etc/sysconfig/network/dhcp and make sure DHCLIENT_SET_DEFAULT_ROUTE=“yes”

Hi lccts1,

Thanks for your assistance; I am being sent the gateway in the response, and I do have it set to set the default route. It’s incredibly bizarre that it just doesn’t get ‘setup’ with the ifup system.

[neptho]

And, the results:

vostramos:/home/shawn # dhcpcd-test wlan0 | grep GATEWAY
GATEWAY=192.168.0.1
vostramos:/home/shawn # grep DEFAULT_ROUTE /etc/sysconfig/network/dhcp
DHCLIENT_SET_DEFAULT_ROUTE="yes"

The only thing I have done was remove the ipw3945d package since I’m using iwl3945, and I detest that thing.

[cookdav]

@neptho

Hi swerdna,

Thanks for your reply.

When I do that, it will config “up” the interface, but it never establishes the default gateway route. I’m on 10.3 w/ all (current) updates.

make sure that you have no OTHER device that gets setup
for boot-time, or else the default-route won’t get set.

e.g. if your hard-wired interface is enabled at boot, go
in and change it to ‘manually’ or ‘never’, and then
your wireless should get its default-route.

Hope this helps…

Dave

[swerdna]

DHCP assigns an IP address. I didn’t think it was tasked to supply Name Servers or the gateway. I could be wrong (often am wrong), am I wrong?

[neptho]

@cookdav

make sure that you have no OTHER device that gets setup
for boot-time, or else the default-route won’t get set.

Hmm, I do have an eth0 device, but I have set that to manual/off. Or, so YaST claims.

Can I just set a different metric for eth0 and turn it to ‘automatic’?

I used to do a nasty hack in Debian to grep the ifconfig status for a connection, and if found, it’d attempt dhcp on the interface, otherwise, it would be ignored.

@swerdna

DHCP assigns an IP address. I didn’t think it was tasked to supply Name Servers or the gateway. I could be wrong (often am wrong), am I wrong?

It depends on what RFC you’re reading at the time. In common use, DHCP services have supplied this information for many years.

[swerdna]

It depends on what RFC you’re reading
What’s an RFC?

[user]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Request for Comments. Google will give you 21M hits if you search for
it including:

http://en.wikipedia.org/wiki/Request_for_Comments

Good luck.

swerdna wrote:
|> It depends on what RFC you’re readingWhat’s an RFC?
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIVDnP3s42bA80+9kRAqwGAJsEk9qFpRKVLZnESN/iBUXiQFyo1wCeJZC2
5Ach6vFtikR5l7+cT78g8X8=
=eBe0
-----END PGP SIGNATURE-----

[cookdav]

@swerdna

What’s an RFC?

Google:
define: RFC