On Tue, 15 Jan 2013 13:26:21 -0800 Tom Eastep <[email protected]> wrote:
> On 01/15/2013 01:19 PM, JB wrote: > > On Tue, 15 Jan 2013 11:53:45 -0800 > > Tom Eastep <[email protected]> wrote: > > > > >> > >> What is the make and model of the router? > >> > > > > It's a TP-Link TL-WR841N Wireless N Router. > > > > If all three systems have wireless connections to that router, then they > should be able to communicate. > > Again with Shorewall cleared on both systems, in one system type 'ip > addr ls'. > > That will show you the IP address of your system. It will look something > like: > > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast > state UP qlen 1000 > link/ether 08:00:27:7c:20:d2 brd ff:ff:ff:ff:ff:ff > inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0 > inet6 fe80::a00:27ff:fe7c:20d2/64 scope link > valid_lft forever preferred_lft forever > > In that example, the IP address is 10.0.2.15. > > Now at a shell prompt on the other system, type 'ping <address of first > system>' (e.g., ping 10.0.2.15). > > -Tom It displayed 'network unreachable'. John -- Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. -Benjamin Franklin ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
