I"m having trouble with getting a TP-Link Meteobridge connected through our business network and the following came back from the IT folks:
I found the device at 10.253.4.216. I can see bi-directional traffic between that endpoint and a destination on the internet at 162.55.245.30 on port 80. The firewall is not forbidding any of that traffic. I suspect an issue with the remote application? Packet captures of the traffic look odd. I see the TCP session come up, but then the device on your network sends a RST packet, to which the remote side immediately responds with a FIN, closing the connection before any data has actually been exchanged. Is it possible this device, or the public from which it is connecting, needs to be registered on the remote side? I'm not seeing anything that suggests the traffic is not allowed.
TIA and Help !!
is this a firewall issue ?
Moderator: Mattk
Re: is this a firewall issue ?
Are you talking about a problem with the remote login option of Meteobridge or to get the Meteobridge operational in your Corporate LAN at all?
Re: is this a firewall issue ?
Hi
For starters this is for the remote login to the device -- the TP-Link rapid flashing LED suggests it does not yet have an ip address but it can be seen on the network.
Because remote login doesn't work I'm not able to upload HTTP or FTP data.
It worked OK prior to some upgrades to our corporate LAN.
The unit works well outside of the corporate LAN.
Thanks !
HL
For starters this is for the remote login to the device -- the TP-Link rapid flashing LED suggests it does not yet have an ip address but it can be seen on the network.
Because remote login doesn't work I'm not able to upload HTTP or FTP data.
It worked OK prior to some upgrades to our corporate LAN.
The unit works well outside of the corporate LAN.
Thanks !
HL
Re: is this a firewall issue ?
We now have an ip assigned and can access from within the network but the following is the detail with respect to logging in from outside the network:
TIA
IFCONFIG:
br-lan Link encap:Ethernet HWaddr E8:DE:27:3E:A0:60
inet addr:10.253.4.216 Bcast:10.253.4.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:73933 errors:0 dropped:1784 overruns:0 frame:0
TX packets:19946 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:61614455 (58.7 MiB) TX bytes:1557081 (1.4 MiB)
eth0 Link encap:Ethernet HWaddr E8:DE:27:3E:A0:60
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:74280 errors:0 dropped:99 overruns:0 frame:0
TX packets:19946 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:62701283 (59.7 MiB) TX bytes:1557081 (1.4 MiB)
Interrupt:4
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
RESOLV.CONF:
# Interface lan
nameserver 209.23.125.14
nameserver 10.253.2.14
search gazette.local
TIA
IFCONFIG:
br-lan Link encap:Ethernet HWaddr E8:DE:27:3E:A0:60
inet addr:10.253.4.216 Bcast:10.253.4.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:73933 errors:0 dropped:1784 overruns:0 frame:0
TX packets:19946 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:61614455 (58.7 MiB) TX bytes:1557081 (1.4 MiB)
eth0 Link encap:Ethernet HWaddr E8:DE:27:3E:A0:60
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:74280 errors:0 dropped:99 overruns:0 frame:0
TX packets:19946 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:62701283 (59.7 MiB) TX bytes:1557081 (1.4 MiB)
Interrupt:4
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
RESOLV.CONF:
# Interface lan
nameserver 209.23.125.14
nameserver 10.253.2.14
search gazette.local
Re: is this a firewall issue ?
Is the Meteobridge still stuck in fast blinking mode? If so it cannot download the application stack from the Meteobridge server.