terminal to serial device on startup?
Hi all, I'm trying to get a terminal console session to my serial devices on startup. I've looked around for different terminal emulators and found one called screen. I added the line 10:23:respawn:/usr/local/bin/screen /dev/ttyS0 to my /etc/inittab, but screen seems to take over tty0 not tty10 like I want it to. Is there any way, with screen or a different program, to make a terminal emulator connect to a serial port on one end and a virtual terminal on the other(tty10) on startup? Thanks in advance, Dan DeMond [EMAIL PROTECTED]
network firewalling situation
Hi all,
I'm setting up a machine here to take over the job of our firewall
temporarily. Both machines have the same network cards in the same
configuration. The current firewall is a debian 2.0 machine running
kernel 2.0.29 on an i486. The temp machine is an i386, debian 2.1, kernel
2.2.10. I'm using the same setup scripts in the same order to make the
computer route packets between two networks, but it just isn't working on
the i386. Can anybody tell me what I'm doing wrong?
Thanks in advance,
Dan DeMond
--Network script for current firewall--
#! /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
#portsentry and big brother stuff
portsentry -tcp
/usr/src/bb/runbb.sh
ifconfig eth0 207.106.55.188 netmask 255.255.255.192 broadcast 207.106.55.191
ifconfig eth0:0 207.106.55.187 netmask 255.255.255.192 broadcast 207.106.55.191
ifconfig eth1 207.106.55.126 netmask 255.255.255.192 broadcast 207.106.55.127
# Kernel IP routing table
#Destination GatewayGenmask Iface
/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
/sbin/route add 207.106.55.187 eth0:0
/sbin/route add -net 207.106.55.128 netmask 255.255.255.192 eth0
/sbin/route add -net 207.106.55.64 netmask 255.255.255.192 eth1
/sbin/route add -net 207.106.55.8 gw 207.106.55.123 netmask 255.255.255.248
eth1
/sbin/route add -net 207.106.55.16 gw 207.106.55.123 netmask 255.255.255.240
eth1
/sbin/route add -net 0.0.0.0 gw 207.106.55.190 netmask 0.0.0.0 eth0
# Firewall Filters
ipfwadm -F -p deny
ipfwadm -F -a accept -S 0.0.0.0/0 -D 0.0.0.0/0
#IPADDR=207.106.55.237
#NETMASK=255.255.255.248
#NETWORK=207.106.55.232
#BROADCAST=207.106.55.239
#GATEWAY=207.106.55.238
#ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
#route add -net ${NETWORK}
#route add default gw ${GATEWAY} metric 1
--End--
--ipx script for current firewall--
#!/bin/sh
#
# ipx Bring up/down IPX networking
#
test -f /usr/sbin/ipx_configure || exit 0
# Source function library.
. /etc/init.d/functions
. /etc/ipx.conf
case $1 in
start)
if [ ${IPX_CONFIGURED} = yes ]; then
if [ ${IPX_INTERNAL_NET} = yes ]; then
ipx_internal_net add ${IPX_NETNUM}
else
ipx_interface add -p ${IPX_DEVICE} \
${IPX_FRAME} ${IPX_NETNUM}
fi
if [ ${IPX_SERVER_ROUTE} = yes ]; then
ipx_route add ${IPX_SERVER_NETNUM} \
${IPX_NETNUM} \
${IPX_SERVER_NODENUM}
fi
fi
ipx_configure \
--auto_primary=${IPX_AUTO_PRIMARY} \
--auto_interface=${IPX_AUTO_INTERFACE}
# touch /var/lock/subsys/ipx
;;
stop)
ipx_configure --auto_primary=off --auto_interface=off
ipx_interface delall
# rm -f /var/lock/subsys/ipx
;;
*)
echo Usage: network {start|stop}
exit 1
esac
exit 0
--End--
--ipxripd script for current firewall--
#! /bin/sh
#
# This file was automatically customized by debmake on Jan 9, 1997.
#
# Written by Miquel van Smoorenburg [EMAIL PROTECTED].
# Modified for Debian GNU/Linux by Ian Murdock [EMAIL PROTECTED].
# Modified for Debian by Christoph Lameter [EMAIL PROTECTED]
PATH=/bin:/usr/bin:/sbin:/usr/sbin
DAEMON=/usr/sbin/ipxd
# The following value is extracted by debstd to figure out how to generate
# the postinst script. Edit the field to change the way the script is
# registered through update-rc.d (see the manpage for update-rc.d!)
FLAGS=defaults 40
test -f $DAEMON || exit 0
case $1 in
start)
echo -n Starting IPX RIP/SAP daemon: ipxd
start-stop-daemon --start --exec $DAEMON
echo .
;;
stop)
echo -n Stopping IPX RIP/SAP daemon: ipxd
start-stop-daemon --stop --exec $DAEMON
echo .
;;
*)
echo Usage: /etc/init.d/$0 {start|stop}
exit 1
;;
esac
exit 0
--End--
--ipxconfigure.rcS script for current firewall--
#!/bin/sh
# This script configures the Ethernet cards to route IPX
# packets when hedge boots up.
/usr/sbin/ipx_interface delall
/usr/sbin/ipx_interface add -p eth1 etherii 011D
/usr/sbin/ipx_interface add eth0 etherii 0DDD
/usr/sbin/ipxd
--End--
network aliasing situation
Hi all, I'm setting up a machine here to take over the job of our firewall temporarily. The firewall has two network cards but the new machine has only one. I recompiled the 2.2.10 kernel with ip-aliasing support, and the network will be one electrically when we make the switch. My questions are; 1. Is it possible to assign multiple ipx networks to the same card on two different interfaces? Both networks run EtherII but I'm not sure if you can run them both on the same card. 2. I know I compiled in ip-aliasing support, and I'm using the same ifconfig and route commands that work on other machines for ip-aliasing, but the aliased addresses aren't working from other machines on the network. Is there any reason other than a bad kernel for this? Thanks in advance, Dan DeMond [EMAIL PROTECTED] [EMAIL PROTECTED] ps-please cc any responses to [EMAIL PROTECTED]
saving dselect lists?
Is there any way I can save a dselect configuration and use it in another install? Thanks in advance, Dan DeMond [EMAIL PROTECTED]
Have we been cracked?
Hello all, I'm think that our system may have been cracked. I think they got in through imapd, because of what was in the logfile(see attachment). My question is, did they really get in through imapd? On www.cert.org there was an advisory for imapd, but that was last year this time. Cert said the affected versions were =10.234, while our version reports 11.241. Are newer versions still vulnerable? Thanks in Advance, Dan DeMond daemon.log.0:Jun 19 07:31:08 XX imapd[16504]: connect from cinequanon.com daemon.log.0:Jun 19 07:31:14 XX imapd[16505]: connect from cinequanon.com daemon.log.0:Jun 19 07:31:14 XX imapd[16506]: connect from cinequanon.com daemon.log.0:Jun 19 07:31:15 XX imapd[16508]: connect from cinequanon.com daemon.log.0:Jun 19 07:31:15 XX imapd[16507]: connect from cinequanon.com daemon.log.0:Jun 19 07:31:15 XX imapd[16509]: connect from cinequanon.com daemon.log.0:Jun 19 07:31:15 XX imapd[16510]: connect from cinequanon.com daemon.log.0:Jun 19 07:31:15 XX imapd[16511]: connect from cinequanon.com daemon.log.0:Jun 19 07:31:15 XX imapd[16513]: connect from cinequanon.com daemon.log.0:Jun 19 07:31:15 XX imapd[16512]: connect from cinequanon.com daemon.log.0:Jun 19 07:31:15 XX imapd[16517]: connect from cinequanon.com daemon.log.0:Jun 19 07:31:15 XX imapd[16516]: connect from cinequanon.com daemon.log.0:Jun 19 07:31:15 XX imapd[16515]: connect from cinequanon.com daemon.log.0:Jun 19 07:31:15 XX imapd[16514]: connect from cinequanon.com daemon.log.0:Jun 19 07:31:15 XX imapd[16518]: connect from cinequanon.com daemon.log.0:Jun 19 07:46:36 XX imapd[16584]: connect from cinequanon.com daemon.log.0:Jun 19 07:46:45 XX imapd[16585]: connect from cinequanon.com daemon.log.0:Jun 19 07:46:45 XX imapd[16586]: connect from cinequanon.com daemon.log.0:Jun 19 07:46:45 XX imapd[16587]: connect from cinequanon.com daemon.log.0:Jun 19 07:46:45 XX imapd[16589]: connect from cinequanon.com daemon.log.0:Jun 19 07:46:45 XX imapd[16588]: connect from cinequanon.com daemon.log.0:Jun 19 07:46:45 XX imapd[16590]: connect from cinequanon.com daemon.log.0:Jun 19 07:46:45 XX imapd[16591]: connect from cinequanon.com daemon.log.0:Jun 19 07:46:45 XX imapd[16593]: connect from cinequanon.com daemon.log.0:Jun 19 07:46:45 XX imapd[16592]: connect from cinequanon.com daemon.log.0:Jun 19 07:46:45 XX imapd[16597]: connect from cinequanon.com daemon.log.0:Jun 19 07:46:45 XX imapd[16596]: connect from cinequanon.com daemon.log.0:Jun 19 07:46:45 XX imapd[16595]: connect from cinequanon.com daemon.log.0:Jun 19 07:46:45 XX imapd[16594]: connect from cinequanon.com daemon.log.0:Jun 19 07:46:45 XX imapd[16598]: connect from cinequanon.com mail.info.0:Jun 19 07:31:13 XX imapd[16504]: command stream end of file, while reading line user=??? host=cinequanon.com [209.151.235.233] mail.info.0:Jun 19 07:31:25 XX imapd[16505]: command stream end of file, while reading line user=??? host=cinequanon.com [209.151.235.233] mail.info.0:Jun 19 07:31:25 XX imapd[16507]: command stream end of file, while reading line user=??? host=cinequanon.com [209.151.235.233] mail.info.0:Jun 19 07:31:25 XX imapd[16509]: command stream end of file, while reading line user=??? host=cinequanon.com [209.151.235.233] mail.info.0:Jun 19 07:31:25 XX imapd[16506]: command stream end of file, while reading line user=??? host=cinequanon.com [209.151.235.233] mail.info.0:Jun 19 07:31:25 XX imapd[16508]: command stream end of file, while reading line user=??? host=cinequanon.com [209.151.235.233] mail.info.0:Jun 19 07:31:25 XX imapd[16510]: command stream end of file, while reading line user=??? host=cinequanon.com [209.151.235.233] mail.info.0:Jun 19 07:31:25 XX imapd[16511]: command stream end of file, while reading line user=??? host=cinequanon.com [209.151.235.233] mail.info.0:Jun 19 07:31:25 XX imapd[16512]: command stream end of file, while reading line user=??? host=cinequanon.com [209.151.235.233] mail.info.0:Jun 19 07:31:25 XX imapd[16514]: command stream end of file, while reading line user=??? host=cinequanon.com [209.151.235.233] mail.info.0:Jun 19 07:31:25 XX imapd[16513]: command stream end of file, while reading line user=??? host=cinequanon.com [209.151.235.233] mail.info.0:Jun 19 07:31:25 XX imapd[16516]: command stream end of file, while reading line user=??? host=cinequanon.com [209.151.235.233] mail.info.0:Jun 19 07:31:25 XX imapd[16515]: command stream end of file, while reading line user=??? host=cinequanon.com [209.151.235.233] mail.info.0:Jun 19 07:31:25 XX imapd[16518]: command stream end of file, while reading line user=??? host=cinequanon.com [209.151.235.233] mail.info.0:Jun 19 07:31:25 XX imapd[16517]: command stream end of file, while reading line user=??? host=cinequanon.com [209.151.235.233] mail.info.0:Jun 19 07
e2fsck LARGE_FILE flag error?
Hello all, I was doing an e2fsck on my disk when I got this kinda scary error. Filesystem contains large files, but lacks LARGE_FILE flag in superblock. Fixy? How large are large files? Will this waste data on my drive if I say yes? Where is the large file flag normally set, or why haven't I ever heard of it before? Any information about the large file flag is appreciated. Thanks Dan DeMond
