I got set up yesterday with Verizon DSL. I had to boot into windows to do the account activation, and their tech support walked me through it. Once the connection was up, I added a hub and a second computer (with XP - it's not mine, I swear) opened a browser and began surfing. Setting up DSL on SuSE 8.2 was pretty easy, considering I don't really know what I'm doing. Yast setup for a network card and dsl went smoothly. I only had to make one file edit, to designate eth0 in pppoe.conf, rebooted the computer and then could surf, with download speeds up to 1.7M/s. I even got my firewall working with the new connection, but two things seems to have changed. SuSEfirewall2 was set not to accept pings, and it looks like it's still set that way, but Gibson Research's port scanning utility can ping me. The other thing is that before, I had to manually enter commands (iptables) to drop packets to port 119 to put it into "stealth" mode. Now, I don't have to do that, as it already appears stealthed. Can anyone explain either of these phenomena? Greg
avedis@rcn.com writes:
[...] then could surf, with download speeds up to 1.7M/s.
Just curious, is that bytes or bits? (I wasn't aware of verizon offering such a fast link)
I even got my firewall working with the new connection, but two things seems to have changed. SuSEfirewall2 was set not to accept pings, and it looks like it's still set that way, but Gibson Research's port scanning utility can ping me. The other thing is that before, I had to manually enter commands (iptables) to drop packets to port 119 to put it into "stealth" mode. Now, I don't have to do that, as it already appears stealthed. Can anyone explain either of these phenomena?
I'm not sure why you would want to drop all pings. You'll probably find that the default firewalling rules drop some kinds of ICMP packets, but there are some which are useful to keep around. (personally, I think dropping all inbound ICMP is pretty annoying when trying to diagnose network issues...) As for port 119, this appears to be the NNTP (net news) port -- why would you be running a news server I'm not sure :) -- Josh Huber
Hi greg avedis@rcn.com wrote: (snip,snip) I only had to make one file edit,
to designate eth0 in pppoe.conf, rebooted the computer and then could surf,
That "rebooted the computer" caught my eye. This is Linux, not Windows, you don't need to reboot. In SuSE you can just shutdown and restart the network with rcnetwork restart (rcnetwork is just a script in /sbin. You can browse it with less if you want to see the gory details.) doug
Well, I needed to do something, because it was acting weird. The screen was stalling for a couple seconds at a time, every few seconds. It was too annoying to proceed. This seems to happen after doing NIC setup in yast. Maybe I'll try it again to see if restarting the network helps. Thanks. Greg doug waud wrote:
Hi greg
avedis@rcn.com wrote:
(snip,snip)
I only had to make one file edit,
to designate eth0 in pppoe.conf, rebooted the computer and then could surf,
That "rebooted the computer" caught my eye. This is Linux, not Windows, you don't need to reboot. In SuSE you can just shutdown and restart the network with rcnetwork restart (rcnetwork is just a script in /sbin. You can browse it with less if you want to see the gory details.)
doug
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
Hi again Gregory Avedissian wrote:
Well, I needed to do something, because it was acting weird. The screen was stalling for a couple seconds at a time, every few seconds. It was too annoying to proceed.
Yes, I see that occasionally with KDE. But again, that is not Linux per se. I suspect KDE is not quite ready for prime time. :-) When this happens to me, I just CTRL/ALT/Fn to a plain terminal, init 3 (to kill the Xwindow mess) and then init 5 to restart it. Unless KDE is so screwed up that it has trashed to keyboard, this should work without rebooting.
This seems to happen after doing NIC setup in yast. Maybe I'll try it again to see if restarting the network helps.
I admit that Yast strikes me as slso a bit dodgy. But again, the rcnetwork restart and/or init 3 then 5 should bail you out. doug
participants (4)
-
avedis＠rcn.com -
doug waud -
Gregory Avedissian
-
Josh Huber