发表文章

[C] 检查 nodogsplash 工作的远程 Check nodogsplash working from remote[nodogsplash]

nhimcoi30889 2017-10-9 34

大家好,
我认为一个问题是:

  • 我有一个路由器运行 openwrt + nodogsplash。它的工作完美 (弹出认证, 重定向...)
  • 我可以从远程机器 (vpn) 访问路由器的 ssh
  • 约2或 3, 路由器可以挂起状态 (客户端连接到路由器, 但不显示弹出, 所以客户端不能按图标访问互联网)
  • ssh 到路由器和 ping 互联网通常
    == > 我需要重新启动路由器或麻烦一些问题后, 客户端可以访问互联网
    我想问你: 可以模拟器客户端测试这个案例 (远程模拟器)???
    我不能去路由器检查 (使用我的 smphone 测试) 每次
原文:

Hi everybody,
I think about a problem as :

  • i have a router running openwrt + nodogsplash. Its working perfect ( pop-up authent, redirect ... )
  • i can access router from remote machine ( vpn ) for ssh
  • about 2 or 3 , router can pending status ( client connect to router but dont show pop-up, so client cant press icon access internet )
  • ssh to router and ping internet normally
    ==> i need reboot router or trouble some problem , after client can access internet
    I want to ask you : can simulator a device client for test this case ( remote simulator ) ???
    I cant go to router for check ( use my smphone test ) everytime
相关推荐
最新评论 (15)
nhimcoi30889 2017-10-9
1

@lynxis@mwarning@bluewavenet可以给出一些解决方案吗?

原文:

@lynxis @mwarning @bluewavenet can you give some solution ?

bluewavenet 2017-10-9
2

您可以使用 ndsctl 状态检查它是否正常工作和/等/初始化. d-/nodogsplash 停止

/等/初始化/nodogsplash 启动
重新启动它。还有重新启动路由器的命令。
通常, 如果客户端无法重定向, 则表示它们没有解析 dns。 如果路由器的内存不足也会发生。检查系统日志和内核日志中是否有错误。
您使用的是什么路由器/openwrt/nodogsplash?

原文:

You can use ndsctl status to check if it is working and /etc/init.d/nodogsplash stop
And
/etc/init.d/nodogsplash start
to restart it. Also the reboot command to restart the router.
Usually if clients fail to be redirected it means they are not resolving dns. Can also happen if the router is VERY short of memory. Check the system logs and kernel logs for errors.
What router/openwrt/nodogsplash are you using?

nhimcoi30889 2017-10-9
3

@bluewavenet ,
Im 使用 openwrt CC 15.5.01, nodogsplash 0.9.9.5, 路由器 tplink c20i (ram 64mb, 闪存 8mb)。
我认为 64mb ram 不短

原文:

Tks @bluewavenet ,
Im using openwrt CC 15.5.01 , nodogsplash 0.9.9.5, router tplink c20i ( ram 64mb, flash 8mb ).
I think that 64mb ram is not short

nhimcoi30889 2017-10-9
4

可以提高速度解析 dns 吗?

原文:

Can i increase speed resolve dns ?

nhimcoi30889 2017-10-9
5

您好@bluewavenet ,
我有另一个例子:
我使用 web 服务器来重定向 URL
有时, 我的 web 服务器响应非常缓慢或下降。
此时, 在未找到显示页之前, 客户端的请求将需要很长时间才能解析 dns 或接收响应 web 服务器
我希望它重定向到主 url 约 5s, 如果没有收到来自我的 web 服务器的响应, 它将重定向到另一个 url (第二个 url)
我能行吗?

原文:

Hi @bluewavenet ,
I have another case as :
I use a web server for redirect URL
Sometime, my web server response very slow or down.
This time, client's request will take time very long for resolve dns or receive response web server before show page not found
I want it redirect to primary URL about 5s, if dont receive response from my web server, it'll redirect to another URL ( second url )
I can do it ?

bluewavenet 2017-10-9
6

这不是一个问题与 Nodogsplash, 我不知道有什么可以做到这一点。最好修复您的 web 服务器。为什么不在路由器上运行您的 web 服务器?uhttpd 是在那里和运行已经在 Openwrt 和它支持 PHP。
同样, 慢速 DNS 与 Nodogsplash 无关, 而且很可能是由于您使用的互联网提要有问题。

原文:

This is not a problem with Nodogsplash and I do not know of anything to do this. It would be better to fix your web server. Why not run your web server on your router? uhttpd is there and running already on Openwrt and it supports PHP.
Likewise, slow DNS is nothing to do with Nodogsplash and is most likely due to an issue with the Internet feed you are using.

nhimcoi30889 2017-10-9
7

我认为不能使用 openwrt 作为 web 服务器, 因为闪存存储缓慢 (8mb)
我阅读了您的主题: #113
时间响应初始页平均约7s
你觉得它慢还是正常?
系统的时间响应?

原文:

