INTL 3:770/1 3:770/3
REPLYADDR cl@isbd.net
REPLYTO 3:770/3.0 UUCP
MSGID: c6903847
REPLY: d5bc19ee
PID: SoupGate-Win32 v1.05
bp@www.zefox.net wrote:
> Chris Green wrote:
> >>
[snip]
>
> > The first thing I would be doing is to look at the routers's Web GUI
> > to check what it thinks is going on and what is connected to where.
> >
> >
> The DHCP range is limited to 192.168.1.nnn, with no distinction between
> wired and wireless connections. There's clearly bridging from wirless to
> wired devices such as the printer, which works and can be pinged.
>
> Maybe there's a firewall between wireless clients. I've certainly not needed
> such connections much. I'll poke around on the Web to see if there are any
> references to Guest Mode online. The internal help pages are close to
useless,
> and the configuration menus are worse.
>
Router software does sometimes have bugs. I have a TP-link router
that has a symptom a bit like yours, I can't remember the exact
details (it's relegated to being an access point now) but I do
remember that it was something about the firewall treating WiFi
connections differently from wired ones.
Can you temporarily connect the Pi2 using a wired connection and see
if it then works as expected?
--
Chris Green
·
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 10/0 1 90/1 103/705 105/81 106/201 124/5016 129/305 153/757
SEEN-BY: 153/7715 218/0 1 601 700 840 870 930 220/70 221/1 6 360 226/17
SEEN-BY: 226/30 100 227/114 229/110 111 114 200 206 300 317 400 426
SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038
SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364
SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100
SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35
PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426
|
