Made some progress, in fact probably a school boy error, the 172.16.0.6 vista machine uses wireless. I placed a wired maching on 172.16.0.0/24 and one on 192.168.0.0/24 subnets and they can communicate via ping. Phew.
But it seems 192168.0.0/24 subnet gets no dns resolved, it has dns settings for my ISP which work on the 172 range. Also a traceroute only resolves fully one way. Dont know if the pf needs to nat to get the DNS working. Any ideas and thanks. duxbuz wrote: > > Sorry, ip 172.16.0.6 is the address of the vista machine on otherside of > router. > > I will post the results of the pupil-laptop pinging the server: > > pu...@pupil-laptop:~$ sudo tcpdump -i eth0 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes > 21:59:18.983781 IP pupil-laptop.local.ssh > 172.16.0.6.53471: P > 1475800150:1475800266(116) ack 4280506126 win 566 > 22:00:03.989533 IP 172.16.0.6.53471 > pupil-laptop.local.ssh: . ack 116 > win 63 > 22:00:03.989668 IP pupil-laptop.local.ssh > 172.16.0.6.53471: P > 116:232(116) ack 1 win 566 > 21:59:18.985065 IP pupil-laptop.local.48762 > 212.23.3.100.domain: 26768+ > PTR? 6.0.16.172.in-addr.arpa. (41) > 21:59:19.188086 IP 172.16.0.6.53471 > pupil-laptop.local.ssh: . ack 232 > win 62 > 21:59:21.377730 IP 172.16.0.6.53460 > pupil-laptop.local.ssh: P > 3443212094:3443212146(52) ack 179455010 win 62 > 21:59:21.378147 IP pupil-laptop.local.ssh > 172.16.0.6.53460: P 1:53(52) > ack 52 win 566 > 21:59:21.710276 IP 172.16.0.6.53460 > pupil-laptop.local.ssh: P 52:104(52) > ack 53 win 68 > 21:59:21.710635 IP pupil-laptop.local.ssh > 172.16.0.6.53460: P 53:105(52) > ack 104 win 566 > 21:59:22.041935 IP 172.16.0.6.53460 > pupil-laptop.local.ssh: . ack 105 > win 68 > 21:59:22.043072 IP 172.16.0.6.53460 > pupil-laptop.local.ssh: P > 104:156(52) ack 105 win 68 > 21:59:22.043358 IP pupil-laptop.local.ssh > 172.16.0.6.53460: P > 105:157(52) ack 156 win 566 > 21:59:22.261685 IP 172.16.0.6.53460 > pupil-laptop.local.ssh: . ack 157 > win 68 > > > Thats with this command running on another ssh session: > > pu...@pupil-laptop:~$ ping 172.16.0.254 > PING 172.16.0.254 (172.16.0.254) 56(84) bytes of data. > 64 bytes from 172.16.0.254: icmp_seq=1 ttl=255 time=0.194 ms > 64 bytes from 172.16.0.254: icmp_seq=2 ttl=255 time=0.183 ms > > Seems to be no icmp in there, dont know if thats significant. > > I am still not knowing why I cant ping both ways or why dns wont resolve > on the 192.168.0.0/24 subnet. > > > > > > Christiano Farina Haesbaert wrote: >> >> On 22/01/2009, at 07:11, duxbuz wrote: >> >>> Still no joy with this issue. >>> >>> I was asked to try: >>> >>>> Try this, >>> . >>>> Go the the ubuntu machine (network 192...) and listen to icmp >>>> packets in >>> the interface connected to the >172... network. >>>> >>>> Then get a machine from network 172... and try to ping it. >>>> >>>> You did a tcpdump on the pf pseudo-interface before but you're >>>> problem >>> doesn't seem to be routing and >or pf filter rules. >>> >>>> If you see ICMP requests coming from another ip, you have a nat in >>>> between >>> and that would justify >your "one way ping". >>> >>> I got these results from this: >>> >>> tcpdump: verbose output suppressed, use -v or -vv for full protocol >>> decode >>> >>> listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes >>> >>> 08:30:28.359774 IP pupil-laptop.local.ssh > 172.16.0.6.49797: P >>> 1505958084:15059 >>> 58280(196) ack 379641432 win 566 >>> >> Whats the ip of pupil-laptop.local ? >>> >>> 08:30:28.361092 IP pupil-laptop.local.50398 > 212.23.3.100.domain: >>> 33472+ >>> PTR? 6 >>> .0.16.172.in-addr.arpa. (41) >>> >>> 08:30:28.361960 IP 172.16.0.6.49797 > pupil-laptop.local.ssh: . ack >>> 196 win >>> 66 >>> >>> 08:30:28.375114 IP pupil-laptop.local > 172.168.0.6: ICMP echo >>> request, id >>> 4893 >>> , >>> seq 5, >>> length 64 >> >> Is 172.168.0.6 the correct ip for the server ? >> Is that what you typed in pupil-laptop ? >> You can say that the pupil-laptop packets are arriving at the >> destination, but they get there with ip 172.168.0.6, which seems not >> to be the server, so it passes the packet forward to the default route. >> >>> 08:30:29.375137 IP pupil-laptop.local > 172.168.0.6: ICMP echo >>> request, id >>> 4893 >>> , >>> seq 6, >>> length 64 >>> >>> 08:30:30.375146 IP pupil-laptop.local > 172.168.0.6: ICMP echo >>> request, id >>> 4893 >>> , >>> seq 7, >>> length 64 >>> >>> 08:30:31.375134 IP pupil-laptop.local > 172.168.0.6: ICMP echo >>> request, id >>> 4893 >>> , >>> seq 8, >>> length 64 >>> >>> 08:30:32.375144 IP pupil-laptop.local > 172.168.0.6: ICMP echo >>> request, id >>> 4893 >>> , >>> seq 9, >>> length 64 >>> >>> 08:30:33.359178 IP pupil-laptop.local.50845 > 212.23.6.100.domain: >>> 33472+ >>> PTR? 6 >>> .0.16.172.in-addr.arpa. (41) >>> >>> 08:30:33.375117 IP pupil-laptop.local > 172.168.0.6: ICMP echo >>> request, id >>> 4893 >>> , seq >>> 10, length 64 >>> >>> 08:30:34.375156 IP pupil-laptop.local > 172.168.0.6: ICMP echo >>> request, id >>> 4893, >>> >>> >>> >>> Does this look irregular? >>> >>> >>> >>> >>> >>> Martin Toft-2 wrote: >>>> >>>> What happens when you ping from the OpenBSD router? Does any of the >>>> other equipment reply? >>>> >>>> The Ubuntu machine's firewall settings can be seen by running 'sudo >>>> iptables -L -v -n'. Are you sure it doesn't block incoming ICMP >>>> requests? >>>> >>>> Martin >>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Router-ping-one-way-only-tp21569634p21600393.html >>> Sent from the openbsd user - misc mailing list archive at Nabble.com. >>> >> >> Christiano Farina Haesbaert >> [email protected] >> >> >> > > -- View this message in context: http://www.nabble.com/Router-ping-one-way-only-tp21569634p21633945.html Sent from the openbsd user - misc mailing list archive at Nabble.com.
