Greetings all, this is possibly the most ridiculous thing I have encountered so far.

Current Distro : Slackware 11.0
eth1 : DWL-520 Wireless Adapter
eth0 : VIA Rhine II onboard

I have my wireless eth1 running, if I activate my eth0 (a VIA Rhine II onboard) eth1 is still active, with an ip address, it just can no longer access the internet, but if I deactivate eth0 it begins to work again immediately. I can flip it off and on and it works like a light switch. As long as eth0 is on, I cannot have internet.

I am trying to accomplish ip forwarding, Computer to Xbox. I have it to the point where I can finally get it to detect an ip address, but that requires eth0 to be on, so it gets an ip address but no internet. But if I turn eth0 off, I get internet, but none going to the Xbox, defeating the whole purpose of this.

I've been using firestarter to accomplish this, but that makes 0% difference.

If eth0 and eth1 = ON, then internet = NO
If eth0 = OFF and eth1 = ON then internet = YES

Stupidest crap ever.

I should also mention that I have problems activating my hardware in the KDE configurator, however the GNOME happily activates it. (I installed Dropline Gnome, so I have both configurators to use.)

Brilliantly enough, Network Tools, when both interfaces are active, claims activity is happening for both, but internet does NOT work if they are both active.


Any help is appreciated, thank you much for viewing this.

Are you, by any chance, running the rc.networkmanager that is supplied with the Dropline GNOME 2.16.1 pre-release? Network Manager doesn't support more than one DHCP interface at a time right now, so depending upon your configuration, that can cause some hangups.

If you think that it is operating in err, chmod -x rc.networkmanager and rc.dhcdbd. Then restart and see if it's working the way you'd prefer. Slackware's dhcp stuff is a bit whacked out, and isn't completely ideal for this tool in some configurations.

It is, in fact, designed to not run if you have more than one interface configured, but bringing it up manually after startup could override that. Not sure if it is the issue you are having, but it's worth looking at.

I figured I should just remove dropline-gnome, it was conflicting with KDE's configurator. dropline didn't work anyway, gave me too much crap about dbus and some xorg nonsense. I had downloaded dropline because I needed those gnome libraries.

This caused a major problem, because gdm set itself as the boot manager and without it, Slack could no longer boot. So I reinstalled Slack.

Now I am back to square one. I need to find out the easiest way to compile Firestarter.
It requires many gnome libs that aren't easily buildable because of dependency hell. Has anyone had success building this piece or know of an easier means? (found a .tgz for an older version once, but of course it didn't work without gnome libs : )

::::::: In response to zborgerd's suggestion :::::

I chmod -x'd that stuff and rebooted, stuff was more funkified than before, but manageable at best. It solved 0 problems as there was still the conflict of dropline's configurator (which, if I didn't mention, I was running in KDE) with KDE's. KDE's refused to activate the interface, shouting errors at me because of the conflict, while Gnome rampantly enabled it, causing the original problem.

I'm figuring if I could just get firestarter installed without say... dropline, I think my problems would be at least 50% solved then.

Thanks guys.

If you are using 2.16.x, then there is no X.org stuff. I'm not certain what you are referring to.

You can manually set the boot manager from GDM to KDM or XDM. Slackware tells the system to use GDM first, if it is installed. You can comment out the GDM stuff in /etc/rc.d/rc.4. Sometimes it helps to ask someone before making assumptions about a problem.

I'm not sure what to suggest then. If you have rc.networkmanager disabled, then things function as if nothing were ever changed on a default Slackware installation.

Oh, I mean, GDM decided to become my default graphical login.
I hadn't set inittab to level 4 yet, so I was still doing it from the terminal, but Dropline decided to do it by itself. Either way it's moot now, I reinstalled Slack 11.
Now everything functions properly, I can activate both interfaces at the same time, now I just need to get ipforwarding to work.

I did much research on iptables, but writing my own rules seems to do no good since I'm going by what I see on the net.

In simple terms, this entire quest has been to get what's coming into eth1, to go out eth0.

Dropline does not "decide" which runlevel you will use. Slackware defaults to runlevel 3 and it stays that way unless you change it. The GDM startup stuff is hardcoded into Slackware's rc.4. Even though PV doesn't include GNOME anymore, he still defaults to GDM if it is on the system.