Re: routing question
On Tue, 2001-11-27 at 23:39, shock wrote:
> * nate (debian-user@aphroland.org) spake thusly:
> >
> > from the looks of the info you gave machine A and E are on
> > the same hub..the cables seem to work as they can both get to
> > the dsl..so my guess would be theres a incorrect netmask or
> > broadcast address set on either A or E, and the DSL gateway
> > doesn't seem to care. since machine A and E are on the same subnet
> > and on the same hub theres no routing involved ..its just "there".
>
> here's the /etc/network/interfaces for machine e (debian woody):
>
> iface eth0 inet static
> address 192.168.1.99
> netmask 255.255.255.0
> network 192.168.1.0
> broadcast 192.168.1.255
> gateway 192.168.1.254
>
> machine a (RH6.2) fires up eth0 and eth1 via /etc/rc.d/rc.local with the
> following statements:
>
> ifconfig eth1 192.168.2.1 netmask 255.255.255.0 broadcase 192.168.2.255 up
> ifconfig eth0 192.168.1.10 netmask 255.255.255.0 broadcast 192.168.1.255 up
> route add -net 192.168.2.0 netmask 255.255.255.0 eth1
> route add -net 192.168.1.0 netmask 255.255.255.0 eth0
>
> the broadcast / netmask scenario you described (while potentially
> problematic) seems to be okay. unless i'm overlooking the obvious.
>
> > either that or you may have
> > firewall rules on one or the other
> > that could be blocking traffic. my
> > guess would be bad broadcast
> > somewhere tho ive had similar
> > problems.
>
> machine e has no firewall. machine a contains the following:
>
> /sbin/ipchains -A input -j ACCEPT -i eth0 -s 0/0 67 -d 0/0 68 -p udp
> /sbin/ipchains -P forward DENY
> /sbin/ipchains -A forward -s 192.168.2.0/24 -j MASQ
>
> as further background, i can ssh from a machine on the internet to
> machine a. also, i can ssh from machines on the 192.168.2.x to
> machine a. it seems that only machine e (192.168.1.99) can't
> successfully get to (or see) machine a.
What is the default policy for the input and output chains on "a".
ipchains -L -v -n output will show this. The output of netstat -atp on
"a" would also be helpfull along with the route output from both
machines. I assume the "broadcase" above for eth1 is a typo and not the
actual command right? Are you using some sort of dhcp on "a" with pump?
--mike
Reply to: