Re: [expert] 9.0 Networking === ARGHHHHHHHHHHHHHHHHHHH
On 21 Nov 2002 23:15:26 -0500 Robert Wohlfarth [EMAIL PROTECTED]
wrote:
On Thu, 2002-11-21 at 00:04, Pierre Fortin wrote:
* just enabling modem access resulted in shorewall being silently
enabled... When I tried to switch back to LAN mode, I was unable to
connect to ANYTHING...
The default Shorewall configuration is setup for an ethernet card
(eth0). It blocks access to everything on ppp0 (the dial up connection).
This link provides a proper configuration:
http://shorewall.net/standalone.htm
Thanks -- I'll look at this; but my point to Mandrake is still that this
is a laptop that:
- worked on a LAN
- worked on a dialup
- would not work on a LAN again until I found that shorewall came into the
picture SILENTLY*
* and NO, /var/log/{messages,syslog} does NOT count as notification -- how
many people expect to have networking DISABLED by simply switching from
LAN to dial and back to LAN...
Hopefully future Mandrake releases will configure Shorewall during
install. Wouldn't want dial-up users to give up on Mandrake when there's
no Internet connection.
My problem was not going to dialup; it was going back to LAN...
BTW, I also got some screen captures of MCC claiming I was connected; yet
there were NO cables hooked up... The M in MCC does not stand for
Linu*s*, RedHat, Suse, etc...
I'm on a tight schedule until the end of Dec; and this did not make me
happy at all... so sorry if this sounds too harsh; but shorewall shoved
between my back pockets was a tad harsh too, IMO.
Anyway, while I can get around these issues by myself, I hope there will
be more thought given to those who can't if Mdk still intends to target
new users...
Cheers,
Pierre
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Re: [expert] 9.0 Networking === ARGHHHHHHHHHHHHHHHHHHH
That's why Odyssey is still powering my boxes -- the little engine (release)
that could.
Now Pierre, don't hold back, go ahead and tell us how you really
feel
Pierre Fortin wrote:
I don't like this resorting to this kind of post, and I'll probably start
a small war; but I need to vent...
rant
So far, 9.0 has been more irritation than help... I have a new IBM
ThinkPad A20m which moves around with me. So... as I move around, I
setup my environment for each new type of location... the unit is called
gypsy for obvious reasons.
Anyway... in NC, gypsy connects to my main LAN -- setup everything and
all worked fine in the default profile.
Next, in SC, gypsy connects to another LAN -- same parameters, except for
the DNS servers, so I setup profiles NC and SC.
Last night, I got around to setting it up for dialup... and there started
the descent into hell...
Summary:
* MCC/NetworkInternet is thoroughly confused with 3 profiles (not incl
default)
location interface status net_access
NC eth0 down connected
SC eth0 down connected
DialUp modem down connected
This SUX cuz the there's no LAN connection and the modem can't even be
dialed up because...
* devfsd keeps clobbering my /dev/modem -- I want/need it to be:
lr-xr-xr-x1 root root12 Nov 20 22:32 /dev/modem - /dev/tts/LT0
NOT:
lr-xr-xr-x1 root root 5 Nov 20 22:04 /dev/modem - ttyS0
which does NOT work with an internal Lucent LinModem...
# ll /etc/devfs/conf.d/
total 16
-rw-r--r--1 root root 983 Aug 30 12:19 dynamic.conf
-rw-r--r--1 root root 105 Nov 20 22:04 modem.conf
-rw-r--r--1 root root 103 Oct 30 20:25 mouse.conf
-rw-r--r--1 root root 105 Nov 20 22:04 ttyS0.conf
Gee... any chance conf in {modem,ttyS0}.conf is really just the
abbreviation for confusion...? Somehow, I doubt {modem,ttyS0}.conf are
intended to be used at the same time...
# for f in /etc/devfs/conf.d/*; do echo - $f; cat $f;done
- /etc/devfs/conf.d/dynamic.conf
# dynamic desktop and co
REGISTER.*/part.* EXECUTE /etc/dynamic/scripts/part.script
add $devpath
UNREGISTER .*/part.* EXECUTE /etc/dynamic/scripts/part.script
del $devpath
REGISTERv4l/video.* EXECUTE /etc/dynamic/scripts/webcam.script
add $devpath
UNREGISTER v4l/video.* EXECUTE /etc/dynamic/scripts/webcam.script
del $devpath
REGISTERusb/scanner.* EXECUTE
/etc/dynamic/scripts/scanner.script add $devpath
UNREGISTER usb/scanner.* EXECUTE
/etc/dynamic/scripts/scanner.script del $devpath
REGISTERusb/rio500 EXECUTE /etc/dynamic/scripts/rio500.script
add $devpath
UNREGISTER usb/rio500 EXECUTE /etc/dynamic/scripts/rio500.script
del $devpath
REGISTERusb/tts/[13579] EXECUTE /etc/dynamic/scripts/visor.script
add $devpath
UNREGISTER usb/tts/[13579] EXECUTE /etc/dynamic/scripts/visor.script
del $devpath
REGISTER(usb/lp.*|printers/.*) EXECUTE
/etc/dynamic/scripts/lp.script add $devpath
UNREGISTER (usb/lp.*|printers/.*) EXECUTE
/etc/dynamic/scripts/lp.script del $devpath
- /etc/devfs/conf.d/modem.conf
REGISTER^tts/0$ CFUNCTION GLOBAL mksymlink tts/0 modem
UNREGISTER ^tts/0$ CFUNCTION GLOBAL unlink modem
- /etc/devfs/conf.d/mouse.conf
REGISTER^psaux$ CFUNCTION GLOBAL symlink psaux mouse
UNREGISTER ^psaux$ CFUNCTION GLOBAL unlink mouse
- /etc/devfs/conf.d/ttyS0.conf
REGISTER^tts/0$ CFUNCTION GLOBAL mksymlink tts/0 ttyS0
UNREGISTER ^tts/0$ CFUNCTION GLOBAL unlink ttyS0
* just enabling modem access resulted in shorewall being silently
enabled... When I tried to switch back to LAN mode, I was unable to
connect to ANYTHING...
Nov 19 23:25:37 gypsy drakgw[27131]: running: chkconfig --add shorewall
Nov 19 23:25:37 gypsy drakgw[27131]: running: service /dev/null
shorewall restart
Nov 19 23:25:41 gypsy logger: Shorewall Started
Nov 19 23:25:41 gypsy drakgw[27131]: Configuring a DHCP server on
192.168.1.0
Nov 19 23:25:41 gypsy drakgw[27131]: launched command:
/usr/sbin/update_dhcp.pl
Nov 19 23:25:41 gypsy drakgw[27131]: Updating CUPS configuration
accordingly
Nov 19 23:25:41 gypsy drakgw[27131]: Starting daemons
Nov 19 23:25:41 gypsy drakgw[27131]: launched command:
/etc/rc.d/init.d/cups status /dev/null
Nov 19 23:25:42 gypsy drakgw[27131]: launched command:
/etc/rc.d/init.d/cups stop
Nov 19 23:25:43 gypsy cups: cupsd shutdown succeeded
Nov 19 23:25:43 gypsy drakgw[27131]: launched command:
/etc/rc.d/init.d/dhcpd status /dev/null
Nov 19 23:25:43 gypsy drakgw[27131]: launched command:
/etc/rc.d/init.d/named status /dev/null 2/dev/null
Nov 19 23:25:43 gypsy drakgw[27131]: launched command:
/etc/rc.d/init.d/named stop
Nov 19 23:25:44 gypsy named[1246]: shutting down
Nov 19
Re: [expert] 9.0 Networking === ARGHHHHHHHHHHHHHHHHHHH
On Thu, 2002-11-21 at 00:04, Pierre Fortin wrote: * just enabling modem access resulted in shorewall being silently enabled... When I tried to switch back to LAN mode, I was unable to connect to ANYTHING... The default Shorewall configuration is setup for an ethernet card (eth0). It blocks access to everything on ppp0 (the dial up connection). This link provides a proper configuration: http://shorewall.net/standalone.htm Hopefully future Mandrake releases will configure Shorewall during install. Wouldn't want dial-up users to give up on Mandrake when there's no Internet connection. -- Robert Wohlfarth [EMAIL PROTECTED] Is not life more important than food, and the body more important than clothes? -- Matthew 6:25b Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
[expert] 9.0 Networking === ARGHHHHHHHHHHHHHHHHHHH
I don't like this resorting to this kind of post, and I'll probably start
a small war; but I need to vent...
rant
So far, 9.0 has been more irritation than help... I have a new IBM
ThinkPad A20m which moves around with me. So... as I move around, I
setup my environment for each new type of location... the unit is called
gypsy for obvious reasons.
Anyway... in NC, gypsy connects to my main LAN -- setup everything and
all worked fine in the default profile.
Next, in SC, gypsy connects to another LAN -- same parameters, except for
the DNS servers, so I setup profiles NC and SC.
Last night, I got around to setting it up for dialup... and there started
the descent into hell...
Summary:
* MCC/NetworkInternet is thoroughly confused with 3 profiles (not incl
default)
location interface status net_access
NC eth0 down connected
SC eth0 down connected
DialUp modem down connected
This SUX cuz the there's no LAN connection and the modem can't even be
dialed up because...
* devfsd keeps clobbering my /dev/modem -- I want/need it to be:
lr-xr-xr-x1 root root12 Nov 20 22:32 /dev/modem - /dev/tts/LT0
NOT:
lr-xr-xr-x1 root root 5 Nov 20 22:04 /dev/modem - ttyS0
which does NOT work with an internal Lucent LinModem...
# ll /etc/devfs/conf.d/
total 16
-rw-r--r--1 root root 983 Aug 30 12:19 dynamic.conf
-rw-r--r--1 root root 105 Nov 20 22:04 modem.conf
-rw-r--r--1 root root 103 Oct 30 20:25 mouse.conf
-rw-r--r--1 root root 105 Nov 20 22:04 ttyS0.conf
Gee... any chance conf in {modem,ttyS0}.conf is really just the
abbreviation for confusion...? Somehow, I doubt {modem,ttyS0}.conf are
intended to be used at the same time...
# for f in /etc/devfs/conf.d/*; do echo - $f; cat $f;done
- /etc/devfs/conf.d/dynamic.conf
# dynamic desktop and co
REGISTER.*/part.* EXECUTE /etc/dynamic/scripts/part.script
add $devpath
UNREGISTER .*/part.* EXECUTE /etc/dynamic/scripts/part.script
del $devpath
REGISTERv4l/video.* EXECUTE /etc/dynamic/scripts/webcam.script
add $devpath
UNREGISTER v4l/video.* EXECUTE /etc/dynamic/scripts/webcam.script
del $devpath
REGISTERusb/scanner.* EXECUTE
/etc/dynamic/scripts/scanner.script add $devpath
UNREGISTER usb/scanner.* EXECUTE
/etc/dynamic/scripts/scanner.script del $devpath
REGISTERusb/rio500 EXECUTE /etc/dynamic/scripts/rio500.script
add $devpath
UNREGISTER usb/rio500 EXECUTE /etc/dynamic/scripts/rio500.script
del $devpath
REGISTERusb/tts/[13579] EXECUTE /etc/dynamic/scripts/visor.script
add $devpath
UNREGISTER usb/tts/[13579] EXECUTE /etc/dynamic/scripts/visor.script
del $devpath
REGISTER(usb/lp.*|printers/.*) EXECUTE
/etc/dynamic/scripts/lp.script add $devpath
UNREGISTER (usb/lp.*|printers/.*) EXECUTE
/etc/dynamic/scripts/lp.script del $devpath
- /etc/devfs/conf.d/modem.conf
REGISTER^tts/0$ CFUNCTION GLOBAL mksymlink tts/0 modem
UNREGISTER ^tts/0$ CFUNCTION GLOBAL unlink modem
- /etc/devfs/conf.d/mouse.conf
REGISTER^psaux$ CFUNCTION GLOBAL symlink psaux mouse
UNREGISTER ^psaux$ CFUNCTION GLOBAL unlink mouse
- /etc/devfs/conf.d/ttyS0.conf
REGISTER^tts/0$ CFUNCTION GLOBAL mksymlink tts/0 ttyS0
UNREGISTER ^tts/0$ CFUNCTION GLOBAL unlink ttyS0
* just enabling modem access resulted in shorewall being silently
enabled... When I tried to switch back to LAN mode, I was unable to
connect to ANYTHING...
Nov 19 23:25:37 gypsy drakgw[27131]: running: chkconfig --add shorewall
Nov 19 23:25:37 gypsy drakgw[27131]: running: service /dev/null
shorewall restart
Nov 19 23:25:41 gypsy logger: Shorewall Started
Nov 19 23:25:41 gypsy drakgw[27131]: Configuring a DHCP server on
192.168.1.0
Nov 19 23:25:41 gypsy drakgw[27131]: launched command:
/usr/sbin/update_dhcp.pl
Nov 19 23:25:41 gypsy drakgw[27131]: Updating CUPS configuration
accordingly
Nov 19 23:25:41 gypsy drakgw[27131]: Starting daemons
Nov 19 23:25:41 gypsy drakgw[27131]: launched command:
/etc/rc.d/init.d/cups status /dev/null
Nov 19 23:25:42 gypsy drakgw[27131]: launched command:
/etc/rc.d/init.d/cups stop
Nov 19 23:25:43 gypsy cups: cupsd shutdown succeeded
Nov 19 23:25:43 gypsy drakgw[27131]: launched command:
/etc/rc.d/init.d/dhcpd status /dev/null
Nov 19 23:25:43 gypsy drakgw[27131]: launched command:
/etc/rc.d/init.d/named status /dev/null 2/dev/null
Nov 19 23:25:43 gypsy drakgw[27131]: launched command:
/etc/rc.d/init.d/named stop
Nov 19 23:25:44 gypsy named[1246]: shutting down
Nov 19 23:25:44 gypsy named[1246]: stopping command channel on
127.0.0.1#953
Nov 19 23:25:44 gypsy named[1246]: no longer listening on 127.0.0.1#53
Nov 19 23:25:44 gypsy named[1236]: exiting
Nov 19 23:25:45 gypsy named: named shutdown succeeded
Nov 19 23:25:45 gypsy drakgw[27131]: launched command:
