The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

    Mastodon

  • Twitter Updates

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,839 other subscribers

Archive for the ‘Network-and-equipment’ Category

Next Entries »

OpenVPN connect to the same LAN (bridged mode) (via: The VPN Menu — Endian UTM Appliance v2.4 documentation)

Posted by jpluimers on 2012/08/03

Another research item:

Need to provide access through OpenVPN to the same LAN as where the OpenVPN server runs on.

This is unusual, and requires a bridged OpenVPN solution.

Jürgen Schmidt wrote a nice article on this in 2008.

Endian community edition seems to support this out of the box:

Server configuration

In this panel you can enable the OpenVPN server and define in which zone it should run.

OpenVPN server enabled

Click this to make sure the OpenVPN server is started.

Bridged

If you want to run the OpenVPN server in one of the existing zones check this box. ..

note:

If the OpenVPN server is not bridged you must set the
firewall rules in the VPN firewall to make sure clients
can access any zone - unless you do not want them to.

VPN subnet

This option is only available if you disable bridged mode, which allows you to run the OpenVPN server in its own subnet that can be specified here.

Bridge to

If bridged mode has been selected here you can choose to which zone the OpenVPN server should be bridged.

Dynamic IP pool start address

The first possible IP address in the network of the selected zone that should be used for the OpenVPN clients.

Dynamic IP pool end address

The last possible IP address in the network of the selected zone that should be used for the OpenVPN clients.

–jeroen

via: The VPN Menu — Endian UTM Appliance v2.4 documentation.

Posted in *nix, Endian, Linux, OpenVPN, Power User | Leave a Comment »

Asus RT N66U: steps to get “Tomato Backup Settings & Log to USB Drive Script – TomatoUSB” working on an Asus RT N66U @AustinStAubin

Posted by jpluimers on 2012/07/27

Below are some steps to get the  Tomato Backup Settings & Log to USB Drive Script – TomatoUSB by Austin Saint Aubin working on an Asus RT N66U router.

I presume you are using a Windows system (hence the FAT/FAT32 formatting of the USB stick) for doing the edits and copying of files to an USB stick. Read the rest of this entry »

Posted in *nix, ASUS RT-N66U, Internet, Network-and-equipment, Power User, TomatoUSB | Leave a Comment »

Addendum to Guide to “Install Tomato firmware on Asus RT-N66U / RT-N16 / RT-N12 B1 / RT-N12 C1 / RT-N10U router 韌體教學 | Moonlight Knight”

Posted by jpluimers on 2012/07/23

I had a bit different experience getting the Tomato Shibby firmware loaded on one of my Asus RT-N66U routers than the description from Guide to Install Tomato firmware on Asus RT-N66U nor this Video of the Asus Routers Rescue Mode Tutorial.

Somehow, the Asus Firmware Restoration Utility kept indicating “The wireless router is not in rescue mode”, no matter what I did.

This might be due to that I run VMware Workstation with some virtual LAN adapters on most of my machines.

Or not: the web-interface on the Asus RT N66U would not get into the firmware restoration mode either.

This worked though:

  1. pull the power plug on the RT N66U
  2. press and hold the reset button
  3. insert the power plug on the RT N66U
  4. wait for the power led to slowly blink
  5. release the reset button
  6. wait a few minutes for the modem to become stable
  7. in the mean time set your PC to these IPv4 settings: – host = 192.168.1.100 – mask = 255.255.255.0
  8. start your web-browser
  9. point your web-browser to http://192.168.1.1 (it will time out, don’t worry)
  10. press the power button to turn off the router
  11. wait a few seconds
  12. press the power button to turn on the router now your router gets into rescue mode
  13. refresh your browser so it goes to http://192.168.1.1 again
  14. upload your Tomato firmware

–jeroen

via: Guide to Install Tomato firmware on Asus RT-N66U / RT-N16 / RT-N12 B1 / RT-N12 C1 / RT-N10U router 韌體教學 | Moonlight Knight.

Posted in *nix, ASUS RT-N66U, Internet, Network-and-equipment, Power User, TomatoUSB | 2 Comments »

[Links] Asus RT-N66U (N900) dual-band router

Posted by jpluimers on 2012/06/08

Just came accross an interesting ethernet router: The Asus RT-N66U (N900) dual-band WiFi router.

It has quite a bit of horsepower, is passively cooled, might handle dual-WAN from the stock firmware, and it it doesn’t: it is supposed to run custom firmwares like Tomato, DD-WRT, OpenWRT, etc.

Interesting…

–jeroen

Dual / Triple WAN How To – InfoDepot Wiki.

Posted in ASUS RT-N66U, Internet, Network-and-equipment, Power User, TomatoUSB | 2 Comments »

#@xs4all only over AnnexB with FRITZ!Box 7340 #fail: line sync issues; offline most of the time, max 4 mbit. @xs4all needs to give me some compelling arguments to regain trust in them. @xs4all_HD

Posted by jpluimers on 2012/03/08

xs4all won’t tell you up front, but they changed a couple of things that will bring your 10 mbit down / 1 mbit up to something that hardly connects, and if it does less than half the speed.

This is also a post on how XS4ALL treats long lasting (15 years!) customer relations. Badly.

05.03.12 16:08:01 DSL-Synchronisierung beginnt (Training).
05.03.12 16:06:05 Internetverbindung wurde getrennt.
05.03.12 16:06:05 Internetverbindung IPv6 wurde getrennt, Präfix nicht mehr gültig.
05.03.12 16:06:05 Internetverbindung wurde getrennt.
05.03.12 16:06:05 DSL antwortet nicht (Keine DSL-Synchronisierung).
05.03.12 15:56:30 Internetverbindung IPv6 wurde erfolgreich hergestellt. Präfix: 2001:980:43d9::/48
05.03.12 15:56:30 Internetverbindung IPv6 wurde erfolgreich hergestellt. IP-Adresse: 2001:980:43d9::be05:43ff:fe70:9b53
05.03.12 15:56:26 Internetverbindung wurde erfolgreich hergestellt. IP-Adresse: 82.161.132.169, DNS-Server: 194.109.6.66 und 194.109.9.99, Gateway: 194.109.5.205
05.03.12 15:56:21 DSL ist verfügbar (DSL-Synchronisierung besteht mit 4804/1029 kbit/s).
05.03.12 08:44:20 DSL-Synchronisierung beginnt (Training).

They advertised XS4ALL ONLY (since it on the copper pair you only run DSL, no phone, so you don’t need a splitter) as faster, cheaper and more stable internet and VOIP connection.

It is not. Read the rest of this entry »

Posted in Fritz!, Fritz!Box, Network-and-equipment, Opinions, Power User | Leave a Comment »

xs4all ONLY issues with ADSL sync and Fritz!Box 7340

Posted by jpluimers on 2011/08/26

Recently, I had big problems with my Fritz!Box 7340 losing ADSL sync on my xs4all ONLY connection.

The odd thing is: the problems started after it worked well for quite a while.

I had multiple dozens of these reconnects per day, sometimes as few as once every fre hours, but often as many as half a dozen per hour:

11.07.11 05:14:08 IPv6 Internet connection established successfully. Prefix: 12ab:34cd:56ef::/48
11.07.11 05:14:08 IPv6 Internet connection established successfully. IP address: 12ab:34cd:56ef::fe01dc23:ba45:9867
11.07.11 05:14:07 Internet connection established successfully. IP address: 172.31.120.210, DNS server: 194.109.6.66 and
194.109.9.99, Gateway: 194.109.5.205
11.07.11 05:14:01 DSL is available (DSL synchronization exists with 10007/1029 kbit/s).
11.07.11 05:13:47 DSL synchronization starting (training).
11.07.11 05:13:32 Internet connection cleared.
11.07.11 05:13:32 IPv6 Internet connection was cleared; prefix no longer valid.
11.07.11 05:13:32 Internet connection cleared.
11.07.11 05:13:31 DSL not responding (no DSL synchronization).

The xs4all helpdesk didn’t respond on my emails, and Google searches didn’t reveal much.

This is what I tried:

  1. I tried getting the FRITZ.Box_Fon_WLAN_7340.en-de-es-it-fr.99.05.04-19769.image firmware, mentioned in this thread, but could not download it any more.
  2. I also tried to set the DSL settings to “maximum stability” without any improvement, resetting to factory settings, etc.
  3. The router is already very close to the ISRA point (where DSL enters the house), and I tried both with/without splitter with no improvement whatsoever.
  4. Read the steps in this sat4all thread, but found nothing unusual in my hardware and software config.

I didn’t expect any improvement as nothing on my side has changed, and before xs4all ONLY, I ran DSL for more than 10 years with different modems and no problems whatsoever.

Finally, I downgraded to Firmware-Version 99.04.88 from Firmware-Version 99.04.90.

When downgrading, keep this in mind:

  • Fritz! does not keep old firmware versions on-line; you must regularly get the Fritz!Box 7340 part of their ftp site and keep an archive yourself
  • It will reset your router to factory state and not remember any settings
  • It cannot restore your settings if you saved them with a higher firmware version, not even when you save them with a password as the web-interface seems to suggest

Luckily, one of the things that xs4all did well, is keep an archive of firmware versions for the Fritz!Box 7340, including a Firmware-Version 99.04.88.

Perform these steps when downgrading: Read the rest of this entry »

Posted in Fritz!, Fritz!Box, Network-and-equipment, Power User | 1 Comment »

Older Fritz!Box Firmwares for 7340 (and 7170/7270/7570)

Posted by jpluimers on 2011/03/17

The Dutch internet provider xs4all keeps an archive of some of the older Fritz!Box firmwares.

Sometimes newer firmwares have some issues, and the Fritz people are often very fast removing the old ones.

Here are some older firmwares for Fritz!Box 7170, 7270, 7340 and 7570: Index of /~helpdesk/firmwares.

Fritz themselves have their Firmwares here: ftp://ftp.avm.de///fritz.box/fritzbox.fon_wlan_7340

–jeroen

Posted in Fritz!, Fritz!Box, Network-and-equipment, Power User | Leave a Comment »

ENDIAN Firewall – Connected client can access EFW but no other hosts: enable promiscuous mode on VMware ESXi

Posted by jpluimers on 2010/10/12

While solving a problem with Windows 7 machines not being able to ping the machines on the GREEN LAN of an Endian when connecting through OpenVPN, but XP machines could, I did a few upgrades, then went on to solve the problem.

  • Upgraded from ESX 3.5 to ESXi 4.1 (I needed this anyway because of Pass Through USB support)
  • Upgraded the community edition appliance from Endian 2.2 to Endian 2.4 (which has more configuration options, and better ways for reporting and logging)

Then I went on solving the issue, which I suspected was a kind of routing problem. Read the rest of this entry »

Posted in Endian, ESXi4, ESXi5, ESXi5.1, Firewall, Infrastructure, OpenVPN, Power User, VMware, VMware ESXi | 8 Comments »

Next Entries »