Hi Grommish,
Thanks again for your efforts in not only trying to keep this box alive but to improve upon it's original coding. While I don't use mine any longer I am curious to get it working. Unfortunately my linux skills are lacking somewhat and after SSH to the box and issuing the first command per your post I'm geeted with the following error: mount: can't read '/etc/fstab': No such file or directory I can see the fstab file using Winscp in the etc dir but can't seem to do anything with it (download, edit, etc I get a similar error 'Received error message from remote side: 'scp: /etc/fstab: No such file or directory'). Not sure what I can do about this. I've already reset the shield to factory, re-did the password and ssh settings but same problem. Not a huge issue as I don't rely on this but I'd like to get the sofware on there if I can. Thanks again
Running v2 Firmware
|
In reply to this post by Grommish
Tried running you instructions but keep getting mount: can't read '/etc/fstab': No such file or directory when i running the first command, so I add overlay at the end and all when well ssh -q -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null [hidden email] "mount /dev/mmcblk0p1 /overlay" cd into /overlay and saw in image files so went ahead and ran the other commands again all when well, but on reboot and the switch in G mode it still loaded the old gateway image, rebooted several time but still the same, any ideas? what I've done wrong. Roadrunneruk On Wed, 15 Apr 2020 at 07:39, Grommish [via Itus Networks Owners Forum] <[hidden email]> wrote: Itus Shield Firmware v2.0 (OpenWrt SNAPSHOT r11407+1525-54ba15f9fa) ALPHA |
Administrator
|
Because I had been up for a bit and forgot a piece on the first step. ssh -q -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null [hidden email] "mount /dev/mmcblk0p1 /overlay" That'll actually tell it what device to mount to 😁 On Wed, Apr 15, 2020, 9:53 AM Roadrunnere42 [via Itus Networks Owners Forum] <[hidden email]> wrote:
Running Itus Shield v2 Firmware
|
Administrator
|
Also, Road, you've played with the later test images, check to see if you have a /.norwits file when you boot to the gateway. If you do, remove it, then reboot /.norwits is a keystone file that triggers the actual install on boot On Wed, Apr 15, 2020, 12:41 PM Grommish [via Itus Networks Owners Forum] <[hidden email]> wrote:
Running Itus Shield v2 Firmware
|
Right go it work, can ssh in, but when access through web browser nothing. On Wed, 15 Apr 2020 at 19:03, Grommish [via Itus Networks Owners Forum] <[hidden email]> wrote:
|
Thanks for the updated commands, went on ok and upon reboot I get the orange status light. Can't get an IP though.
Before updated my setup was to connect directly to the Shield (Eth1 to Laptops Ethernet port), this got me an IP in the 10. range when switch was in pos 'r'. After the update with the switch in pos 'g' I dont get any ip from eth1, am I meant to? Like I said this box is not connected to my network yet, just seeing if I can get it going. Thanks!
Running v2 Firmware
|
I downloaded v2 but found that if eth0 is not connect to a network then eth2 will not give an ip, have not tried eth0 On Thu, 16 Apr 2020, 15:33 Turrican [via Itus Networks Owners Forum], <[hidden email]> wrote: Thanks for the updated commands, went on ok and upon reboot I get the orange status light. Can't get an IP though. |
Administrator
|
This image is setup to act like the ROUTER image, even if it's in the GATEWAY position..
This mean: eth0 = WAN - This should go upstream to your network, be it to an internal router as a stub (which is how I operate) or your cable modem. eth0 is set to ask via DHCP for an IP address. eth1/eth2 = LAN - These are your LAN ports.. These should go to your router, switch, hub, PC, etc. eth1/eth2 are BRIDGED interfaces, which means they do NOT pull an IP address. This is handled by the br-lan interface, and assigns itself a 10.10.10.10 address by default. There is no difference between the eth1/eth2 port, although I use eth2 out of habit. The br-lan interface acts as a DHCP/DNS SERVER for the LAN.. It will handle DHCP and DNS queries via dnsmasq. You will NEVER see an IP address under the eth1/eth2 ifconfig.. If you do, something is very very wrong. See my active ifconfig below. Notice the br-lan /eth0 interfaces vs eth1/2 Try rebooting the Shield if the eth0 doesn't pickup an IP address.. I have no idea why it does it sometimes (always has). Be default, snort is NOT running (it works, but I've yet to get the procd calls in /etc/init.d/snort to actually work. If you want to run it, type: /usr/bin/snort -Q -v --daq afpacket --daq-dir /usr/lib/daq/ -i eth0:br-lan -c /etc/snort/snort.lua -A alert_full -D
Running Itus Shield v2 Firmware
|
Thanks Gromish, I’ll hook it up to my lan and test again tomorrow
All the best
From: Grommish [via Itus Networks Owners Forum] <ml+[hidden email]>
Sent: Thursday, April 16, 2020 5:32:58 PM To: Turrican <[hidden email]> Subject: Re: Itus Firmware v2 This image is setup to act like the ROUTER image, even if it's in the GATEWAY position..
This mean: eth0 = WAN - This should go upstream to your network, be it to an internal router as a stub (which is how I operate) or your cable modem. eth0 is set to ask via DHCP for an IP address. eth1/eth2 = LAN - These are your LAN ports.. These should go to your router, switch, hub, PC, etc. eth1/eth2 are BRIDGED interfaces, which means they do NOT pull an IP address. This is handled by the br-lan interface, and assigns itself a 10.10.10.10 address by default. There is no difference between the eth1/eth2 port, although I use eth2 out of habit. The br-lan interface acts as a DHCP/DNS SERVER for the LAN.. It will handle DHCP and DNS queries via dnsmasq. You will NEVER see an IP address under the eth1/eth2 ifconfig.. If you do, something is very very wrong. See my active ifconfig below. Notice the br-lan /eth0 interfaces vs eth1/2 Try rebooting the Shield if the eth0 doesn't pickup an IP address.. I have no idea why it does it sometimes (always has). Be default, snort is NOT running (it works, but I've yet to get the procd calls in /etc/init.d/snort to actually work. If you want to run it, type: /usr/bin/snort -Q -v --daq afpacket --daq-dir /usr/lib/daq/ -i eth0:br-lan -c /etc/snort/snort.lua -A alert_full -D
Running Itus Shield v2 Firmware
If you reply to this email, your message will be added to the discussion below:
http://itus.accessinnov.com/FIRMWARE-Itus-Networks-Shield-Firmware-Upgrade-WIP-tp1726p1952.html
To start a new topic under Technical Discussion, email ml+[hidden email]
To unsubscribe from [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*, click here. NAML
Running v2 Firmware
|
Administrator
|
Thank you for trying :)
You've got my Hangouts info, feel free to hit me up there if you have issues
Running Itus Shield v2 Firmware
|
Administrator
|
In reply to this post by Roadrunnere42
Road,
Make sure your attempting to access the luCI interface from BEHIND the Shield. It is set to ONLY listen to 10.10.10.10 (the br-lan interface) For testing purposes, if you want to add whatever IP is on eth0, you can ssh into the shield and type uci add_list uhttpd.main.listen_http='x.x.x.x:80' uci add_list uhttpd.main.listen_https='x.x.x.x:443' service uhttpd reload This will add additional IP:port binds for uhttpd. If your eth0 pulls a 192.168.1.116 address (as shown from ssh) uci add_list uhttpd.main.listen_http='192.168.1.16:80' uci add_list uhttpd.main.listen_https='192.168.1.16:443' service uhttpd reload
Running Itus Shield v2 Firmware
|
This post was updated on .
In reply to this post by Grommish
Ok, hooked up my LAN to Eth0 and it is not getting any IP, tried several reboots and waited etc:
root@OpenWrt:/# ifconfig br-lan Link encap:Ethernet HWaddr 2C:26:5F:80:09:41 inet addr:10.10.10.10 Bcast:10.10.10.255 Mask:255.255.255.0 inet6 addr: fe80::2e26:5fff:fe80:941/64 Scope:Link inet6 addr: fd18:640:804c::1/60 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:2068 (2.0 KiB) eth0 Link encap:Ethernet HWaddr 2C:26:5F:80:09:40 inet6 addr: fe80::2e26:5fff:fe80:940/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:144 errors:0 dropped:4 overruns:0 frame:0 TX packets:37 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:22046 (21.5 KiB) TX bytes:8529 (8.3 KiB) I moved the switch to R and rebooted just to test (left the cables are they were) and it got an IP straight away, and I could get to the admin page in my browser: root@Shield:/# ifconfig ---snip--- eth0 Link encap:Ethernet HWaddr 2C:26:5F:80:09:40 inet addr:192.168.1.113 Bcast:192.168.1.255 Mask:255.255.255.0 any suggestions? it looks like it's getting an IPv6 address but not an IPv4?? I've reloaded the image and same results. Thanks
Running v2 Firmware
|
Administrator
|
Try this, from the Shield and booted into the new image. mount /dev/mmcblk1p1 /overlay touch /overlay/ItusgatewayImage unmount /overlay reboot On Fri, Apr 17, 2020, 10:58 AM Turrican [via Itus Networks Owners Forum] <[hidden email]> wrote: Ok, hooked up my LAN to Eth0 and it is not getting any IP, tried several reboots and waited etc:
Running Itus Shield v2 Firmware
|
Thanks! That worked!
From: Grommish [via Itus Networks Owners Forum] <ml+[hidden email]>
Sent: Friday, April 17, 2020 6:23:10 PM To: Turrican <[hidden email]> Subject: Re: Itus Firmware v2 Try this, from the Shield and booted into the new image.
mount /dev/mmcblk1p1 /overlay
touch /overlay/ItusgatewayImage
unmount /overlay
reboot
On Fri, Apr 17, 2020, 10:58 AM Turrican [via Itus Networks Owners Forum] <[hidden email]> wrote:
Ok, hooked up my LAN to Eth0 and it is not getting any IP, tried several reboots and waited etc: Running Itus Shield v2 Firmware
If you reply to this email, your message will be added to the discussion below:
http://itus.accessinnov.com/FIRMWARE-Itus-Networks-Shield-Firmware-Upgrade-WIP-tp1726p1957.html
To start a new topic under Technical Discussion, email ml+[hidden email]
To unsubscribe from [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*, click here. NAML
Running v2 Firmware
|
Administrator
|
Fantastic. If you need a package built, let me know. If you make changes to your settings, let me know what and where, and I can put it in. On Fri, Apr 17, 2020, 1:44 PM Turrican [via Itus Networks Owners Forum] <[hidden email]> wrote:
Running Itus Shield v2 Firmware
|
Thanks Grommish much appreciated. I might get some time to play this weekend, happy to get this far!
Running v2 Firmware
|
Administrator
|
The biggest issue the Shield has is the arch. OpenWrt doesn't do much of anything for it. So, while we do have opkg, OpenWrt doesn't build for mips64, at least, not that I can find.
There is an option for it, but it just returns the same "has no valid architecture, ignoring." returns. So, if you want to ADD a package (you can use opkg list to see the list), let me know and I can compile it out and send you the ipkg file you can use to install. Maybe in the future I can figure out if it's feasible to run a buildbot to update the packages automatically. Then i can just find a place to host (maybe whoever is hosting this place?) and we can create our own arch release for it. Or.. Maybe I'm just doing it wrong on my end :D Just to save you some search time: if you want to run snort3, which I can't get to run automatically for some reason yet, from the shield type: snort -Q -v --daq afpacket --daq-dir /usr/lib/daq -c /etc/snort/snort.lua -i eth0:br-lan -A alert_fast -D Adblock is working, however, it takes a few minutes to fully load in. If you're monitoring your processes (ps -w), when you see /bin/sh /etc/adblock/adblock.monitor 4.0.4 It's up and stable. Then you can visit your favorite ad-laden site and see what happens (I like http://speedtest.net). When you log into luCi (http://10.10.10.10), if you go to Services, AdBlock, then click on the DNS Report tab, then click blue Refresh button and Refresh button on pop-up.
Running Itus Shield v2 Firmware
|
one little bug it think when my laptop is connected to the shield it's dns is set to 10.10.10.10 so no web sites are accessible . The laptop is set to auto for network setting, I have to manual set the Dns to say 1.1.1.1 and all works, what needs changing on the Shield to allow auto configuration for dns? If I ssh into Shield ping works fine and web diagnostics work fine On Fri, 17 Apr 2020 at 20:33, Grommish [via Itus Networks Owners Forum] <[hidden email]> wrote: The biggest issue the Shield has is the arch. OpenWrt doesn't do much of anything for it. So, while we do have opkg, OpenWrt doesn't build for mips64, at least, not that I can find. |
Administrator
|
The DNS should be 10.10.10.10. If it's not working, it means there is something wrong with the DNS settings. The path goes like this : PC->Shield->External. The shield handles its own DNS so it can black hole bad domains. As far as setting the DNS in DHCP, I'd have to look that up, but it is set correctly if your laptop is set to 10.10.10.10 for DNS. On Sat, Apr 18, 2020, 6:47 AM Roadrunnere42 [via Itus Networks Owners Forum] <[hidden email]> wrote:
Running Itus Shield v2 Firmware
|
I found changing the forwarding address in the shield to 9.9.9.9 did the trick for me.
Running v2 Firmware
|
Free forum by Nabble | Edit this page |