On Mo, 2016-09-26 at 11:52 -0500, Lonnie Abelbeck wrote: > On Sep 26, 2016, at 11:13 AM, Armin Tüting <armin.tueting@tueting-onl > ine.com> wrote: > > > > > > > > > Also try: > > > -- > > > arp-scan -lI eth0 > > > -- > > > and make sure you don't colliding IP's. > > No double ip addresses! But, where is my AstLinux > > arp-scan -lI eth0 > > Interface: eth0, datalink type: EN10MB (Ethernet) > > Starting arp-scan 1.9 with 256 hosts (http://www.nta-monitor.com/to > > ols/ > > arp-scan/) > > 192.168.60.1 00:00:00:d0:64:ce CONNECT AS > > 192.168.60.5 00:00:00:08:67:09 Manufacturer > > Good, that is normal, only external ARP replies are listed. > > > > > > > > > > Also try: > > > -- > > > ip route > > ip route > > default via 192.168.60.1 dev eth0 metric 2 > > 192.168.10.0/24 via 192.168.40.1 dev eth1 metric 1 > > 192.168.40.0/24 dev eth1 proto kernel scope link src > > 192.168.40.6 > > 192.168.50.0/24 via 192.168.40.1 dev eth1 metric 1 > > 192.168.60.0/24 dev eth0 proto kernel scope link src > > 192.168.60.6 > > > > Armin. > > Your network CIDR's look fine. > > Where are the "metric 1" routes coming from ?: > -- > 192.168.10.0/24 via 192.168.40.1 dev eth1 metric 1 > 192.168.50.0/24 via 192.168.40.1 dev eth1 metric 1 > -- > are you adding those manually ? Yes! I've added them through /mnt/kd/rc.elocal! They're static routes off eth1!
> Where are the 192.168.10.0/24 and 192.168.50.0/24 networks in your > configuration ? I've added them through /mnt/kd/rc.elocal > Also this looks odd with the "metric 2" added, are you doing that?: Yup! > -- > default via 192.168.60.1 dev eth0 metric 2 > -- > > If your SSH client is from either the 192.168.10.0/24 or > 192.168.50.0/24 network external to eth0 then those added routes are > messing things up. That's the case! Sorry, I'm not getting the point :( > Just for comparison, here is a working test box with a static > external interface eth0 (10.10.50.62) and LAN interfaces eth1, > eth1.10 and eth1.50 > -- ip route -- > default via 10.10.50.1 dev eth0 > 10.10.50.0/24 dev eth0 proto kernel scope link src 10.10.50.62 > 192.168.101.0/24 dev eth1 proto kernel scope link src > 192.168.101.1 > 192.168.110.0/24 dev eth1.10 proto kernel scope link src > 192.168.110.1 > 192.168.202.0/24 dev eth1.50 proto kernel scope link src > 192.168.202.1 > -- This configuration reflects one subnet on eth0 and three subnets connected to eth1 - isn't it? I'm only having one subnet on eth0 and eth1 connected. The subnet x.10/24 and x.60/24 are reachable through eth1 with a GW external to eth1. Armin. ------------------------------------------------------------------------------ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
