I'm still having problems getting this to work. The
"ARP: on own address" has quieted a bit. But, packets still sometimes
to not travel correctly. Perhaps you can identify some oversight in my
configurations below?
I'm currently using 2.0.34 with v0.99E 3c59x.c driver patch. I'm also
using "ipportfw"ing... This is the situation:
192.9.100.117 (lidp12)
|
|
+------+-----------------------------------------------------------------+
|192.9.100.114 (lidp10, eth0) |
| |
| (firewall system) |
| |
| 192.168.9.1 (tethys, eth1) |
+------------------------------------------------------+-----------------+
|
|
192.168.9.2 (phobos)
The goal, is to have a "telnet" command executed from 192.9.100.117:
telnet 192.9.100.114 11207
to be forwarded to 192.168.9.2 on port 23
I've gotten this to work, but with only semi success.
The configurations that I'm using to make it happen are on the firewall system:
---------cut-------------cut-------------cut-------------cut-----------
ifconfig eth0 192.9.100.114 netmask 255.255.255.0 broadcast 192.9.100.255 up
ifconfig eth1 192.168.1.1 broadcast 192.168.1.255 netmask 255.255.255.0 broadcast 192.168.1.255 up
route add -net 192.9.100.0 netmask 255.255.255.0 eth0
route add -host 192.168.1.1 eth1
route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.1.1 eth1
route add default eth0
echo "1" > /proc/sys/net/ipv4/ip_forward
# The default rules are accept since the "eth0" interface is also used
# by our intraweb for other purposes.
ipfwadm -F -f ; ipfwadm -F -p accept
ipfwadm -I -f ; ipfwadm -I -p accept
ipfwadm -O -f ; ipfwadm -O -p accept
ipfwadm -I -a accept -P tcp -S 192.168.1.0/24 -D 192.9.100.117/32 23 -W eth1
ipfwadm -O -a accept -P tcp -S 192.9.100.117/32 23 -D 192.168.1.0/24 -W eth1
ipfwadm -F -a accept -P tcp -D 192.9.100.117/32 -S 192.168.1.0/24 -W eth1
ipfwadm -I -a accept -P tcp -D 192.9.100.114/32 -S 192.9.100.117/32 23 -W eth0
ipfwadm -O -a accept -P tcp -D 192.9.100.117/32 23 -S 192.9.100.114/32 -W eth0
ipfwadm -F -m -a accept -P tcp -S 192.168.1.0/24 -D 192.9.100.117/32 -W eth0
# Notice, I'm masquerading on both devices, eth0 and eth1
ipfwadm -O -a accept
ipfwadm -I -a accept
ipfwadm -F -m -a accept
ipportfw -C
ipportfw -A -t 192.9.100.114/11207 -R 192.168.1.2/23
---------cut-------------cut-------------cut-------------cut-----------
The routes on 192.9.100.117 (an AIX system):
Route Tree for Protocol Family 2:
127 127.0.0.1 U 4 7889321 lo0 - -
192.9.100 192.9.100.117 U 2160 836762175 en1 - -
192.168.1.2 192.9.100.114 UGH 0 2174 en1 - -
The routes on 192.168.1.2 (a UnixWare system):
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.2 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
192.9.100.0 192.168.1.1 255.255.255.0 UG 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 61 lo
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 eth0
---------cut-------------cut-------------cut-------------cut-----------
Can you see if there is an oversight in my configs? Thanks in adance.
In previous e-mail, Stephen Davies said:
>
> >
> > Why do I get these messages in dmesg?:
> > ARP: arp called for own IP address
> >
> > my system has two 3Com 3c905B Cyclone 100baseTx cards....
> >
> > eth0: 3Com 3c905B Cyclone 100baseTx at 0x6000, 00:10:4b:c5:4b:35, IRQ 9
> > 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/NWay Autonegotiation interface.
> > Enabling bus-master transmits and whole-frame receives.
> > eth1: 3Com 3c905B Cyclone 100baseTx at 0x6100, 00:10:4b:c5:4b:d5, IRQ 10
> > 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/NWay Autonegotiation interface.
> > Enabling bus-master transmits and whole-frame receives.
> > 3c59x.c:v0.99E 5/12/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
> >
>
> What are the IP addresses involved an what do your DNS entries look like?
>
> This message can be caused by having two different IPs resolving to the one
> name.
>
> Cheers,
> Stephen.
>
>
> ========================================================================
> Stephen Davies Consulting scldad@sdc.com.au
> Adelaide, South Australia. Voice: 61-8-82728863
> Computing & Network solutions. Fax: 61-8-82741015
>
>
>
>
-- Frank Koenen
- To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu