Results 1 to 9 of 9
  1. #1
    Newbie
    Join Date
    Apr 2017
    Posts
    6

    Default Network printer from LAN2 to LAN1

    Hello Guys,

    Need some help on this because I have been hitting my head against a wall all day. Here is my configuration.
    U25 Untangle device.

    Lan1 is setup as Bridge mode to fios router with 192.168.1.1/24
    Lan2 is setup as "Internal" with 192.168.1.1/24 bridged to Lan1 (Netgear Switch for local devices such as NAS/Printer/Smartthings device, etc).
    Lan3 is setup as "Wireless Device" with 192.168.1.1/24 bridged to Lan1 (Wireless router for Wireless devices such as Mac/Laptop/Nest, etc).

    How do i get Lan 3 to talk to Lan 2 so I can print from my wired Printer.

    I see to have created two bypass rules but that only got me to ping the printer device. Am i missing something? Please help.

    Thank you

  2. #2
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    15,905

    Default

    Everything is bridged together? If so you don't have separate LANs and everything should be able to talk to each other.

    If you can ping it you should be good.
    Sorry don't know much about printing protocols
    Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  3. #3
    Newbie
    Join Date
    Apr 2017
    Posts
    6

    Default

    Correct. Everything is bridged together, but i still cannot ping LAN3 devices to LAN2 device. I just tested with pinging NAS on Lan2 and received Destination Port Unreachable. Same with my DVR that is sitting in LAN2.
    Any idea?

  4. #4
    Master Untangler
    Join Date
    Dec 2014
    Posts
    117

    Default

    Can you post some screenshots of the Interfaces in question / how they are setup in the Untangle? I have a couple theories but would need to see the interface setup's to provide a guided answer here. Thank you!

  5. #5
    Newbie
    Join Date
    Apr 2017
    Posts
    6

    Default

    untang1.PNGuntang2.PNG
    Please see attached.

  6. #6
    Master Untangler f1assistance's Avatar
    Join Date
    Apr 2009
    Location
    Holly Springs, NC
    Posts
    360

    Default

    Okay, I'm confused, what exactly is the reasoning for bridging the internal Nic's together? Seems to add unnecessary complications to a simple subnet configuration which could be had by a single internal Nic...
    Last edited by f1assistance; 04-21-2017 at 03:08 AM.
    Untangle...because nothing's worse than doing nothing!
    -------
    2, Pentium (R) Dual-Core CPU E5300 @ 2.60GHz 2599.968, 2089.96MB RAM

  7. #7
    Newbie
    Join Date
    Apr 2017
    Posts
    6

    Default

    This has been resolved. I just unchecked the NAT Traffic exiting this interface(and bridged peers) and everything is working again.

  8. #8
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    21,267

    Default

    Quote Originally Posted by f1assistance View Post
    Okay, I'm confused, what exactly is the reasoning for bridging the internal Nic's together? Seems to add unnecessary complications to a simple subnet configuration which could be had by a single internal Nic...
    It makes Untangle an expensive switch.
    f1assistance likes this.
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  9. #9
    Master Untangler f1assistance's Avatar
    Join Date
    Apr 2009
    Location
    Holly Springs, NC
    Posts
    360

    Default

    Ah, gotcha! ;-)
    Untangle...because nothing's worse than doing nothing!
    -------
    2, Pentium (R) Dual-Core CPU E5300 @ 2.60GHz 2599.968, 2089.96MB RAM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2