Starting FIPS 186-2 random number generator Initializing Distributed Enforcement Architectureįirmware Version: SonicOS Enhanced 5.9.0.3-117oĭirectory: /depot-14739-51/Octeon/5.9.0/m2/target/oct_mips64/sw_octeon210-sc-base Initializing Deep Packet Inspection framework Initializing Terminal Services support for SSO Starting Endpoint Anomoly detection and Reporting (EAR) Starting IP fragmentation/reassembly handlers Log initializations dependent on preferences Generating gratuitous ARP for Transparent Mode IPs Initial GUI Interface Statistics Counters Starting Stateful Packet Inspection engine Setting Time Zone and updating Daylight savings time Initializing preference export memory buffer devices Pre-initializing Terminal Services support for SSO
Initializing backend dynamic update support Initializing interface packet queue scheme Initializing Memory for Application Firewall Config Objects Starting common gateway interface handler 562 InitializedĪdjusting SonicSetup Watchdog if necessary for large prefsĬreating interface names and default itids Re-using existing memory for ELF: Base addr, 0×2000000, size: 0xe000000 # Loading ELF image with entry point: 0×82008000 …īootloader: Done loading app on coremask: 0×1
0 code on a ConnectME, if I set the module to use DHCP. U-boot 5.0.2.11 (Production build) (Build time: 13:26:22)OCTEON SNWL_CHESTNUT-1 CN5010-SCP pass 1.1, Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)įlash: 32 MB ( Bank 0: 16 MB Bank 1: 16 MB )Īllocating memory for ELF: Base addr, 0×2000000, size: 0xe000000 To make multiple devices behind the SonicWALL security appliance accessible from the public side. I'm getting afraid that the only way to load some custom stuff in it is using the 32-pin header on the PCB which can be observed in the picture made by dashpuppy:
Luckily there's support for the Octeon MIPS64 platform for some linux and BSD flavors but I've no clue how to get it on it (apart from the fact that I also have to figure out first what modules to include during the kernel compilation). I hoped to find something that gives some indication how it boots but nope. Furthermore I've tried to dissect the firmware using Binwalk (which I usually find very helpful) but more than a rather flat entropy graph (1) I haven't been able to deduce from it. I've connected with the CLI but that's extremely limited and I haven't been able to squeze info about the FS and/or OS out of it.
However, as SonicWall units have some nice hardware features and are pretty good performers I'd like to give them a second life. These units are party disabled by Dell: most of the security functions are impaired and the licenses have all been tranfered to the newer models.
SonicWalls that have been discarded because of a Dell upgrade path to 6th. I have read all the other threads related to Sonicwall issues but my situation seems different since there are no call drop issues or one way audio.Lately my personal toybox has expanded with a bunch of 5th Gen. I am confused as to what is causing this and would love any advice if anyone has seen this where everything is functional but are just limited on the number of endpoints registered I assume because of some port issue. I ran a packet monitor on the Sonicwall and when I see the phone trying to register to the server IP I am seeing a drop error of “Drop Code: 247(NAT policy generate unique remap port failed)”
On the Sonicwall I made sure the NAT Policy is set with “Disable Source Port Remap”. I am noticing the ports showing up for the endpoints that are registered in FreePBX is 5060 then 50 when the Yealinks are all actually just set with 5060. Whenever I try and register others it fails. The issue is I cannot register anymore than 3 phones. I was able to get 3 phones registered and incoming and outgoing calls work with audio both ways. I have a hosted FreePBX with Cyberlynk and am trying to roll out all our Yealink 42g phones in one of our locations behind a Sonicwall soho Firewall.