I think that can't use openwrt as web server because the flash store slow (8mb)
I read your topic : #113
Time response splash page average about 7s
You think its slow or normal ?
Time response on your system ?

misterlexa 2017-10-9
8

你可以使用简单的 cron。
创建这样的 sh 脚本:

"如果 pgrep" nodogsplash ">/开发/空

然后

command wget "http://www.mysite.com/nodogsplash?works=1

其他

command wget "http://www.mysite.com/nodogsplash?works=0

command /etc/init.d/nodogsplash start

上网'

然后:
crontab-e

* * * * * /path/to/your/script.sh;

原文:

You can use simple cron.
Create sh script like this:

`if pgrep "nodogsplash" > /dev/null

then

command wget "http://www.mysite.com/nodogsplash?works=1

else

command wget "http://www.mysite.com/nodogsplash?works=0

command /etc/init.d/nodogsplash start

fi`

then:
crontab -e
and
* * * * * /path/to/your/script.sh;

bluewavenet 2017-10-9
9

@nhimcoi30889
在 Ubiquiti 子弹 M2, Nanostation M2, AirGateway LR 和 PCEngines Alix 2d2: 响应时间 < 2 秒所有这些。Alix 2d2 支持超过 350 Nodogsplash 连接每天和峰值的〜60同时用户和仍然 < 2 秒的飞溅页。

原文:

@nhimcoi30889
On Ubiquiti Bullet M2, Nanostation M2, AirGateway LR, and PCEngines Alix 2d2 : Response time <2 seconds on all of these. Alix 2d2 supporting over 350 Nodogsplash connections per day and peak of ~60 simultaneous users and still <2 sec to splash page.

nhimcoi30889 2017-10-9
10

您好@bluewavenet ,
你能告诉我哪个元素决定了登陆页面的响应时间吗?

原文:

Hi @bluewavenet ,
Can you tell me which does element that decide response time for landing page ?

bluewavenet 2017-10-9
11

控制初始页面响应时间的最大元素是您的网络提要的响应时间。客户端设备必须先解析 dns, 然后再在端口80上进行请求, 然后再重定向。99.9% 的设备在热点将是移动的 "智能手机" 或 "平板", 而不是 "笔记本电脑", 这些设备都有类似的方法来检测一个热点, 这取决于 dns。 这称为 "门户检测", 根据操作系统的不同而有所不同, 但检测时间短, 此时将断开其 wifi 连接, 然后在后台重试。如果您的互联网饲料是非常缓慢的门户检测可以进入一个无限循环。这与 Nodogsplash 以及与路由器的连接有关的一切都无关。

原文:

The biggest element controlling response time to splash page is the response time of your Internet feed. The client device has to resolve dns then make a request on port 80 before being redirected. 99.9% of devices on a hotspot will be mobile "smartphone" or "tablet" rather than "laptop" and these devices all have a similar means of detecting a hotspot which depends upon dns. This is called portal detection and varies depending on operating system but has a short timeout for detection at which point will disconnect its wifi and then retry in the background. If your Internet feed is very slow the portal detection can get into an infinite loop. This is nothing to do with Nodogsplash and everything to do with your router's connection.

nhimcoi30889 2017-10-9
12

我觉得有问题登陆页 (飞溅页) 在 AP 本地, 所以互联网饲料不决定?

原文:

I think have a problem. landing page ( splash page ) on AP locally, so internet feed dont decide ?

bluewavenet 2017-10-9
13

在端口80上所请求的 web 页的 dns 解析的响应时间是为在路由器上举行的初始化页面所占用的时间的主要因素。因此, 是的, 互联网饲料做 "决定"。

原文:

The response time from the Internet for the dns resolution of the requested web page on port 80 is the dominant factor in the time taken for the splash page held on the router to be served up. So yes, the Internet feed does "decide".

nhimcoi30889 2017-10-9
14

我可以将 AP 用于 DNS 服务器吗?当客户端请求 dns 解析时, 它将首先在本地广播到 AP (或者我可以在 hosts 文件上定义 dns?

原文:

I can use AP for DNS server ? When client request dns resolution, it'll broadcast to AP locally first ( or i can define dns on hosts file ? )

bluewavenet 2017-10-9
15

Nodogsplash 必须在路由器上运行, 默认情况下, OpenWrt 将向客户端提供 dhcp 和 dns。设置任何其他方式只是使它不必要的复杂。
这是为了提供互联网接入的条款和条件的接受 (通常由您定制的飞溅页面提供)。这听起来像你需要修复你的互联网饲料第一。

原文:

Nodogsplash has to run on a router and by default OpenWrt will provide dhcp and dns to clients. Setting up any other way just makes it unnecessarily complicated.
This is all designed to provide Internet access on acceptance of terms and conditions (usually provided by your customised splash page). It sounds like you need to fix your Internet feed first.

返回
发表文章
nhimcoi30889
文章数
4
评论数
31
注册排名
60911