[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: routing question



* Michael Heldebrant (hmike@portalofevil.com) spake thusly:
> 
> Everything looks ok so far.  Routing information is the only thing left
> that I can think of.

any specific flags i should be passing the route command?  here's a
brief one:

[root@exitwound stephen]# /sbin/route -ee
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface    MSS   Window irtt
192.168.2.0     *               255.255.255.0   U     0      0        0 eth1     0     0      0
192.168.2.0     *               255.255.255.0   U     0      0        0 eth1     0     0      0
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0     0     0      0
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0     0     0      0
127.0.0.0       *               255.0.0.0       U     0      0        0 lo       0     0      0
default         cayman.exitwoun 0.0.0.0         UG    0      0        0 eth0     0     0      0
> 
> > [root@exitwound stephen]# netstat -atp
> > Active Internet connections (servers and established)
> > Proto Recv-Q Send-Q Local Address           Foreign Address State       PID/Program name
> > tcp        0      0 pappy.exitwound.o:pop-3 calypso.exitwound:44919 TIME_WAIT   -
> > tcp        0      0 192.168.1.10:pop-3      calypso.exitwound:44918 TIME_WAIT   -
> > tcp        0      0 *:6010                  *:* LISTEN      607/sshd2
> > tcp        0    232 pappy.exitwound.org:ssh calypso.exitwound:44912 ESTABLISHED 607/sshd2
> > tcp        0      0 *:smtp                  *:* LISTEN      409/sendmail: accep
> > tcp        0      0 192.168.1.10:www        *:* LISTEN      363/httpd
> > tcp        0      0 *:mysql                 *:* LISTEN      359/mysqld
> > tcp        0      0 *:ssh                   *:* LISTEN      291/sshd2
> > tcp        0      0 *:pop-3                 *:* LISTEN      282/inetd
> > tcp        0      0 *:pop-2                 *:* LISTEN      282/inetd
> 
> You are listening on both cards in theory for sshd2.  Can "a" get a ping
> response from "e"?

nope.  "a" can't see "e" and "e" can't see "a".  can't ping, ssh2, nada.

> Why do you have a hole in your firewall for the dhcp information then? 
> If it's all internal to the modem (meaning you never change ip's ever)
> you may want to remove that from the firewall.

at one time i needed dhcp, but i don't use it any more.  you're right.
i need to close it.  thx.
-- 
 ____) ,_)        ,_)
(-(__  |_  _  _ |/
 ____) | |(_)(_ |\
(                 \_,
 _______________________________________________
| http://www.exitwound.org : hard to find       |
 _______________________________________________
| A reverend wanted to telephone another        |
| reverend. He told the operator, "This is a    |
| parson to parson call."                       |
 _______________________________________________
 -------------BEGIN GEEK CODE BLOCK-------------
| Version: 3.1                                  |
| GJ/IT d- s: a C+++>$ UL++++ P+++ L+++ E--- W++| 
| N+@ o K- w O- M- V PS+ PE Y+ PGP++ t+@ 5@ X++ |
| R tv+@ b+ DI++++ D+ G++ e++++ h---- r+++ y+++ |
 --------------END GEEK CODE BLOCK--------------



Reply to: