Sponsored Content
Operating Systems Solaris A little complex: why my packet don't route? Post 303026120 by hicksd8 on Tuesday 20th of November 2018 12:07:54 PM
Old 11-20-2018
We had a very similar question asked recently when various of us tried to help.

Configure Solaris zone on new network

May I suggest that you read ALL this thread first. The OP seemed to find his own solution by amending the zone configuration to specify a router ip.

If none of this works for you please do post back here.

Last edited by hicksd8; 11-20-2018 at 01:14 PM..
 

7 More Discussions You Might Find Interesting

1. IP Networking

Seeing IP packet

Hi, Is there any way that i can directly take out the IP packet and see its contents. Waiting for your answer .............. Bye (4 Replies)
Discussion started by: manjunath
4 Replies

2. IP Networking

Software/tool to route an IP packet to proxy server and capture the Proxy reply as an

Hi, I am involved in a project on Debian. One of my requirement is to route an IP packet in my application to a proxy server and receive the reply from the proxy server as an IP packet. My application handles data at the IP frame level. My application creates an IP packet(with all the necessary... (0 Replies)
Discussion started by: Rajesh_BK
0 Replies

3. Programming

packet capture

can anyone tell me how can i capture the packets. i have tried ethernet software to capture them but its not doing what i want it to do it (1 Reply)
Discussion started by: dazdseg
1 Replies

4. Cybersecurity

filter packet

Exercise: Protection of WEB and DNS servers using the context-free rules for packet filtering: - Protect your WEB-server, so that would be for him can be accessed by browsers, and could go to dns. - Protect your primary DNS-server so that it could be to contact clients and secondary servers.... (1 Reply)
Discussion started by: numeracy
1 Replies

5. AIX

Packet loss coming with big packet size ping

(5 Replies)
Discussion started by: Vishal_dba
5 Replies

6. UNIX for Dummies Questions & Answers

iptables / ip route packet routing with multiple gateways

Hi all. Linux noob here. I was hoping someone could help me with configuring some routing rules on my router, an Asus AC68. The router is connected to two gateways, wan0_gateway and wan1_gateway. I have rules set up in the router gui that will push all traffic from every IP other than my own... (0 Replies)
Discussion started by: Bishi
0 Replies

7. IP Networking

Packet going out of wrong interface due to OS automatically added cache route with lower metric

RHEL 7.0, IPV6 Scenario: I have routed specific network using network scripts. 1. "ip -6 route show" shows that route has been added. ( with metric 1024) 2. Ping of the specific IP through that route is successful. 3. Now after few days, for some reason, we see that cache route appears for... (3 Replies)
Discussion started by: msr1981
3 Replies
DHCP-HELPER(8)						      System Manager's Manual						    DHCP-HELPER(8)

NAME
dhcp-helper - A DHCP/BOOTP relay agent. SYNOPSIS
dhcp-helper [OPTION]... DESCRIPTION
dhcp-helper is a DHCP and BOOTP relay agent. It listens for DHCP and BOOTP broadcasts on directly connected subnets and relays them to DHCP or BOOTP servers elsewhere. It also relays replies from the remote servers back to partially configured hosts. Once hosts are fully config- ured they can communicate directly with their servers and no longer need the services of a relay. OPTIONS
The only required option is at least one DHCP server to relay to. The simplest way to configure dhcp-helper on a router is just to give the interface to the network containing the DHCP server with a -b option. All the other interfaces present on the machine will then accept DHCP requests. On a machine which does not have an interface on the network containing the DHCP server, use a -s option instead. -s <server> Specify a DHCP or BOOTP server to relay to. The server may be given as a machine name or dotted-quad IP address. More than one server may be specified. -b <interface> Relay to a DHCP or BOOTP server using broadcast via <interface>. This eliminates the need to give a server address. <interface> is automatically added to the list of interfaces which will not receive DHCP requests. -i <interface> Specify which local interfaces to listen on for DHCP/BOOTP broadcasts. If no -i flags are given all interfaces are used except those specified by -e flags and those specified by -b flags. -e <interface> Specify which local interfaces to exclude. -p Use alternative ports (1067/1068) for the DHCP client and server. -v Report the software release version and copyright information. -d Debug mode, do not change UID, write a pid-file or go into the background. -r <file> Specify an alternate path for dhcp-helper to record its process-id in. Normally /var/run/dhcp-helper.pid. -u <username> Specify the userid to which dhcp-helper will change after startup. The daemon must normally be started as root, but it will drop root priviledges after startup by changing id to another user. Normally this user is "nobody" but that can be over-ridden with this switch. NOTES
Dhcp-helper requires a 2.2 or later Linux kernel. The "Linux packet filter" and "packet socket" facilities are not required, which is the chief advantage of this software over the ISC DHCP relay daemon. AUTHOR
This manual page was written by Simon Kelley <simon@thekelleys.org.uk>. DHCP-HELPER(8)
All times are GMT -4. The time now is 12:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy